Vendor-reported status observed by INTERNETMON
New Relic status
New Relic · 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
106
Retained
100
Affected retained
0
Projection scope: complete · 100 retained of 106 reported components across 9 source groups · bounded/truncated source projection.
APM : US
Group: Alert Notifications : US
Operational
APM : Europe
Group: Alert Notifications : Europe
Operational
APM Agent : US
Group: Data Ingest : US
Operational
APM Agent : Europe
Group: Data Ingest : Europe
Operational
Alerts : US
Group: UI : US
Operational
Alerts : Europe
Group: UI : Europe
Operational
APM Agent : JP
Group: Data Ingest : JP
Operational
APM : JP
Group: Alert Notifications : JP
Operational
Alerts : JP
Group: UI : JP
Operational
APM : US
Group: UI : US
Operational
Browser : US
Group: Alert Notifications : US
Operational
APM : Europe
Group: UI : Europe
Operational
Browser : Europe
Group: Alert Notifications : Europe
Operational
Browser Agent : US
Group: Data Ingest : US
Operational
Browser Agent : Europe
Group: Data Ingest : Europe
Operational
Browser Agent : JP
Group: Data Ingest : JP
Operational
Browser : JP
Group: Alert Notifications : JP
Operational
APM : JP
Group: UI : JP
Operational
Infrastructure : US
Group: Alert Notifications : US
Operational
Infrastructure : Europe
Group: Alert Notifications : Europe
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 · 181.86 ms feed latency
Operational
HTTP 200 · 166.19 ms feed latency
Operational
HTTP 200 · 180.33 ms feed latency
Operational
HTTP 200 · 182.32 ms feed latency
Operational
HTTP 200 · 243.53 ms feed latency
Operational
HTTP 200 · 108.17 ms feed latency
Operational
HTTP 200 · 292.46 ms feed latency
Operational
HTTP 200 · 90.56 ms feed latency
Operational
HTTP 200 · 165.65 ms feed latency
Operational
HTTP 200 · 235.75 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
322.28 ms
JSON source