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
53 incidents · newest first
Today6
CloudflareCloudflare Secure Web Gateway and DLP enforcement issues for Google Geminiresolved 22:46 UTC26 h 16 min
Started 19 Oct 20:30 UTCUpdated 17 min 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 it4 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 today 19:35 UTCUpdated 2 h 47 min ago
Bot Management
This incident has been resolved.
1 earlier update
today 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 it2 other incidents at the same time · 5 earlier incidents
Palo Alto Networks cloud servicesWildFire Issuelast seen 16:15 UTCunknown
Posted today 06:52 UTCUpdated 6 h 49 min ago
WildFireWildFire UK CloudUK
This incident has been resolved.
7 earlier updates
today 16:10 UTCMonitoringA fix has been implemented and we are monitoring the results.
today 16:06 UTCIdentifiedThe issue has been identified and a fix is being implemented.
today 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.
today 13:08 UTCUpdateGCP is still continuing investigating the issue -https://status.cloud.google.com/regional/europe#status-table
today 09:46 UTCUpdateGCP is still continuing investigating the issue. There is no ETA yet.
today 07:37 UTCUpdateThis is due to an outage from GCP.
today 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 it5 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 today 11:28 UTCUpdated 10 h 40 min ago
GermanyWildFireWildFire Germany Cloud
This incident has been resolved.
3 earlier updates
today 12:22 UTCMonitoringA fix has been implemented and we are monitoring the results.
today 12:20 UTCIdentifiedThe issue has been identified and a fix is being implemented.
today 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 it3 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 today 07:08 UTCUpdated 15 h 26 min 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
today 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
today 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
today 07:32 UTC ChangeIntel noticed a new title; it was "Intermittent 503 on GitLab.com"
Around it4 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Zero Trust connectivityresolved 06:32 UTC3 h 11 min
Started today 03:20 UTCUpdated 16 h 26 min ago
DashboardZero Trust
This incident has been resolved.
9 earlier updates
today 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.
today 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.
today 04:44 UTCMonitoringA fix has been implemented and we are monitoring the results.
today 04:40 UTCIdentifiedThe issue has been identified and a fix is being implemented.
today 04:22 UTCInvestigatingWe are continuing to investigate the issue.
today 04:09 UTCInvestigatingWe are continuing to investigate the issue.
today 03:47 UTCInvestigatingWe are continuing to investigate the issue.
today 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.
today 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 it1 other incident 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 30 h 8 min ago
WebhooksActionsPages
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
19 Oct 16:56 UTCMonitoringActions, Pages and Webhooks are operating normally.
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
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.
CloudflareCloudflare Fedramp Dashboard and Accessresolved 19:09 UTC1 h 12 min
Started 16 Oct 17:56 UTCUpdated 4d 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 it1 other incident 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 4d 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.
GitLab.comGitLab.com CI/CD Incidentlast seen 13:23 UTC≥ 1 h 45 min
Started 16 Oct 11:33 UTCUpdated 4d ago
CI/CD
We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.
2 earlier updates
16 Oct 11:33 UTCInvestigatingWe’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
16 Oct 11:33 UTCInvestigatingWe’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
Around it3 other incidents at the same time · 5 earlier incidents
Between 12:58 and 13:03 UTC, Cloudflare experienced an elevated rate of HTTP 5xx errors in Ashburn (IAD). The incident is now resolved, and systems are fully operational.
Around it1 other incident at the same time · 5 earlier incidents
Elsewhere at the same time
GitLab.comGitLab.com CI/CD IncidentReported or observed window: 16 Oct 11:33 UTC to 16 Oct 13:23 UTC
CloudflareCloudflare Dashboard sign up issuesresolved 11:24 UTC1 h 9 min
Started 16 Oct 10:15 UTCUpdated 4d ago
Dashboard
This incident has been resolved.
3 earlier updates
16 Oct 11:12 UTCMonitoringWe are continuing to monitor for any further issues.
16 Oct 10:46 UTCIdentifiedWe are continuing to work on a fix for the issue.
16 Oct 10:15 UTCInvestigatingCloudflare is aware of and investigating an issue where some users are unable to sign up to the Cloudflare Dashboard. We are working to mitigate the problem and will update shortly.
Around it2 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Access Availability Issuesresolved 09:59 UTC38 min
Started 16 Oct 09:20 UTCUpdated 4d ago
Access
This incident has been resolved.
3 earlier updates
16 Oct 09:41 UTCMonitoringWe are continuing to monitor for any further issues.
16 Oct 09:21 UTCIdentifiedThe issue has been identified and a fix is being implemented.
16 Oct 09:20 UTCInvestigatingCloudflare is investigating issues with Cloudflare Access after login. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
CloudflareNetwork Performance Issues in Thailandresolved 07:30 UTC42 min
Started 16 Oct 06:48 UTCUpdated 4d ago
Network
Cloudflare investigated and resolved issues with network performance in Bangkok, Thailand. There may have been elevated response times and an increase in 5xx errors between 06:48 and 07:30 UTC. This has been resolved and normal operations have resumed.
CloudflareNetwork issues in Incheon (ICN)resolved 02:11 UTC58 min
Started 16 Oct 01:13 UTCUpdated 4d ago
Network
Between 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since returned to normal baselines, and the issue is now fully resolved.
Around it2 other incidents at the same time · 5 earlier incidents
CloudflareWorkers Cron Triggers issuesresolved 01:06 UTC1 h 4 min
Started 16 Oct 00:01 UTCUpdated 4d ago
Workers
Workers Cron Triggers have stabilized
2 earlier updates
16 Oct 00:54 UTCMonitoringWe are continuing to monitor for any further issues.
16 Oct 00:01 UTCIdentifiedCloudflare is investigating issues with Workers Cron Triggers. A subset of customers may not being their cron get invoked. We are working to mitigate this problem. More updates to follow shortly.
Around it1 other incident at the same time · 5 earlier incidents
CloudflareAudit Logs v2 ingestion is missing multiple Cloudflare productsresolved 00:36 UTC2 days
Started 13 Oct 10:14 UTCUpdated 4d ago
Audit Logs
This incident has been resolved.
2 earlier updates
13 Oct 11:45 UTCMonitoringWe are continuing to monitor for any further issues.
13 Oct 10:14 UTCIdentifiedSince 2026-10-12 at 16:57:24 UTC, audit logs from multiple Cloudflare products are not ingested into the audit logs v2 database anymore. V1 audit logs are not affected
Around it6 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
CloudflareNetwork Performance Issues in Eastern North Americaresolved 21:38 UTC49 min
Started 15 Oct 20:48 UTCUpdated 5d ago
North AmericaNetwork
This incident has been resolved.
2 earlier updates
15 Oct 21:24 UTCMonitoringOur engineering teams are continuing to remediate the issue. No customer impact is being seen at this time.
15 Oct 20:48 UTCIdentifiedCloudflare has identified an issue with network performance affecting our Ashburn (IAD) and Newark (EWR) facilities. Customers may observed elevated latency and/or errors for traffic handled by these facilities until the issue is resolved. We are working on a fix for this issue and will have more updates shortly.
Around it4 other incidents at the same time · 5 earlier incidents
CloudflarePages.dev sites experiencing availability issues in Norwayresolved 21:26 UTC4 h 43 min
Started 15 Oct 16:42 UTCUpdated 5d ago
Pages
This incident has been resolved.
3 earlier updates
15 Oct 21:15 UTCMonitoringWe are continuing to monitor for any further issues.
15 Oct 20:52 UTCIdentifiedWe are continuing to work on a fix for the issue.
15 Oct 16:42 UTCInvestigatingCloudflare is aware of and is investigating reports that pages.dev subdomains are not available in Norway. Pages sites that use Custom Domains are not impacted. We will update this as more information become available.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareIncreased HTTP 502 Errorsresolved 20:39 UTC9 h 51 min
Started 15 Oct 10:47 UTCUpdated 5d ago
CDN/CacheNetwork
This incident has been resolved.
3 earlier updates
15 Oct 11:41 UTCMonitoringWe are continuing to monitor for any further issues.
15 Oct 11:27 UTCIdentifiedWe are continuing to work on a fix for the issue.
15 Oct 10:47 UTCInvestigatingCloudflare is investigating an increased level of HTTP 502 errors. 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
GitLab.comCI/CD Job Delays on GitLab.comlast seen 19:55 UTC≥ 3 h 32 min
Started 15 Oct 16:18 UTCUpdated 5d ago
CI/CDCI/CD - Hosted runners on LinuxCI/CD - Hosted runners on WindowsCI/CD - Hosted runners on macOSCI/CD - Hosted runners for GitLab community contributions
We have identified the cause of the issue causing CI/CD delays on GitLab.com and are working to take corrective actions. The issue may persists intermittently as we do so. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234
2 earlier updates
15 Oct 16:19 UTCInvestigatingWe are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234
15 Oct 16:18 UTCInvestigatingWe are investigating an issue affecting GitLab.com CI/CD. Some pipelines may remain in the created state for an extended period or fail to start, causing CI/CD workflows to stall. More Details at https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234
Around it6 other incidents at the same time · 5 earlier incidents
We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.
4 earlier updates
15 Oct 18: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.
15 Oct 18:53 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
15 Oct 18:34 UTCUpdateCCA Automations are experiencing delays when users start an Automation
15 Oct 18:31 UTCInvestigatingWe are investigating reports of impacted performance for some GitHub services.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareDNS Update Delaysresolved 18:19 UTC2 h 45 min
Started 15 Oct 15:33 UTCUpdated 5d ago
DNS Updates
This incident has been resolved.
3 earlier updates
15 Oct 16:27 UTCMonitoringA fix has been implemented and we are monitoring the results.
15 Oct 16:13 UTCIdentifiedThe issue has been identified and a fix is being implemented.
15 Oct 15:33 UTCInvestigatingCloudflare is investigating delays in propagation of updates to DNS records in multiple regions. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareIncreased Errors for Durable Objectsresolved 18:00 UTC2 h 23 min
Started 15 Oct 15:37 UTCUpdated 5d ago
AI SearchArtifactsContainersD1Durable ObjectsWorkers Assets+1 more
This incident has been resolved.
2 earlier updates
15 Oct 16:12 UTCIdentifiedThe issue has been identified and a fix is being implemented.
15 Oct 15:37 UTCInvestigatingCloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in DEN. 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
CloudflareDNS Update DelaysStated window: 15 Oct 15:33 UTC to 15 Oct 18:19 UTC
CloudflareNetwork Performance Issues in Londonresolved 17:46 UTC13 min
Started 15 Oct 17:33 UTCUpdated 5d ago
EuropeDurable ObjectsR2RealtimeKit
This incident has been resolved.
1 earlier update
15 Oct 17:33 UTCIdentifiedWe are working to mitigate impact to Internet users in this region. Cloudflare has identified the issue and is implementing a fix.
Around it6 other incidents at the same time · 5 earlier incidents
Cloudflare resolved an incident where we observed network performance issues in our Kuala Lumpur (KUL) facility. Customers may have observed elevated error rates and/or increased latency today, 2026-10-15, between approximately 16:10 and 16:15 UTC.
Around it4 other incidents at the same time · 5 earlier incidents
CloudflareIncreased Errors for Durable Objects and Downstream Services in Western Europeresolved 10:02 UTC43 min
Started 15 Oct 09:18 UTCUpdated 5d ago
Durable Objects
This incident has been resolved.
1 earlier update
15 Oct 09:18 UTCMonitoringCloudflare is investigating issues causing an increase of errors for Durable Objects and downstream services in Western Europe from 09:00 UTC. This is currently recovering. More updates to follow shortly.
Around it4 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Workers AI Issuesresolved 09:37 UTC2 h 26 min
Started 15 Oct 07:10 UTCUpdated 5d ago
Workers AI
This incident has been resolved.
2 earlier updates
15 Oct 07:57 UTCMonitoringWe are continuing to monitor for any further issues.
15 Oct 07:10 UTCInvestigatingCloudflare has identified an issue whereby customers might experience errors from inference requests to certain models using Workers AI. These are the list of impacted model: @cf/deepseek-ai/deepseek-v4-flash-0731 @cf/deepseek-ai/deepseek-v4-pro-0813 @cf/zai-org/glm-5.2 @cf/zai-org/glm-5.3 @cf/zai-org/glm-5.3-flash We are working to mitigate this problem. More updates to follow shortly.
Around it6 other incidents at the same time · 5 earlier incidents
CloudflareElevated Errors in China Network Colosresolved 09:28 UTC5 days
Started 10 Oct 04:13 UTCUpdated 5d ago
China Network
This incident has been resolved.
5 earlier updates
14 Oct 17:50 UTCMonitoringA fix has been implemented and we are monitoring the results.
12 Oct 15:33 UTCIdentifiedWe have identified that increased latency and 5xx errors affecting certain China Network colos are caused by cross-border routing instability in the China network. We are actively working to mitigate impact for affected customers by adjusting traffic routing, and are continuing to work with our network partners on a resolution. Customers experiencing issues may contact Cloudflare Support.
12 Oct 04:23 UTCIdentifiedWe are investigating reports of degraded performance for traffic traversing the public internet between certain cities and provinces in mainland China and origin servers located outside the region. The impact is being reported across multiple ISPs and manifests as slower speeds or intermittent timeouts. While this congestion occurs upstream of Cloudflare's network, our engineering team is actively working to mitigate the effects. Intermittent 524 timeout errors is expected to continue due to ongoing congestion. While there is no fixed timeline for full resolution, as there are dependencies outside our network, we are taking steps to reduce customer impact.
10 Oct 05:48 UTCIdentifiedThe issue has been identified and a fix is being implemented.
10 Oct 04:13 UTCInvestigatingWe are investigating a spike in errors observed in our China colos.
Around it3 other incidents at the same time · 5 earlier incidents
Elsewhere at the same time · within 12 hours of its start
Mitigations have been applied to customers.gitlab.com, and we are monitoring service availability. Intermittent errors may continue to affect Customers Portal pages and GitLab.com groups that rely on the portal for subscription-related operations. We are continuing to investigate the underlying cause and will provide another update when more information is available. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23240
4 earlier updates and 1 change ChangeIntel noticed
15 Oct 05:50 UTCInvestigatingNo material updates to report. We'll share another update when we have more information.
15 Oct 05:27 UTCInvestigatingNo material updates to report. We are still investigating the root cause.
15 Oct 05:10 UTCInvestigatingWe have received reports that some groups on GitLab.com are experiencing HTTP 500 errors because the group is unable to sync with customers.gitlab.com. We are continuing to investigate the issue.
15 Oct 04:43 UTCInvestigatingWe're investigating an issue that's stopping pages on customers.gitlab.com from loading. Purchasing, renewing, and managing subscriptions may be affected. GitLab.com itself is not affected.
15 Oct 07:41 UTC ChangeIntel noticed a new title; it was "Error loading customers.gitlab.com"
Around it5 other incidents at the same time · 4 earlier incidents · 1 change in the 14 days before
CloudflareDegraded performance for Cloudflare Browser Runresolved 06:46 UTC48 min
Started 15 Oct 05:57 UTCUpdated 5d ago
Browser Run
This incident has been resolved.
3 earlier updates
15 Oct 06:44 UTCMonitoringWe are continuing to monitor for any further issues.
15 Oct 06:37 UTCIdentifiedWe are continuing to work on a fix for the issue.
15 Oct 05:57 UTCInvestigatingCloudflare is investigating an issue causing degraded performance for Browser Run. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Around it3 other incidents at the same time · 5 earlier incidents
CloudflareCloudflare Workers - Cron Trigger Activation Issuesresolved 01:29 UTC19 h 53 min
Started 14 Oct 05:36 UTCUpdated 5d ago
Workers
Workers Cron Trigger backlogs have cleared and appear healthy. Cron Trigger schedules should be executing as expected. Some schedule redeploys may be required for a small fraction of Workers who were impacted during the incident.
3 earlier updates
14 Oct 08:14 UTCMonitoringWe are continuing to monitor for any further issues.
14 Oct 07:23 UTCIdentifiedA fix has been identified and is underway
14 Oct 05:36 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
Elsewhere at the same time · within 12 hours of its start
Palo Alto Networks cloud servicesAI Runtime Security (AIRS) Cloud Degraded Performance (AIRS API Intercept URL Filtering) in USlast seen 01:26 UTCunknown
Posted 15 Oct 00:51 UTCUpdated 5d ago
United States - AmericasUnited StatesAI Runtime Security Cloud
The issue affecting the URL Filtering Detection Service in AI Runtime Security API has been resolved. URL filtering detection features has worked normally since 01:07 UTC.Customer Impact: From about 00:00 UTC to 01:07 UTC on October 15, 2026, URL content in prompts and responses may not have been categorized or blocked. Scan requests kept processing and returned successful responses, and all other detections worked as normal. Other regions were not affected.We apologize for the inconvenience and will review how to prevent this from happening again.
1 earlier update
15 Oct 00:51 UTCInvestigatingWe are currently investigating this issue with URL Filtering Detection Service, that affects detection features offered by AI Runtime Security API.Customer Impact: Scan requests are still being processed and return successful responses, and all other detections work as normal. But URL content in prompts and responses may not be categorized or blocked while this lasts. Other regions are not affected.We'll post another update within 60 minutes, or sooner once service is restored.
Around it3 other incidents at the same time · 1 earlier incident · 1 change in the 14 days before
GitLab.comIncrease of HTTP 50X errors on GitLab.comlast seen 23:43 UTC≥ 40 h 28 min
Started 13 Oct 07:10 UTCUpdated 6d ago
WebsiteAPIGit OperationsPackage RegistryContainer RegistryGitLab Duo
Monitoring confirms that GitLab.com services have remained stable. We are continuing to monitor for any recurrence of the issues before marking this incident as resolved.
4 earlier updates
13 Oct 07:59 UTCMonitoringWe are seeing improvements across all services on GitLab.com. We are resuming our investigation on identifying the root cause.
13 Oct 07:48 UTCInvestigatingGeneral GitLab.com service continues to improve. We're now focused on restoring Duo services.
13 Oct 07:30 UTCInvestigatingWe are seeing an improvement in errors rates in our monitoring, starting from 07:14 UTC. We are still identifying the root cause.
13 Oct 07:10 UTCInvestigatingWe are currently investigating reports of an increase of HTTP 50X errors on GitLab.com
Around it6 other incidents at the same time · 1 earlier incident · 2 changes in the 14 days before
Elsewhere at the same time · within 12 hours of its start
GitLab.comGitLab.com CI/CD pipelines delayed or not startinglast seen 18:36 UTC≥ 3 h 58 min
Started 14 Oct 14:33 UTCUpdated 6d ago
CI/CD
We identified the issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively working to resolve the issue. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
4 earlier updates and 1 change ChangeIntel noticed
14 Oct 16:40 UTCInvestigatingWe are investigating an issue affecting GitLab.com and general site errors and slowness related to the initial issue. We are actively investigating the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
14 Oct 15:22 UTCInvestigatingWe are investigating an issue affecting GitLab.com CI/CD. Merge train, scheduled, and child/downstream pipelines may be delayed, remain in a created or pending state, or fail to start. Mergeability analysis and webhook notifications may also be delayed. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
14 Oct 14:33 UTCInvestigatingWe are investigating an issue affecting GitLab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23190
14 Oct 14:33 UTCInvestigatingWe are investigating an issue affecting GitLab.com merge trains. Some merge train pipelines may remain in the created state for an extended period or fail to start, causing merge trains and related CI/CD workflows to stall. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
14 Oct 15:24 UTC ChangeIntel noticed a new title; it was "Merge train pipelines delayed or not starting"
Around it6 other incidents at the same time · 3 earlier incidents · 2 changes in the 14 days before
Cisco MerakiCloud Communication Interruptionlast seen 17:10 UTCunknown
Posted 14 Oct 13:58 UTCUpdated 6d 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
14 Oct 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.
14 Oct 14:15 UTCIdentifiedWe have identified the problem and are working to remediate it now. We will provide further updates as the incident progresses.
14 Oct 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
14 Oct 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 it3 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 14 Oct 07:43 UTCUpdated 6d 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
14 Oct 04:54 UTCMonitoringA fix has been implemented and we are monitoring the results.
14 Oct 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 14 Oct 04:55 UTCUpdated 6d 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 6d 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
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