Vendor-reported status observed by INTERNETMON
Box status
Box · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Platform services
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.
Active incidents
No active incidents were included in this vendor report.
Maintenance
No active or upcoming maintenance was included in this vendor report.
Component health
Reported
84
Retained
84
Affected retained
0
Projection scope: complete · 84 retained of 84 reported components across 8 source groups.
Content API
Group: Box Platform / API
Operational
Login/SSO
Group: Box Web Application
Operational
Login/SSO
Group: Desktop Applications
Operational
Login/SSO
Group: Mobile Applications
Operational
Microsoft Office Integration
Group: Partners / Integrations
Operational
Case Submission Workflow
Group: Box Community and Support Website (community.box.com)
Operational
Web Application
Group: Box Notes
Operational
Australia
Group: Box Zones
Operational
Content Preview
Group: Box Platform / API
Operational
Box Sync
Group: Desktop Applications
Operational
Uploads/Downloads
Group: Box Web Application
Operational
Preview
Group: Mobile Applications
Operational
Apple iWork
Group: Partners / Integrations
Operational
Blog Posts and Knowledge Articles
Group: Box Community and Support Website (community.box.com)
Operational
Canada
Group: Box Zones
Operational
Box Drive
Group: Desktop Applications
Operational
Collaboration
Group: Box Web Application
Operational
Authentication (OAuth 2.0 / JWT)
Group: Box Platform / API
Operational
Search
Group: Mobile Applications
Operational
Community Forums
Group: Box Community and Support Website (community.box.com)
Operational
Showing 20 of 84 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.
Recent observed status changes and checkpoints
These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.
Operational
HTTP 200 · 106.6 ms feed latency
Operational
HTTP 200 · 221.62 ms feed latency
Operational
HTTP 200 · 110.95 ms feed latency
Operational
HTTP 200 · 148.86 ms feed latency
Operational
HTTP 200 · 290.69 ms feed latency
Operational
HTTP 200 · 169.26 ms feed latency
Operational
HTTP 200 · 180.86 ms feed latency
Operational
HTTP 200 · 58.33 ms feed latency
Operational
HTTP 200 · 188.78 ms feed latency
Operational
HTTP 200 · 114.16 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
176.38 ms
JSON source