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
42 incidents · newest first
Today9
GitLab.comGeneral slowness on Gitlab.comlast seen 17:08 UTC≥ 31 min
Started today 16:32 UTCUpdated 47 min ago
WebsiteGit Operations
We identified and resolved an issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are monitoring the platform to ensure the issue remains resolved. More details here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23320
Around it3 other incidents at the same time · 4 earlier incidents · 1 change in the 14 days before
CloudflareSupport Helpdesk Availability Issuesresolved 09:42 UTC6 h 39 min
Started today 03:03 UTCUpdated 7 h 37 min ago
Support Site
This incident has been resolved.
7 earlier updates
today 06:37 UTCMonitoringA fix has been implemented and we are monitoring the results.
today 05:56 UTCIdentifiedWe are continuing to work on a fix for the issue.
today 04:43 UTCIdentifiedWe are continuing to work on a fix for the issue.
today 03:37 UTCIdentifiedSupport portal, live chat support and emergency telephone line are still unavailable due to the ongoing helpdesk provider outage. Customers may experience issues submitting or viewing tickets/chats, and overall response times may be delayed. Customers with urgent issues should revert to using the support email address ([email protected]).
today 03:37 UTCIdentifiedSupport portal, live chat support and emergency telephone line are still unavailable due to the ongoing helpdesk provider outage. Customers may experience issues submitting or viewing tickets/chats, and overall response times may be delayed. Customers with urgent issues should revert to using the support email address ([email protected]).
today 03:03 UTCInvestigatingOur helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time.
today 03:03 UTCInvestigatingOur helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time. For urgent enquiries, Enterprise customers can reach Customer Support on the emergency telephone line.
Around it4 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Access Availability Issuesresolved 09:22 UTC20 min
Started today 09:01 UTCUpdated 7 h 57 min ago
Access
This incident has been resolved.
3 earlier updates
today 09:15 UTCMonitoringA fix has been implemented and we are monitoring the results.
today 09:12 UTCIdentifiedThe issue has been identified and a fix is being implemented.
today 09:01 UTCInvestigatingCloudflare is investigating issues with Cloudflare Access when using Microsoft Entra ID. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Around it2 other incidents at the same time · 5 earlier incidents
GitHubDelayed Actions status check resultslast seen 08:05 UTCunknown
Posted today 07:29 UTCUpdated 9 h 15 min ago
Actions
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.
4 earlier updates
today 07:56 UTCUpdateAs of 07:27 UTC, Actions results are delivering within normal SLOs again.Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future.
today 07:53 UTCMonitoringThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
today 07:31 UTCUpdateWe are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC.Recovery is already being seen but our team is continuing to investigate and monitor performance.
today 07:29 UTCInvestigatingWe are investigating reports of degraded performance for Actions
Around it1 other incident at the same time · 5 earlier incidents
GitHubProject updates delayedlast seen 02:30 UTCunknown
Posted 22 Oct 15:28 UTCUpdated 14 h 50 min ago
Pull RequestsIssues
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.
17 earlier updates and 1 change ChangeIntel noticed
today 00:55 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
22 Oct 23:48 UTCUpdateGitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. We're continuing to work on the remaining delays and monitor recovery.
22 Oct 22:07 UTCUpdateSome GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed.We have seen some recovery, and are working to add more capacity to accelerate the recovery.
22 Oct 20:46 UTCUpdateSome GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed.We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.
22 Oct 19:56 UTCUpdateSome GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.
22 Oct 19:04 UTCUpdateSome updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
22 Oct 18:26 UTCUpdateThe other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
22 Oct 17:43 UTCUpdateWe're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.
22 Oct 17:41 UTCUpdateActions, Issues, Packages and Pull Requests are operating normally.
22 Oct 17:16 UTCUpdateWe're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. We're continuing to work towards full recovery and monitoring for stability.
22 Oct 16:41 UTCUpdateSome users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. We're working through multiple mitigation efforts and continuing to investigate.
22 Oct 16:35 UTCUpdateAPI Requests is operating normally.
22 Oct 16:28 UTCUpdatePackages is experiencing degraded performance. We are continuing to investigate.
22 Oct 16:26 UTCUpdateAPI Requests is experiencing degraded performance. We are continuing to investigate.
22 Oct 16:08 UTCUpdateSome users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and evaluating mitigation options to restore normal service.
22 Oct 15:33 UTCUpdateSome users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and working to restore normal service.
22 Oct 15:28 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Issues and Pull Requests
22 Oct 22:32 UTC ChangeIntel noticed a new title; it was "Errors loading Issues, Pull Requests, and search results"
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareDelayed audit log delivery for WARP and Zero Trust servicesresolved 00:10 UTC6 h 38 min
Started 22 Oct 17:32 UTCUpdated 17 h 9 min ago
Audit LogsZero Trust
This incident has been resolved.
2 earlier updates
22 Oct 17:50 UTCMonitoringA fix has been implemented and we are monitoring the results.
22 Oct 17:32 UTCInvestigatingWe are investigating an issue affecting audit log delivery for WARP API. Audit logs for some customers may be delayed or not delivered, and some dependent services may also be affected. We have identified the cause as a capacity problem in a shared internal data pipeline in our PDX region. Mitigations are in place and the pipeline is partially recovered. We are continuing to monitor and work toward full recovery.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareElevated error rates for Durable Objects in Western Europeresolved 00:09 UTC6 h 17 min
Started 22 Oct 17:51 UTCUpdated 17 h 11 min ago
Durable Objects
This incident has been resolved.
2 earlier updates
22 Oct 18:19 UTCMonitoringA fix has been implemented and we are monitoring the results.
22 Oct 17:51 UTCInvestigatingWe are investigating elevated error rates affecting Durable Objects in Western Europe. Customers may see errors when using Durable Objects and related services. We will post updates as we learn more.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareNetwork Error Log Processing Unavailableresolved 22:00 UTC5 h 30 min
Started 22 Oct 16:30 UTCUpdated 19 h 19 min ago
Logs
This incident has been resolved.
3 earlier updates
22 Oct 21:36 UTCMonitoringA fix has been implemented and we are monitoring the results.
22 Oct 20:08 UTCInvestigatingPartial service restored. Root cause investigation is currently underway.
22 Oct 16:30 UTCInvestigatingSince 20:19 UTC, new Network Error Logging (NEL) reports are not being processed. Reports received during this period will not appear in Network Error Logging analytics. Website traffic and other services are not affected. We are investigating and will provide an update as soon as possible.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareElevated errors for some requests in Ashburn, Virginiaresolved 17:31 UTC29 min
Started 22 Oct 17:01 UTCUpdated 23 h 48 min ago
North AmericaCDN/CacheWorkers
This incident has been resolved.
1 earlier update
22 Oct 17:01 UTCInvestigatingWe are investigating elevated error rates (HTTP 502) for some requests handled by our Ashburn, Virginia data center. Some customers may see failed or intermittent responses for websites and applications, including Workers, served through this location. We are actively investigating and will provide updates as we learn more.
Around it3 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Workers API Latencyresolved 16:15 UTC42 min
Started 22 Oct 15:33 UTCUpdated 25 h 4 min ago
Workers
This incident has been resolved.
2 earlier updates
22 Oct 16:04 UTCMonitoringWe are continuing to monitor for any further issues.
22 Oct 15:33 UTCIdentifiedCloudflare is investigating an increased latency when interacting with Workers API and Workers configuration in the dashboard. Customers might experience longer wait times on Workers endpoints, particularly when deploying a script. Workers that are already running in production are not affected. More updates to follow shortly.
Around it2 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time
GitHubProject updates delayedReported or observed window: 22 Oct 15:28 UTC to today 02:30 UTC
GitHubIncident with Actions Resultslast seen 15:18 UTCunknown
Posted 22 Oct 14:18 UTCUpdated 26 h 2 min ago
Actions
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.
6 earlier updates
22 Oct 15:18 UTCUpdateGitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.
22 Oct 15:17 UTCMonitoringThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
22 Oct 15:06 UTCUpdateWe’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.
22 Oct 14:35 UTCUpdateRepository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.
22 Oct 14:19 UTCUpdateWe’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.
22 Oct 14:18 UTCInvestigatingWe are investigating reports of degraded performance for Actions
22 Oct 01:08 UTCMonitoringA fix has been implemented and we are monitoring the results.
22 Oct 00:23 UTCInvestigatingCloudflare is experiencing network congestion in Portland and Seattle, US. We are working to mitigate impact to Internet users in this region.
Around it1 other incident at the same time · 5 earlier incidents
CloudflareElevated Error Rate for Durable Objects in Lisbonresolved 00:35 UTC44 min
Started 21 Oct 23:50 UTCUpdated 40 h 44 min ago
EuropeDurable Objects
This incident has been resolved.
1 earlier update
21 Oct 23:50 UTCInvestigatingWe are currently investigating an issue where we are observing higher than usual error rates for Durable Objects in our Lisbon (LIS) facility.
Around it1 other incident at the same time · 5 earlier incidents
CloudflareElevated Errors for R2 and Durable Objects in ENAMresolved 21:21 UTC2 h 6 min
Started 21 Oct 19:15 UTCUpdated 43 h 58 min ago
Durable ObjectsR2
This incident has been resolved.
2 earlier updates
21 Oct 19:30 UTCResolvedCloudflare has resolved an issue affecting R2 and Durable Objects in the Eastern North America region. Some customers may have seen elevated errors between approximately 19:19 and 19:28 UTC on October 21, 2026.
21 Oct 19:05 UTCResolvedCloudflare has resolved an issue affecting R2 and Durable Objects in the Eastern North America region. Some customers may have seen elevated errors between approximately 19:02 and 19:05 UTC on October 21, 2026.
Around it5 other incidents at the same time · 5 earlier incidents
CloudflareIncreased Latency in Indiaresolved 19:57 UTC3 h 14 min
Started 21 Oct 16:42 UTCUpdated 45 h 23 min ago
CDN/Cache
This incident has been resolved.
2 earlier updates
21 Oct 18:51 UTCMonitoringWe have identified and implemented a fix for this issue and are currently monitoring the results.
21 Oct 16:42 UTCInvestigatingWe are investigating reports of increased latency affecting some traffic in India. Affected users may experience slower loading times. Our engineering teams are investigating, and we will provide an update as more information becomes available.
Around it6 other incidents at the same time · 5 earlier incidents
GitHubDelays for Pull Requests and Webhook deliverieslast seen 19:22 UTCunknown
Posted 21 Oct 14:52 UTCUpdated 45 h 58 min ago
Pull Requests
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.
14 earlier updates
21 Oct 19:22 UTCUpdatePull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.
21 Oct 18:52 UTCUpdateAudit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates.
21 Oct 18:18 UTCUpdateAudit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow.
21 Oct 17:09 UTCUpdatePull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates.
21 Oct 16:59 UTCUpdateActions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues.
21 Oct 16:57 UTCUpdateActions and Webhooks are operating normally.
21 Oct 16:34 UTCUpdateAudit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more.
21 Oct 16:33 UTCUpdatePull Requests is operating normally.
21 Oct 16:25 UTCUpdateAudit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.
21 Oct 16:17 UTCUpdateAudit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.
21 Oct 15:58 UTCUpdateWe continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.
21 Oct 15:36 UTCUpdateWe are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.
21 Oct 15:15 UTCUpdateActions is experiencing degraded performance. We are continuing to investigate.
21 Oct 14:52 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
Around it5 other incidents at the same time · 5 earlier incidents
2 Apr 18:05 UTCUpdateWe are continuing to monitor for any further issues.
3 Mar 19:06 UTCUpdateWe are continuing to monitor for any further issues.
3 Mar 03:10 UTCUpdateWe are continuing to monitor for any further issues.
2 Mar 22:49 UTCMonitoringAWS Middle East(Bahrain) outage impacting Cloud NGFW Services.We are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region.Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Status Page: https://health.aws.amazon.com/health/status?path=service-historyNext Update: 5:00PM 3/03/2026 UTC.
OpenAIElevated error rates for gpt-5.6-luna API requestslast seen 16:44 UTCunknown
Posted 21 Oct 16:44 UTC
Chat CompletionsResponses
All impacted services have now fully recovered.
2 changes ChangeIntel noticed
21 Oct 16:47 UTC ChangeIntel noticed the text change
21 Oct 15:51 UTC ChangeIntel noticed the text change
Around it3 other incidents at the same time · 5 earlier incidents
Palo Alto Networks cloud services[Cortex XDR / XSIAM / XSOAR 8 / XPANSE/ CLOUD] Degraded Performance in UK Regionlast seen 01:44 UTCunknown
Posted 20 Oct 07:52 UTCUpdated 2d ago
Cortex CloudUnited KindomCortex XDRUnited KingdomCortex XSIAMCortex XSOAR 8.x+1 more
This incident has been resolved.
5 earlier updates and 1 change ChangeIntel noticed
20 Oct 16:06 UTCMonitoringA fix has been implemented and we are monitoring the results.
20 Oct 14:17 UTCUpdateWe continue to see gradual improvement in the situation and are closely monitoring the status
20 Oct 11:50 UTCUpdateWe are seeing gradual improvements in some areas of the UK region and are continuing to work closely with our cloud vendor to mitigate the issue
20 Oct 10:30 UTCUpdateThe issue originates with our cloud vendor, and we are continuing to work closely with them to mitigate its impact.
20 Oct 07:52 UTCIdentifiedWe are currently experiencing degraded performance in the UK region.We have identified the root cause and are implementing a fix.
20 Oct 11:52 UTC ChangeIntel noticed a new title; it was "Degraded Performance in UK Region"
Around it6 other incidents at the same time · 2 earlier incidents · 1 change in the 14 days before
Elsewhere at the same time · within 12 hours of its start
The Customers Portal is loading normally again, and we are no longer observing the intermittent 404 errors affecting sign-in and page loading. A redeployment has completed successfully, and we are monitoring the service for any recurrence before resolving the incident.
3 earlier updates
20 Oct 23:15 UTCInvestigatingWe’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
20 Oct 22:47 UTCInvestigatingWe’re continuing our investigation of 404s on the customers panel. We’ll update you as we learn more.
20 Oct 21:56 UTCInvestigatingWe've investigating 404s on the customers panel. We'll update as we learn more
Around it3 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Secure Web Gateway and DLP enforcement issues for Google Geminiresolved 22:46 UTC26 h 16 min
Started 19 Oct 20:30 UTCUpdated 2d ago
Data Loss Prevention (DLP)Gateway
This incident has been resolved.
2 earlier updates
19 Oct 23:46 UTCIdentifiedWe are rolling out a fix to restore Secure Web Gateway application controls for Google Gemini. Work continues to restore DLP prompt logging and enforcement.
19 Oct 20:30 UTCIdentifiedCloudflare has identified an issue affecting Gateway application controls and Data Loss Prevention (DLP) inspection for certain Google Gemini traffic. We are working on a fix and will provide further updates as more information becomes available.
Around it5 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
CloudflareIssue with Bot management traffic categorization for verified botsresolved 20:16 UTC41 min
Started 20 Oct 19:35 UTCUpdated 2d ago
Bot Management
This incident has been resolved.
1 earlier update
20 Oct 19:35 UTCInvestigatingCloudflare is investigating issues with our Bot Management feature. Customers may observe a limited number of verified bots incorrectly identified as automated traffic
Around it3 other incidents at the same time · 5 earlier incidents
OpenAIAuthentication errors for some userslast seen 17:35 UTCunknown
Posted 20 Oct 17:35 UTC
Login
On October 20, from 9:35 to 10:35 a.m. PDT, some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex. We rolled back a configuration change, and service was restored.
2 changes ChangeIntel noticed
21 Oct 23:19 UTC ChangeIntel noticed the text change
21 Oct 23:04 UTC ChangeIntel noticed a new title; it was "Authentication errors for some API users"
Around it3 other incidents at the same time · 5 earlier incidents
Palo Alto Networks cloud servicesWildFire Issuelast seen 16:15 UTCunknown
Posted 20 Oct 06:52 UTCUpdated 3d ago
WildFireWildFire UK CloudUK
This incident has been resolved.
7 earlier updates
20 Oct 16:10 UTCMonitoringA fix has been implemented and we are monitoring the results.
20 Oct 16:06 UTCIdentifiedThe issue has been identified and a fix is being implemented.
20 Oct 15:24 UTCUpdateAs per GCP most of their services are up in europe-west2 region. But we still see some n/w failures. We are following up with GCP.
20 Oct 13:08 UTCUpdateGCP is still continuing investigating the issue -https://status.cloud.google.com/regional/europe#status-table
20 Oct 09:46 UTCUpdateGCP is still continuing investigating the issue. There is no ETA yet.
20 Oct 07:37 UTCUpdateThis is due to an outage from GCP.
20 Oct 06:52 UTCInvestigatingWildFire is currently experiencing an issue in UK Cloud. We are actively working on this issue and will provide another update by 9:00 AM UTC with further details. Customer Impact: Delay in sample processing and client disconnection errorsWorkaround: N/A
Around it6 other incidents at the same time · 2 earlier incidents · 1 change in the 14 days before
Palo Alto Networks cloud servicesWildFire Issuelast seen 12:24 UTCunknown
Posted 20 Oct 11:28 UTCUpdated 3d ago
GermanyWildFireWildFire Germany Cloud
This incident has been resolved.
3 earlier updates
20 Oct 12:22 UTCMonitoringA fix has been implemented and we are monitoring the results.
20 Oct 12:20 UTCIdentifiedThe issue has been identified and a fix is being implemented.
20 Oct 11:28 UTCInvestigatingWildFire is currently experiencing an issue in Germany Cloud. We are actively working on this issue and will provide another update by 13:30 UTC with further details. Customer Impact: Frequent disconnection and Delay in Sample processingWorkaround: N/A
Around it4 other incidents at the same time · 2 earlier incidents · 1 change in the 14 days before
GitLab.comIntermittent 500 on GitLab.comlast seen 10:00 UTC≥ 2 h 46 min
Started 20 Oct 07:08 UTCUpdated 3d ago
Website
This issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
2 earlier updates and 1 change ChangeIntel noticed
20 Oct 07:37 UTCMonitoringThis issue affects projects and groups using GitLab Secrets Manager. Users saw HTTP 500 errors, not 503 as previously stated. A mitigation has been applied and we're monitoring. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
20 Oct 07:08 UTCInvestigatingWe're investigating intermittent HTTP 503 errors when opening project pages. At this time, this issue only occurs in specific projects. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23288
20 Oct 07:32 UTC ChangeIntel noticed a new title; it was "Intermittent 503 on GitLab.com"
Around it5 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time
Palo Alto Networks cloud servicesWildFire IssueReported or observed window: 20 Oct 06:52 UTC to 20 Oct 16:15 UTC
CloudflareCloudflare Zero Trust connectivityresolved 06:32 UTC3 h 11 min
Started 20 Oct 03:20 UTCUpdated 3d ago
DashboardZero Trust
This incident has been resolved.
9 earlier updates
20 Oct 06:14 UTCMonitoringThe Cloudflare Access API has been fully restored, with error rates and latency returning to normal levels. We continue to monitor these services.
20 Oct 05:46 UTCMonitoringThe Cloudflare Access API continues to experience higher-than-normal error rates and increased latency. We are working to resolve the remaining API issues. Edge functionality, including Access logins and Cloudflare Secure Web Gateway connectivity, has been fully restored. We continue to monitor these services.
20 Oct 04:44 UTCMonitoringA fix has been implemented and we are monitoring the results.
20 Oct 04:40 UTCIdentifiedThe issue has been identified and a fix is being implemented.
20 Oct 04:22 UTCInvestigatingWe are continuing to investigate the issue.
20 Oct 04:09 UTCInvestigatingWe are continuing to investigate the issue.
20 Oct 03:47 UTCInvestigatingWe are continuing to investigate the issue.
20 Oct 03:20 UTCInvestigatingCloudflare is investigating an issue with traffic that goes through Cloudflare One Gateway when an identity policy is present in the policy decision. This impacts all onramps to Cloudflare One Gateway. Cloudflare One Gateway policies with no identity policy are unaffected. We are also seeing impact to the Cloudflare Dashboard and are investigating further.
20 Oct 03:20 UTCInvestigatingCloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust. Cloudflare WARP and Zero Trust users may experience connectivity issues or a degraded Internet experience.
Around it2 other incidents at the same time · 5 earlier incidents
GitHubDegraded availability for GitHub Actions, GitHub Pages and Webhookslast seen 16:56 UTCunknown
Posted 19 Oct 15:49 UTCUpdated 4d ago
WebhooksActionsPages
On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. Impact - Workflow status updates, logs, and checks were delayed. - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed. - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. Pages deployments and webhooks generated by Actions runs were delayed. An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts. We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capaci…
6 earlier updates
19 Oct 16:56 UTCMonitoringActions, Pages and Webhooks are operating normally.
19 Oct 16:56 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.
19 Oct 16:30 UTCUpdateWe’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.
19 Oct 15:56 UTCUpdateWe’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. Customers may experience delays in workflow processing, site builds and webhook delivery.
19 Oct 15:50 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
19 Oct 15:49 UTCInvestigatingWe are investigating reports of degraded performance for Actions and Pages
Around it1 other incident at the same time · 5 earlier incidents
Due to unexpected prefix withdrawals on peering links in IAD and CMH (Ashburn, Virginia and Columbus, Ohio, in the United States) on an external provider, customers experienced increased latency and timeouts from 08:00 to 08:50 UTC. Services have fully normalized following the restoration of prefix advertisements.
Around it1 other incident at the same time · 5 earlier incidents
CloudflareCloudflare Fedramp Dashboard and Accessresolved 19:09 UTC1 h 12 min
Started 16 Oct 17:56 UTCUpdated 6d ago
AccessFedRamp Dashboard
This incident has been resolved.
5 earlier updates and 1 change ChangeIntel noticed
16 Oct 19:02 UTCMonitoringA fix has been implemented and we are monitoring the results.
16 Oct 18:47 UTCIdentifiedThe issue has been identified and a fix is being implemented.
16 Oct 18:15 UTCInvestigatingCloudflare is investigating issues with accessing the Cloudflare Fedramp Dashboard and related Cloudflare Access services. Logging into dashboards and applications protected by Fedramp Access is impacted. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Edge. Cloudflare has identified the issue and is working on a fix.
16 Oct 17:56 UTCInvestigatingCloudflare is investigating issues with accessing the Cloudflare Fed Dashboard. 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 Fed Dashboard are impacted as requests might fail and/or errors may be displayed. Cloudflare has identified the issue and is working on a fix. Impacted services
16 Oct 17:56 UTCInvestigatingCloudflare is investigating issues with accessing the Cloudflare Fedramp Dashboard and related Cloudflare Access services. Logging into dashboards and applications protected by Fedramp Access is impacted. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Edge. Cloudflare has identified the issue and is working on a fix.
16 Oct 18:16 UTC ChangeIntel noticed a new title; it was "Cloudflare Fed Dashboard"
Around it2 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time
GitLab.com503s on GitLab.comReported or observed window: 16 Oct 16:10 UTC to 16 Oct 17:25 UTC
GitLab.com503s on GitLab.comlast seen 17:25 UTC≥ 1 h 10 min
Started 16 Oct 16:10 UTCUpdated 7d ago
WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab Pages+17 more
We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
4 earlier updates
16 Oct 16:52 UTCIdentifiedMost services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
16 Oct 16:40 UTCIdentifiedWe have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
16 Oct 16:25 UTCInvestigatingWe are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
16 Oct 16:10 UTCInvestigatingWe are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.
Around it1 other incident at the same time · 5 earlier incidents
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