Vendor-reported status observed by INTERNETMON
Akamai status
Akamai · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Cloud and delivery 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
42
Retained
42
Affected retained
0
Projection scope: complete · 42 retained of 42 reported components across 6 source groups.
Akamai Control Center
Group: Customer Service, Documentation and Community
Operational
Cloudlets
Group: Content Delivery
Operational
Log Delivery
Group: Data Services
Operational
Configuration Deployment
Group: Configuration
Operational
Akamai MFA
Group: Enterprise Security
Operational
Account Protector
Group: App & Network Security
Operational
Edge Delivery
Group: Content Delivery
Operational
Content Purge
Group: Configuration
Operational
Akamai Identity Cloud
Group: App & Network Security
Operational
mPulse
Group: Data Services
Operational
Enterprise Application Access
Group: Enterprise Security
Operational
Akamai Customer Community
Group: Customer Service, Documentation and Community
Operational
Bot Management
Group: App & Network Security
Operational
Reporting
Group: Data Services
Operational
Global Traffic Management
Group: Content Delivery
Operational
Enterprise Application Access: API Service
Group: Enterprise Security
Operational
Akamai Partner Community
Group: Customer Service, Documentation and Community
Operational
TLS Provisioning (Certificates, CPS)
Group: Configuration
Operational
Image Management
Group: Content Delivery
Operational
SIEM Data feeds
Group: Data Services
Operational
Showing 20 of 42 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 · 56.98 ms feed latency
Operational
HTTP 200 · 256.1 ms feed latency
Operational
HTTP 200 · 227.85 ms feed latency
Operational
HTTP 200 · 387.22 ms feed latency
Operational
HTTP 200 · 135.14 ms feed latency
Operational
HTTP 200 · 226.02 ms feed latency
Operational
HTTP 200 · 357.08 ms feed latency
Operational
HTTP 200 · 124.97 ms feed latency
Operational
HTTP 200 · 160.16 ms feed latency
Operational
HTTP 200 · 315.65 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
156.05 ms
JSON source