Vendor-reported status observed by INTERNETMON
Iterable status
Iterable · 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
488
Retained
100
Affected retained
0
Projection scope: complete · 100 retained of 488 reported components across 68 source groups · bounded/truncated source projection.
Global Web Application
Operational
Email Sends
Group: Cluster 5
Operational
Email Sends
Group: Cluster 6
Operational
Email Sends
Group: Cluster 8
Operational
Email Sends
Group: Cluster 9
Operational
Email Sends
Group: Cluster 10
Operational
Email Sends
Group: Cluster 11
Operational
Email Sends
Group: Cluster 12
Operational
Email Sends
Group: Cluster 13
Operational
Email Sends
Group: Cluster 14
Operational
Email Sends
Group: Cluster 15
Operational
Email Sends
Group: Cluster 16
Operational
Email Sends
Group: Cluster 17
Operational
Email Sends
Group: Cluster 18
Operational
Emails Sends
Group: Cluster 19
Operational
Email Sends
Group: Cluster 20
Operational
Email Sends
Group: Cluster 21
Operational
Email Sends
Group: Cluster 22
Operational
Email Sends
Group: Cluster 23
Operational
Email Sends
Group: Cluster 100
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 · 403.91 ms feed latency
Operational
HTTP 200 · 198.75 ms feed latency
Operational
HTTP 200 · 375.51 ms feed latency
Operational
HTTP 200 · 301.65 ms feed latency
Operational
HTTP 200 · 300.96 ms feed latency
Operational
HTTP 200 · 212.47 ms feed latency
Operational
HTTP 200 · 424.67 ms feed latency
Operational
HTTP 200 · 212.18 ms feed latency
Operational
HTTP 200 · 168.72 ms feed latency
Operational
HTTP 200 · 304.29 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
112.01 ms
JSON source