Vendor-reported status observed by INTERNETMON
CircleCI status
CircleCI · 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
39
Retained
39
Affected retained
0
Projection scope: complete · 39 retained of 39 reported components across 2 source groups.
AWS
Group: CircleCI Dependencies
Operational
Atlassian Bitbucket API
Group: Upstream Services
Operational
Docker Jobs
Operational
Atlassian Bitbucket Source downloads
Group: Upstream Services
Operational
Google Cloud Platform Google Cloud DNS
Group: CircleCI Dependencies
Operational
Machine Jobs
Operational
Atlassian Bitbucket SSH
Group: Upstream Services
Operational
macOS Jobs
Operational
Google Cloud Platform Google Cloud Networking
Group: CircleCI Dependencies
Operational
Atlassian Bitbucket Webhooks
Group: Upstream Services
Operational
Google Cloud Platform Google Cloud Storage
Group: CircleCI Dependencies
Operational
Windows Jobs
Operational
Google Cloud Platform Google Compute Engine
Group: CircleCI Dependencies
Operational
Pipelines & Workflows
Operational
Docker Hub
Group: Upstream Services
Operational
mailgun API
Group: CircleCI Dependencies
Operational
GitHub Git Operations
Group: Upstream Services
Operational
CircleCI API
Operational
CircleCI UI
Operational
mailgun Outbound Delivery
Group: CircleCI Dependencies
Operational
Showing 20 of 39 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 · 217.93 ms feed latency
Degraded
HTTP 200 · 143.91 ms feed latency
Operational
HTTP 200 · 178.91 ms feed latency
Degraded
HTTP 200 · 101.31 ms feed latency
Operational
HTTP 200 · 235.23 ms feed latency
Operational
HTTP 200 · 240.04 ms feed latency
Operational
HTTP 200 · 193.34 ms feed latency
Operational
HTTP 200 · 160.13 ms feed latency
Operational
HTTP 200 · 442.84 ms feed latency
Operational
HTTP 200 · 198.94 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
218.52 ms
JSON source