What Microsoft, GitHub, Cloudflare, Ubiquiti, Cisco Meraki, Palo Alto Networks, GitLab, OpenAI, Anthropic, and Google post on their public status pages, read every 5 minutes while something is open. Each incident shows what else was happening and what changed in the same products just before.
On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not increase capacity as intended, so the backlog did not clear on its own. The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job processing so on-call is paged before customers experience delayed pull request updates.
3 earlier updates
1 Sep 16:00 UTCUpdateTime to update pull request diffs have improved to normal thresholds.
1 Sep 15:00 UTCUpdateDiffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
1 Sep 15:00 UTCInvestigatingWe are investigating reports of degraded performance for Pull Requests
Cloudflare resolved an issue with network performance for our Sofia (SOF) facility which occurred today, 2026-10-08, from approximately 21:35 to 21:50 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
1 earlier update
8 Oct 22:31 UTCInvestigatingCloudflare resolved an issue with network performance for our Sofia (SOF) facility which occurred today, 2026-10-08, from approximately 21:35 to 21:50 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
Around it3 other incidents at the same time · 5 earlier incidents
Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
Around it4 other incidents at the same time · 5 earlier incidents
Cloudflare resolved an issue with network performance for our Kochi (COK) facility which occurred today, 2026-10-08, between approximately 14:00 and 17:00 UTC. Customers may have observed elevated latency and/or error rates from this facility during this period.
Around it3 other incidents at the same time · 5 earlier incidents
We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts with pipeline and activity runs, integration runtime management, or authoring operations. Our engineers are actively working to determine the cause and impact. As a workaround, customers are advised to cancel and retry affected runs that fail, time out, or remain in progress longer than expected.
Around it4 other incidents at the same time · 2 earlier incidents · 3 changes in the 14 days before
We are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact . Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected. Further updates will be provided as more information becomes available.
Around it4 other incidents at the same time · 1 earlier incident · 4 changes in the 14 days before
Azure Data Factory issues in UK SouthWe are aware of an issue affecting Azure Data Factory in UK South, where a subset of customers may experience failures, delays, or timeouts when running pipelines and activities, managing integration runtimes, or performing authoring operations. Our engineers are actively investigating the cause and impact.Workaround: Customers are advised to cancel and retry affected pipeline or activity runs that fail, time out, or remain in progress longer than expected.Further updates will be provided as more information becomes available.
Around it3 other incidents at the same time · 2 earlier incidents · 3 changes in the 14 days before
We have identified an issue which resulted in some organizations to be incorrectly paused for having reached their spend limit, resulting in refused requests on the Claude API, Claude.ai, Claude Code, Claude Security, and Claude Cowork. This is now resolved.
Around it2 other incidents at the same time · 4 earlier incidents · 1 change in the 14 days before
GitHubIncident with Git Operations, Issues, Actions and Pull Requestslast seen 18:04 UTCunknown
Posted 7 Oct 17:17 UTCUpdated 31 h 12 min ago
Git OperationsPull RequestsActionsIssues
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.
5 earlier updates
7 Oct 18:00 UTCUpdateAll systems have recovered. We have applied mitigations and do not anticipate another recurrence.
7 Oct 17:27 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
7 Oct 17:25 UTCUpdateWe observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
7 Oct 17:25 UTCUpdateWe observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update shortly.
7 Oct 17:17 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
Around it3 other incidents at the same time · 5 earlier incidents
GitHubIncident with Git Operations, Pull Requests and Actionslast seen 16:25 UTCunknown
Posted 7 Oct 15:14 UTCUpdated 32 h 51 min ago
Git OperationsPull RequestsActions
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.
19 earlier updates
7 Oct 16:23 UTCUpdateGit Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
7 Oct 15:58 UTCUpdateWe are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
7 Oct 15:56 UTCUpdateThe degradation has been mitigated. We are monitoring to ensure stability.
7 Oct 15:49 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
7 Oct 15:49 UTCUpdateThe degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
7 Oct 15:47 UTCUpdateThe degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
7 Oct 15:41 UTCUpdateWe are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
7 Oct 15:35 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
7 Oct 15:32 UTCUpdateActions is operating normally.
7 Oct 15:31 UTCUpdateThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
7 Oct 15:27 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
7 Oct 15:27 UTCUpdateGit Operations is operating normally.
7 Oct 15:25 UTCUpdatePull Requests is experiencing degraded performance. We are continuing to investigate.
7 Oct 15:24 UTCUpdateWe observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
7 Oct 15:21 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
7 Oct 15:16 UTCUpdateWebhooks is experiencing degraded availability. We are continuing to investigate.
7 Oct 15:15 UTCUpdateIssues is experiencing degraded performance. We are continuing to investigate.
7 Oct 15:14 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
7 Oct 15:14 UTCInvestigatingWe are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
Around it3 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare API service issuesresolved 15:24 UTC43 min
Started 7 Oct 14:41 UTCUpdated 33 h 51 min ago
API
This incident has been resolved.
2 earlier updates
7 Oct 14:55 UTCMonitoringA fix has been implemented and we are monitoring the results.
7 Oct 14:41 UTCInvestigatingCloudflare is investigating issues with Cloudflare Dashboard APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
Around it3 other incidents at the same time · 5 earlier incidents
CloudflareNetwork Performance Issues in Columbusresolved 11:51 UTC9 h 2 min
Started 7 Oct 02:48 UTCUpdated 37 h 25 min ago
North AmericaNetwork
This incident has been resolved.
3 earlier updates
7 Oct 05:11 UTCMonitoringA fix has been implemented and we are monitoring the results.
7 Oct 03:06 UTCIdentifiedThe issue has been identified and a fix is being implemented.
7 Oct 02:48 UTCInvestigatingCloudflare is investigating issues with Network Performance in Columbus, OH (CMH). We are working to analyze and mitigate this problem. More updates to follow shortly.
Around it3 other incidents at the same time · 5 earlier incidents
This incident has been resolved. From 17:00 PT on October 6 / 00:00 UTC on October 7 to 18:40 PT on October 6 / 01:40 UTC on October 7, many requests to load usage data on the platform.claude.com Usage page and the Admin API usage report returned errors.
1 earlier update
7 Oct 01:20 UTCInvestigatingWe are investigating elevated errors loading usage data on the platform.claude.com Usage page and the Admin API usage report endpoint since 5 PM PT. Messages API requests are not affected. We will provide an update as soon as possible.
Around it1 other incident at the same time · 5 earlier incidents
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.
8 earlier updates
6 Oct 22:40 UTCUpdateWe are deploying a mitigation and plan to resume migrations shortly thereafter
6 Oct 21:29 UTCUpdateWe are working towards a mitigation that will allow us to resume processing enterprise migrations.
6 Oct 20:57 UTCInvestigatingAll services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
6 Oct 20:26 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
6 Oct 20:22 UTCUpdateA number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
6 Oct 20:12 UTCUpdatePull Requests is operating normally.
6 Oct 20:04 UTCUpdateWebhooks is operating normally.
6 Oct 19:57 UTCInvestigatingWe are investigating reports of degraded performance for Pull Requests and Webhooks
Around it2 other incidents at the same time · 5 earlier incidents
CloudflareNetwork routing issueresolved 15:33 UTC1 h 59 min
Started 6 Oct 13:34 UTCUpdated 2d ago
Network
This incident has been resolved.
3 earlier updates
6 Oct 14:34 UTCMonitoringWe are continuing to monitor for any further issues.
6 Oct 14:15 UTCIdentifiedWe are continuing to work on a fix for the issue.
6 Oct 13:34 UTCInvestigatingCloudflare is aware of an issue with network routing to Microsoft Azure, which is causing errors for requests directed to origins hosted on that service. The team is actively working on remediation.
Around it3 other incidents at the same time · 5 earlier incidents
The issue affecting Claude Opus 5.5 has been resolved.
2 earlier updates
6 Oct 12:37 UTCIdentifiedWe have identified the cause of elevated errors on requests to Claude Opus 5.5 and are working on a fix. We will provide an update as soon as possible.
6 Oct 12:24 UTCInvestigatingWe are investigating elevated errors on requests to Claude Opus 5.5. We will provide an update as soon as possible.
Around it1 other incident at the same time · 4 earlier incidents · 1 change in the 14 days before
CloudflareRSA Keyless SSL handshake issuesresolved 09:06 UTC44 min
Started 6 Oct 08:22 UTCUpdated 2d ago
Keyless SSL
This incident has been resolved.
2 earlier updates
6 Oct 08:55 UTCMonitoringWe are continuing to monitor for any further issues.
6 Oct 08:22 UTCIdentifiedCloudflare is aware of and is investigating an issue with Keyless SSL, which results in TLS handshake failures, only affecting RSA Keyless SSL with specific key backend configurations. We are working to resolve this. Updates to follow.
Around it2 other incidents at the same time · 5 earlier incidents
OpenAIElevated errors affecting multiple products including ChatGPT (conversations), Image generations, Spaces and Pages, API rehydration, and Dots.last seen 03:17 UTCunknown
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.
2 earlier updates
6 Oct 00:05 UTCUpdateUsers may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
5 Oct 23:47 UTCInvestigatingWe are investigating reports of impacted performance for some GitHub services.
Around it6 other incidents at the same time · 5 earlier incidents
Microsoft 365 admin centerAdmins intermittently may be unable to access the Microsoft 365 admin centerlast seen 01:23 UTCunknown
Posted 6 Oct 00:09 UTCUpdated 3d ago
Admin center
User impact: Admins intermittently may be unable to access the Microsoft 365 admin center. Current status: We're continuing to analyze the unusually large increase in requests to the Microsoft 365 admin center along with recent service updates to isolate potential sources of impact that contributed to the traffic increase. We’ve implemented performance optimizations to assist with processing affected traffic and we've validated that service availability has recovered to pre-impact levels. We're continuing our investigation in order to isolate and remediate the underlying root cause to ensure the similar scenario does not occur again in the future. Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as the investigation progresses. Start time: Monday, October 5, 2026, at 10:28 PM UTC Next update by: Tuesday, October 6, 2026, at 1:30 AM UTC
Microsoft 365 admin centerAdmins intermittently may be unable to access the Microsoft 365 admin centerlast seen 00:13 UTCunknown
Posted 5 Oct 23:39 UTCUpdated 3d ago
Admin center
User impact: Admins intermittently may be unable to access the Microsoft 365 admin center. Current status: We’re investigating an unusually large increase in requests to the Microsoft 365 admin center and expect that this increase is resulting in requests queuing and timing-out. We’re reviewing options for mitigating this issue and determining if other factors are contributing to the problem. Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. Next update by: Wednesday, October 6, at 12:30 AM UTC
Microsoft 365 admin centerSome admins may be unable to access the Microsoft 365 admin portallast seen 23:43 UTCunknown
Posted 5 Oct 23:21 UTCUpdated 3d ago
Admin center
Current status: We're investigating a potential issue impacting admin access to the Microsoft 365 admin portal in certain regions and we're checking for impact to your organization. We'll provide an update within 30 minutes.
GitHubIncident with Actionslast seen 22:49 UTCunknown
Posted 5 Oct 19:11 UTCUpdated 3d ago
Actions
On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.
12 earlier updates
5 Oct 22:49 UTCResolvedThis 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.
5 Oct 22:40 UTCUpdatePages is operating normally.
5 Oct 21:54 UTCUpdateActions is operating normally.
5 Oct 21:32 UTCUpdateWe have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
5 Oct 21:31 UTCUpdateActions is experiencing degraded performance. We are continuing to investigate.
5 Oct 21:22 UTCUpdatePages is experiencing degraded performance. We are continuing to investigate.
5 Oct 21:09 UTCUpdateIn addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
5 Oct 20:47 UTCUpdateActions is experiencing degraded availability. We are continuing to investigate.
5 Oct 20:39 UTCUpdateWe’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
5 Oct 19:50 UTCUpdateWe’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
5 Oct 19:15 UTCUpdateWe’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
5 Oct 19:11 UTCInvestigatingWe are investigating reports of degraded performance for Actions
Around it5 other incidents at the same time · 5 earlier incidents
CloudflareAPI Shield JWT Validation Errorsresolved 22:39 UTC11 h 43 min
Started 5 Oct 10:55 UTCUpdated 3d ago
API Shield
This incident has been resolved.
3 earlier updates
5 Oct 20:09 UTCMonitoringA fix has been implemented and we are monitoring the results.
5 Oct 11:24 UTCIdentifiedThe issue has been identified and a fix is being implemented.
5 Oct 10:55 UTCInvestigatingCloudflare is investigating an issue affecting API Shield JWT validation for customers using symmetric keying material. Our team is actively working on restoring normal service.
Around it6 other incidents at the same time · 5 earlier incidents
5 Oct 17:53 UTCMonitoringA fix has been implemented and we are monitoring the results.
5 Oct 17:14 UTCInvestigatingWe are investigating an issue leading to decreased availability for Durable Objects and dependent services in the Eastern North America region. Our engineering team is actively working to mitigate the impact, and further updates will be provided as soon as more information becomes available.
Around it5 other incidents at the same time · 5 earlier incidents
The issue affecting Claude Mythos 5.1 and Claude Fable 5.1 has been resolved. Impact occurred from 05:40 PT / 12:40 UTC to 06:10 PT / 13:10 UTC.
1 earlier update
5 Oct 13:05 UTCInvestigatingWe are investigating elevated errors on requests to Claude Mythos 5.1 and Claude Fable 5.1. We will provide an update as soon as possible.
Around it3 other incidents at the same time · 3 earlier incidents · 1 change in the 14 days before
Cloudflare investigated reports of increased latency affecting requests for cacheable assets across multiple locations between 09:30 and 11:10 UTC. The issue is now resolved.
1 earlier update and 1 change ChangeIntel noticed
5 Oct 09:30 UTCResolvedCloudflare investigated reports of increased latency affecting requests to the CDG data center for cacheable assets between 09:30 and 11:10 UTC. The issue is now resolved.
5 Oct 13:11 UTC ChangeIntel noticed a new title; it was "Increase in Latency in Paris, France region (CDG)"
Around it1 other incident at the same time · 5 earlier incidents
CloudflareIssues with Workers Build failing to startresolved 07:28 UTC2 days
Started 3 Oct 05:54 UTCUpdated 3d ago
Workers Builds
This incident has been resolved.
2 earlier updates
3 Oct 08:54 UTCMonitoringA fix has been implemented and we are monitoring the results.
3 Oct 05:54 UTCInvestigatingCloudflare is aware of and investigating an issue with Cloudflare Workers build failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.
Around it2 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
CloudflareHyperdrive Degraded Performanceresolved 00:00 UTC24 days
Started 11 Sep 00:00 UTCUpdated 25 h 20 min ago
Hyperdrive
Cloudflare identified an issue that affected Hyperdrive performance between 11th September and 5th October 2026. During this time, customers may have experienced elevated latency. This incident has been resolved.
Around it4 other incidents at the same time
Elsewhere at the same time · within 12 hours of its start
CloudflareCloudflare CDN experiencing increase in errors.resolved 21:57 UTC11 min
Started 2 Oct 21:46 UTCUpdated 6d ago
CDN/CacheCDN Cache Purge
This incident has been resolved.
2 earlier updates
2 Oct 21:46 UTCMonitoringCloudflare is investigating an increase in errors for CDN configuration changes and purge calls specifically issued from the dashboard. Otherways to purge and configure Cloudflare (for example via API or terraform) were unaffected.
2 Oct 21:46 UTCMonitoringCloudflare is investigating an increase in errors for CDN configuration changes and purge calls specifically issued from the dashboard. Purges sent via API were unaffected. CDN configuration changes across the dashboard, API and others saw impact.
Around it3 other incidents at the same time · 5 earlier incidents
Between 17:11 and 17:22 UTC, Cloudflare experienced network performance degradation impacting Seoul, South Korea (ICN). The issue has been identified and fully mitigated, and network performance has returned to normal levels.
Around it2 other incidents at the same time · 5 earlier incidents
30 Sep 14:06 UTCMonitoringA fix has been implemented and we are monitoring the results.
30 Sep 11:31 UTCIdentifiedThe issue has been identified and a fix is being implemented.
30 Sep 10:31 UTCInvestigatingCloudflare is investigating issues with network performance in Madrid (MAD). We are working to analyse and mitigate this problem. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
Bars compare how long each incident lasted, up to three days; a lighter bar is a lower bound and a hatched one is unknown. Older incidents are kept for 90 days on the timeline.
Azure post-incident reviews
What went wrong in major incidents and what Microsoft is changing