Vendor-reported status observed by INTERNETMON
Sumo Logic status
Sumo Logic · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
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
198
Retained
100
Affected retained
0
Projection scope: complete · 100 retained of 198 reported components across 11 source groups · bounded/truncated source projection.
APIs
Group: Japan (JP)
Operational
APIs
Group: North America 1 (US1)
Operational
APIs
Group: North America 2 (US2)
Operational
APIs
Group: Europe 1 (EU)
Operational
APIs
Group: Europe 2 (DE)
Operational
APIs
Group: Australia (AU)
Operational
APIs
Group: Canada (CA)
Operational
APIs
Group: Korea (KR)
Operational
APIs
Group: America Federal (FED)
Operational
APIs
Group: Zurich (CH)
Operational
APIs
Group: European Sovereign Cloud (ESC)
Operational
Authentication
Group: Korea (KR)
Operational
Authentication
Group: North America 1 (US1)
Operational
Authentication
Group: North America 2 (US2)
Operational
Authentication
Group: Europe 1 (EU)
Operational
Authentication
Group: Europe 2 (DE)
Operational
Authentication
Group: Australia (AU)
Operational
Authentication
Group: Japan (JP)
Operational
Authentication
Group: Canada (CA)
Operational
Authentication
Group: America Federal (FED)
Operational
Showing 20 of 100 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 · 498.15 ms feed latency
Operational
HTTP 200 · 5158.03 ms feed latency
Operational
HTTP 200 · 504.66 ms feed latency
Operational
HTTP 200 · 414.23 ms feed latency
Operational
HTTP 200 · 335.04 ms feed latency
Operational
HTTP 200 · 543.61 ms feed latency
Operational
HTTP 200 · 346.64 ms feed latency
Operational
HTTP 200 · 557.19 ms feed latency
Operational
HTTP 200 · 463.01 ms feed latency
Operational
HTTP 200 · 339.7 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
256.8 ms
JSON source