βοΈ Cloud Weather
Real-time Cloud Service Status
Timeline
Network Performance Issues in XFN
minor Β· investigating
Cloudflare is investigating issues with Network Performance in Xiangyang, China. We are working to analyze and mitigate this problem. More updates to follow shortly.
View Details βIncreased HTTP 499 and 5xx Errors in our Osaka, Japan (KIX) data center
minor Β· resolved
This incident has been resolved.
View Details βCloudflare Workers AI Issues
minor Β· resolved
This incident has been resolved.
View Details βCloudflare Workers Builds: increased failures
minor Β· resolved
This incident has been resolved.
View Details βDisruption with some GitHub services
minor Β· resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
View Details βLoad Balancing and Health Checks degraded performance
minor Β· resolved
This incident has been resolved.
View Details βCloudflare Dashboard service issues
minor Β· resolved
This incident has been resolved.
View Details βCloudflare Workers AI Issues
minor Β· resolved
This incident has been resolved.
View Details βIssues with Private Network CIDR Routes for WARP Connector
none Β· resolved
Cloudflare was investigating an issue affecting WARP Connector where traffic destined for specific Private IP CIDR ranges failed to route correctly for a small subset of accounts. This occurred between 2025-11-20 18:09 UTC to 2025-11-21 13:44 UTC. During this window, affected WARP Connectors may have appeared connected but failed to pass traffic to specific internal resources. Our engineering team identified the underlying cause and deployed a fix. This issue is fully resolved now.
View Details βNetwork Performance Issues in Asia
minor Β· resolved
This incident is now resolved.
View Details βCNI Version 2 Issues in Newark
minor Β· resolved
This incident has been resolved.
View Details βDisruption with some GitHub services
minor Β· resolved
Between November 20, 2025 17:16 UTC to November, 2025 19:08 UTC some users experienced delayed or failed Git Operations for raw file downloads. On average, the error rate was less than 0.2%. This was due to a sustained increase in unauthenticated repository traffic.<br /><br />We mitigated the incident by applying regional rate limiting and are taking steps to improve our monitoring and time to mitigation for similar issues in the future.
View Details βIncident with Actions
minor Β· resolved
On November 19, between 17:36 UTC and 18:04 UTC, GitHub Actions service experienced degraded performance that caused excessive latency in queueing and updating workflow runs and job statuses. Operations related to artifacts, cache, job steps and logs also had significantly increased latency. At peak, 67% of workflow jobs queued during that timeframe were impacted, and the median latency for impacted operations increased by up to 35x.<br /><br />This was caused by a significant change in load pattern on Actions Cache-related operations, leading to a saturated shared resource on the backend. The impact was mitigated by mitigating the new load pattern.<br /><br />To reduce the likelihood of a recurrence, we are improving rate-limiting measures in this area to ensure a more consistent experience for all customers. We are also evaluating changes to reduce the scope of impact.
View Details βDisruption with some GitHub services
minor Β· resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
View Details βGit operation failures
major Β· resolved
From Nov 18, 2025 20:30 UTC to Nov 18, 2025 21:34 UTC we experienced failures on all Git operations, including both SSH and HTTP Git client interactions, as well as raw file access. These failures also impacted products that rely on Git operations.<br /><br />The root cause was an expired TLS certificate used for internal service-to-service communication. We mitigated the incident by replacing the expired certificate and restarting impacted services. Once those services were restarted we saw a full recovery.<br /><br />We have updated our alerting to cover the expired certificate and are performing an audit of other certificates in this area to ensure they also have the proper alerting and automation before expiration. In parallel, we are accelerating efforts to eliminate our remaining manually managed certificates, ensuring all service-to-service communication is fully automated and aligned with modern security practices.
View Details βElevated error rate for domain search and registration
minor Β· resolved
This incident has been resolved.
View Details βDisruption with some GitHub services
minor Β· resolved
Between November 17, 2025 21:24 UTC and November 18, 2025 00:04 UTC the gists service was degraded and users were unable to create gists via the web UI. 100% of gist creation requests failed with a 404 response. This was due to a change in the web middleware that inadvertently triggered a routing error. We resolved the incident by rolling back the change. We are working on more effective monitoring to reduce the time it takes to detect similar issues and evaluating our testing approach for middleware functionality.
View Details βDisruption with some GitHub services
major Β· resolved
From Nov 17, 2025 00:00 UTC to Nov 17, 2025 15:00 UTC Dependabot was hitting a rate limit in GitHub Container Registry (GHCR) and was unable to complete about 57% of jobs.<br /><br />To mitigate the issue we lowered the rate at which Dependabot started jobs and increased the GHCR rate limit.<br /><br />Weβre adding new monitors and alerts and looking into more ways to decrease load on GHCR to help prevent this in the future.
View Details βBuilds and Deployments were Temporarily in a Queued State
minor Β· resolved
Builds and deployments were stuck in a queued state between 10:05 to 10:30 UTC. Our team identified the root cause and deployed a fix, and everything is now operating normally.
View Details βBuilds and Deployments are Currently in a Queued State
minor Β· resolved
This incident has been resolved.
View Details β