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.
Choose the providers you depend on and the regions you run in, and what affects you comes first
Ended in the last 7 days
59 incidents · newest first
Tue 6 Oct1
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 8d 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
Cisco MerakiCloud Communication Interruptionlast seen 17:10 UTCunknown
Posted today 13:58 UTCUpdated 57 min ago
North and South AmericaDashboardEnd User Device Connectivity
This incident is now resolved. We are sorry for any interruption to your service.
3 earlier updates
today 16:26 UTCMonitoringWe have deployed a fix and regular service is now restored. We will continue to monitor the situation. Please reach out to Meraki Support if you a re still experiencing a service interruption.
today 14:15 UTCIdentifiedWe have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses.
today 13:58 UTCInvestigatingWe are investigating an issue with the Device to Cloud Communication that is impacting some users. Next update as soon as more information becomes available.
Around it6 other incidents at the same time · 1 change in the 14 days before
today 16:43 UTCMonitoringCloudflare has implemented a fix and is currently monitoring for exceptions. We will update the status once the issue is resolved.
23 Sep 11:02 UTCIdentifiedThe issue has been identified and a fix is being implemented.
22 Sep 19:23 UTCInvestigatingCloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.
Around it4 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
CloudflareIncreased HTTP Errors in London (LHR)resolved 07:51 UTC8 min
Started today 07:43 UTCUpdated 7 h 12 min ago
Network
Cloudflare is aware of, and has resolved, an increased level of HTTP errors in London (LHR), between 07:43 UTC and 07:51 UTC. Services have resumed normal operation after this time.
Around it6 other incidents at the same time · 5 earlier incidents
Mitigations have been put in place to prevent recurrence.
2 earlier updates
today 04:54 UTCMonitoringA fix has been implemented and we are monitoring the results.
today 04:40 UTCInvestigatingCloudflare is investigating increased numbers of 5XX errors in PDX. 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
CloudflareElevated errors in Los Angeles (LAX)resolved 05:20 UTC25 min
Started today 04:55 UTCUpdated 12 h 16 min ago
Network
Customers reaching Los Angeles (LAX) colo may have seen an elevate number of errors during the time. The problem has been mitigated, and we are currently monitoring.
Around it6 other incidents at the same time · 5 earlier incidents
Cloudflare observed possible network congestion in Dallas, TX, United States (DFW) between 14th October 03:02–03:30 UTC. The issue has fully resolved, and we are monitoring for stability.
Around it4 other incidents at the same time · 5 earlier incidents
Monitoring shows failures are still occurring in a tool used by Duo Code Review. The service remains available, but reviews may contain less context than expected. A fix is merged and awaiting deployment; we’ll update once recovery is confirmed.
4 earlier updates
13 Oct 00:29 UTCMonitoringErrors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated.
13 Oct 00:28 UTCMonitoringErrors affecting Code Review tools have decreased, and the tools appear to be operating normally. We’re monitoring error rates and investigating the improvement. A fix is merged but not yet in production, so recovery is still being validated.
12 Oct 13:37 UTCIdentifiedWe've identified the cause of the issue affecting GitLab Duo Workflow operations. Duo Code Review remains available, but reviews may contain less context than expected. Our engineering teams are expediting a fix and will continue monitoring until service is fully restored. For more details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158
12 Oct 11:30 UTCIdentifiedWe’re investigating an issue affecting some GitLab Duo Workflow operations. Duo Code Review results may be incomplete or lower quality than expected. Our engineering teams are working on mitigation and will provide further updates. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23158
Around it6 other incidents at the same time · 1 earlier incident · 1 change in the 14 days before
Elsewhere at the same time · within 12 hours of its start
CloudflareCloudflare Workers - Cron Trigger Activation Issuesresolved 00:09 UTC8 h 51 min
Started 13 Oct 15:18 UTCUpdated 17 h 58 min ago
Workers
This incident has been resolved.
3 earlier updates
13 Oct 23:10 UTCMonitoringWe are continuing to monitor for any further issues.
13 Oct 15:19 UTCIdentifiedThe issue has been identified and a fix is being implemented.
13 Oct 15:18 UTCInvestigatingCloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
13 Oct 20:37 UTCIdentifiedCloudflare is investigating issues with network performance in LAX. 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
Microsoft 365 admin centerAdmins may be unable to review Service health or Message center postings in the Microsoft 365 admin centerlast seen 22:38 UTCunknown
Posted 13 Oct 21:02 UTCUpdated 21 h 5 min ago
Admin center
User impact: Admins may have been unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Admins' "What's new" tab in the Microsoft Teams admin center may have been blank and displayed an error stating, "We can't load data. Try again." Final status: We've completed our monitoring period and validated that the rollback of the service update containing the misconfiguration successfully remediated impact. Scope of impact: This issue affected some admins attempting to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. Start time: Monday, October 12, 2026, at 9:54 PM UTC End time: Tuesday, October 13, 2026, at 7:35 PM UTC Root cause: A recent service update introduced a misconfiguration which caused the Service Health and Communications API to return authentication errors, resulting in impact. Next steps: - We're analyzing the offending service update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future. This is the final update for the event.
Microsoft 365 admin centerAdmins may be unable to review Service health or Message center postings in the Microsoft 365 admin centerlast seen 21:07 UTCunknown
Posted 13 Oct 19:53 UTCUpdated 22 h 14 min ago
Admin center
User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We're continuing to monitor recovery, and we anticipate some users will start to see remediation at this time. To ensure impact is fully remediated, we've extended our monitoring period, and we anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 10:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC
GitLab.comJob delays on saas-linux-small-amd64 hosted runnerslast seen 21:02 UTC≥ 6 h 30 min
Started 13 Oct 14:27 UTCUpdated 22 h 36 min ago
CI/CDCI/CD - Hosted runners on Linux
Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The delays were caused by errors and capacity constraints from our cloud provider when provisioning runner capacity in one region, between approximately 13:17 and 19:15 UTC. Jobs that were delayed are now starting as usual. We are monitoring to make sure performance remains stable and will post an update when this incident is resolved.
2 earlier updates
13 Oct 15:46 UTCIdentifiedWe have identified an ongoing Google Cloud Compute Engine issue affecting runner-capacity provisioning in us-east1. Some GitLab.com CI/CD jobs using small Linux x86-64 hosted runners may remain pending longer than usual before starting. Our engineering teams are working with Google Cloud to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176
13 Oct 14:27 UTCInvestigatingWe are investigating increased queue times for CI/CD jobs using GitLab.com small Linux x86-64 hosted runners. Affected jobs may remain pending longer than usual before starting. We have identified errors and delays when provisioning runner capacity and are working to restore normal job start times. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23176
Around it6 other incidents at the same time · 1 earlier incident · 2 changes in the 14 days before
GitHub[Retroactive] Actions workflow run logs delayedlast seen 20:30 UTCunknown
Posted 13 Oct 20:30 UTCUpdated 21 h 37 min ago
Actions
On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up.The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.
Around it6 other incidents at the same time · 5 earlier incidents
Microsoft 365 admin centerAdmins may be unable to review Service health or Message center postings in the Microsoft 365 admin centerlast seen 19:57 UTCunknown
Posted 13 Oct 18:52 UTCUpdated 23 h 14 min ago
Admin center
User impact: Admins may be unable to review Service health or Message c enter postings in the Microsoft 365 admin center. More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again." Current status: We've received reports from a subset of affected users who have reported that they are unable to review Service health or Message c enter postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. We've isolated that a recent service update introduced a misconfiguration which cause s the Service Health and Communications API to return authentication errors, resulting in impact. We're rolling back the offending update and monitoring for remediation. We anticipate impact to be resolved by our next scheduled update. Scope of impact: This issue affects some admins who may be unable to review Service health or Message c enter postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses. Start time: Monday, October 12, 2026, at 9:54 PM UTC Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 8:00 PM UTC. Root cause: A recent service update introduced a misconfiguration which cause s the Service Health and Communications API to return authentication errors, resulting in impact. Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC
Microsoft 365 admin centerUsers may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)last seen 18:46 UTCunknown
Posted 13 Oct 18:20 UTCUpdated 23 h 47 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs As a workaround, users may disable GSA to access the affected Microsoft 365 services until the resolution of this incident. Current status: We're finishing our restarts throughout the affected infrastructure and expect this will be complete and resolve all impact by Tuesday, October 13, 2026, at 7:00 PM UTC. Our telemetry is showing service recovery, and we'll continue to monitor to ensure full remediation. Scope of impact: Some users in Germany attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 7:40 AM UTC Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC
Microsoft 365 admin centerUsers may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)last seen 18:21 UTCunknown
Posted 13 Oct 17:26 UTCUpdated 24 h 40 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're continuing our targeted restarts throughout the impacted infrastructure, and our telemetry shows services hosted on the restarted infrastructure are now operating at healthy service levels. We're also receiving confirmation that impact is resolved for some users. Scope of impact: Some users in Germany attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 7:40 AM UTC Next update by: Tuesday, October 13, 2026, at 6:30 PM UTC
7 Oct 21:44 UTCMonitoringWe've mitigated the errors loading usage data on platform.claude.com and in the Admin API usage report. While we work on a full fix, the most recent ~30 minutes of usage may take longer to appear on the platform.claude.com. API requests are not affected, and we will provide additional updates here.
7 Oct 17:28 UTCIdentifiedWe've identified the cause of errors loading usage data. The Admin API usage report has recovered, and fixes for the platform.claude.com Usage and Rate limits pages are in progress. The most recent 30 minutes of usage may be delayed. Core functionality is not affected.
7 Oct 16:36 UTCUpdateWe are continuing to work on elevated errors affecting usage data on the platform.claude.com Usage and Rate limits pages and the Admin API usage report. A mitigation for the Usage page and the Admin API usage report is rolling out; once it is in place, the most recent usage may take about 30 minutes to appear there. Core functionality is not affected.
7 Oct 13:25 UTCInvestigatingWe are investigating elevated errors affecting usage data on the platform.claude.com Usage page and the Admin API usage report. Core functionality is not affected. We will provide an update as soon as possible.
Around it6 other incidents at the same time · 4 earlier incidents · 1 change in the 14 days before
Elsewhere at the same time · within 12 hours of its start
12 Oct 21:41 UTCIdentifiedWe are continuing to work on a fix for the issue.
12 Oct 08:52 UTCInvestigatingCustomers reaching Los Angeles (LAX) colo may see an elevate number of errors. Our team is investigating and working on mitigating the issue.
Around it1 possibly related5 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
Microsoft 365 admin centerUsers may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)last seen 17:31 UTCunknown
Posted 13 Oct 16:25 UTCUpdated 25 h 41 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're restarting a portion of impacted infrastructure where we've removed traffic and are seeing positive trends towards recovery. We've confirmed through internal testing that this resolves impact for some users and we're monitoring to validate the full recovery of the service. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Next update by: Tuesday, October 13, 2026, at 5:30 PM UTC
Cloudflare saw issues with network performance in IAD that resulted in an increase in errors across Cloudflare services. Users may have experienced increases errors or timeouts reaching Cloudflare’s network or services.
Around it6 other incidents at the same time · 5 earlier incidents
Microsoft 365 admin centerUsers may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)last seen 16:31 UTCunknown
Posted 13 Oct 15:24 UTCUpdated 26 h 42 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We've completed redirecting traffic to healthy infrastructure and are assessing for positive trends towards recovery. We're continuing to investigate additional mitigating actions to expedite remediation. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Next update by: Tuesday, October 13, 2026, at 4:30 PM UTC
Microsoft 365 admin centerUsers may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)last seen 15:25 UTCunknown
Posted 13 Oct 15:10 UTCUpdated 26 h 57 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're redirecting traffic from the underperforming infrastructure to improve service health. We're monitoring to confirm this will fully resolve impact. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC
Microsoft 365 admin centerAdmin center: Service degradationlast seen 15:15 UTCunknown
Posted 13 Oct 14:59 UTCUpdated 27 h 7 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're redirecting traffic from the underperforming infrastructure to improve service health. We're monitoring to confirm this will fully resolve impact. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC
Microsoft 365 admin centerUsers may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)last seen 15:04 UTCunknown
Posted 13 Oct 14:38 UTCUpdated 27 h 29 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We've deployed the traffic optimizations and although we saw a reduction of errors initially, this did not fully resolve the issue. We're continuing to troubleshoot the issue to develop additional mitigation strategies. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Start time: Tuesday, October 13, 2026, at 8:00 AM UTC Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC
13 Oct 10:42 UTCMonitoringVendor has updated to say that their maintenance window will be extended till 13:00 UTC. Customers should continue to expect normal network behaviour and performance through the maintenance window.
13 Oct 06:57 UTCMonitoringImpact observed 06:33 - 06:41 UTC when we observe the vendor restoring the impacted capacity. We believe they temporarily affected all remaining capacity during the restoration and are following up with them. At this point all capacity has been restored and we are monitoring
13 Oct 05:09 UTCMonitoringWe have identified the issue to be related to third-party circuit maintenance, have mitigated the impact that affected traffic, and customers should expect normal network behaviour and performance through the maintenance window. We will update when the maintenance is complete, expected at 10:00 GMT today (2026-10-13).
13 Oct 05:00 UTCMonitoringWe have taken measures to address any impact and are closely monitoring the situation.
13 Oct 04:52 UTCIdentifiedWe are continuing to work on a fix for the issue.
13 Oct 04:52 UTCIdentifiedThe issue has been identified and a fix is being implemented.
13 Oct 04:00 UTCInvestigatingCloudflare is investigating issues with network performance in Ashburn, US (IAD). We are working to analyse and mitigate this problem. More updates to follow shortly.
Around it1 possibly related5 other incidents at the same time · 5 earlier incidents
Microsoft 365 admin centerAdmin center: Service degradationlast seen 14:39 UTCunknown
Posted 13 Oct 13:39 UTCUpdated 28 h 27 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're continuing to apply the aforementioned traffic and performance optimizations with early signals showing signs of recovery. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC
Microsoft 365 admin centerAdmin center: Service degradationlast seen 13:44 UTCunknown
Posted 13 Oct 11:43 UTCUpdated 30 h 23 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services using GSA. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We’ve identified that a section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. We’re applying performance and traffic optimizations to remediate impact and restore connectivity. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted. Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. Next update by: Tuesday, October 13, 2026, at 1:30 PM UTC
Microsoft 365 admin centerAdmin center: Service degradationlast seen 11:48 UTCunknown
Posted 13 Oct 10:34 UTCUpdated 31 h 33 min ago
Admin center
User impact: Users may be unable to access multiple Microsoft 365 services. More info: Impacted services may include, but aren't limited to: - Outlook - Outlook on the web - OneDrive - SharePoint Online - Microsoft Teams - Windows 365 Cloud PCs Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix. Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section may be impacted. Next update by: Tuesday, October 13, 2026, at 11:30 AM UTC
CloudflareCloudflare Network Performance Issuesresolved 23:49 UTC7 h 27 min
Started 12 Oct 16:22 UTCUpdated 42 h 17 min ago
CDN/Cache
This incident has been resolved.
2 earlier updates
12 Oct 17:13 UTCIdentifiedWe are continuing to work on a fix for the issue.
12 Oct 16:22 UTCInvestigatingCloudflare is investigating intermittent performance issues affecting some data centers. Customers may experience errors or increased latency when accessing websites and services proxied through Cloudflare. We are working to mitigate this issue.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Workers - Cron Trigger Activation Issuesresolved 22:20 UTC3 h 10 min
Started 12 Oct 19:09 UTCUpdated 43 h 47 min ago
Workers
This incident has been resolved.
2 earlier updates
12 Oct 19:39 UTCMonitoringA fix has been implemented and we are monitoring the results.
12 Oct 19:09 UTCInvestigatingCloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
Between 12:54 and 21:06 UTC on October 12, 2026, Cloudflare experienced an issue that affected network performance in Seattle. During this time, customers may have experienced degraded network performance. This incident has been resolved.
Around it1 possibly related5 other incidents at the same time · 5 earlier incidents
GitHubIncident with Actions, Pull Requests and Issueslast seen 20:16 UTCunknown
Posted 12 Oct 12:21 UTCUpdated 45 h 51 min ago
Pull 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.
12 earlier updates
12 Oct 19:28 UTCUpdateWeb and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
12 Oct 17:34 UTCUpdateWeb and email notifications continue to be delayed as we work through a backlog of notifications.
12 Oct 15:50 UTCUpdateNotifications have resumed but will continue to be delayed as we work through a backlog.
12 Oct 15:19 UTCUpdateWe have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
12 Oct 14:37 UTCUpdateWe have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
12 Oct 14:36 UTCUpdateThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
12 Oct 14:35 UTCUpdateThe degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
12 Oct 13:38 UTCUpdateOur initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
12 Oct 13:02 UTCUpdatePull Requests is operating normally.
12 Oct 12:57 UTCUpdateWe have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
12 Oct 12:33 UTCUpdateUsers may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.
12 Oct 12:21 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Issues and Pull Requests
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Workers APIresolved 14:05 UTC33 min
Started 12 Oct 13:32 UTCUpdated 2d ago
Workers
This incident has been resolved.
2 earlier updates
12 Oct 13:42 UTCMonitoringA fix has been implemented and we are monitoring the results.
12 Oct 13:32 UTCInvestigatingCloudflare is investigating 504s errors when interacting with Workers API and Workers configuration in the dashboard. Customers might experience some unavailability on Workers endpoints, particularly when deploying a script. Workers that are already running in production are not affected. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
GitLab.comErrors and slow performance on merge requests in the specific groups.last seen 10:19 UTC≥ 2 days
Started 10 Oct 04:49 UTCUpdated 4d ago
WebsiteAPIGit OperationsCI/CD
We have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150
2 earlier updates
10 Oct 06:26 UTCMonitoringWe have applied a mitigation and are seeing sustained recovery in error rates and performance on merge request and pipeline pages for the affected projects. We are continuing to monitor. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150
10 Oct 04:49 UTCInvestigatingWe are investigating reports of errors and slow performance on merge request and pipeline pages for projects in the specific groups. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23150
Around it3 other incidents at the same time · 1 change in the 14 days before
Elsewhere at the same time · within 12 hours of its start
CloudflareCloudflare API service issuesresolved 02:12 UTC7 h 19 min
Started 9 Oct 18:52 UTCUpdated 4d ago
API
This incident has been resolved.
3 earlier updates
9 Oct 21:10 UTCMonitoringA fix has been implemented and we are monitoring the results.
9 Oct 20:58 UTCIdentifiedThe issue has been identified and a fix is being implemented.
9 Oct 18:52 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 it6 other incidents at the same time · 5 earlier incidents
Palo Alto Networks cloud servicesCloud NGFW for AWS: Management Portal access errorslast seen 20:55 UTCunknown
Posted 9 Oct 20:33 UTCUpdated 4d ago
Cloud NGFW for AWSN.Virginia (us-east-1)
Message:This incident has been resolved. Access to the Cloud NGFW for AWS management portal is fully restored.Beginning at approximately 18:05 UTC, a configuration change applied during a routine internal deployment caused the portal's content delivery layer to lose access to its origin, resulting in "Access Denied" errors for users loading the portal. We corrected the access configuration and confirmed the portal is serving normally.
1 earlier update
9 Oct 20:33 UTCInvestigatingWe are investigating reports of "Access Denied" errors when accessing the Cloud NGFW for AWS management portal. Multiple customers are affected. Firewall traffic processing is not impacted - this issue is limited to portal access. We will provide an update within 30 minutes.
CloudflareCloudflare DNS Resolver 1.1.1.1 and Gateway DNS are having issues in SINresolved 19:30 UTC4 h 49 min
Started 9 Oct 14:41 UTCUpdated 4d ago
AsiaGatewayRecursive DNS
This incident has been resolved.
4 earlier updates and 1 change ChangeIntel noticed
9 Oct 16:03 UTCMonitoringA fix has been implemented and we are monitoring the results.
9 Oct 14:42 UTCInvestigatingWe are continuing to investigate this issue.
9 Oct 14:41 UTCInvestigatingCloudflare is aware of, and investigating, an issue which potentially impacts multiple users in SIN that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.
9 Oct 14:41 UTCInvestigatingCloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Singapore that use the 1.1.1.1 public resolver or Gateway DNS. Further detail will be provided as more information becomes available.
9 Oct 14:48 UTC ChangeIntel noticed a new title; it was "Cloudflare DNS Resolver 1.1.1.1 are having issues in SIN"
Around it5 other incidents at the same time · 5 earlier incidents
CloudflareNetwork Performance Issues in Queretaroresolved 19:10 UTC19 min
Started 9 Oct 18:50 UTCUpdated 4d ago
North AmericaNetwork
This incident has been resolved.
2 earlier updates
9 Oct 18:51 UTCMonitoringWe have identified the cause of this issue and have applied a fix. We are currently monitoring the results.
9 Oct 18:50 UTCInvestigatingCloudflare is investigating issues with Network Performance in our Queretaro (QRO) facility. We are working to analyze and mitigate this problem. More updates to follow shortly.
Around it4 other incidents at the same time · 5 earlier incidents
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 · 1 earlier incident · 4 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
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