We are investigating reports of degraded performance for Actions

Cloudflare is investigating issues with Network Performance in Osaka, Japan datacenter (KIX). We are working to analyze and mitigate this problem. More updates to follow shortly.

The Cloudflare Workers API is experiencing increased errors and changes to Cron Triggers may be delayed. Already deployed Workers and existing Cron Triggers are unaffected.

We are investigating reports of impacted performance for some GitHub services.

Customers may notice that when a request is blocked by schema validation, the associated reason or description is not being displayed within the dashboard.

We are actively investigating reports that customers may be experiencing issues . Our engineers are working to resolve the issue and will provide another update shortly.

Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Customers may be seeing an increase of errors using AI Gateway. We are working to identify the root cause and will provide updates as they become available.

The request trace feature is failing for some cacheable assets. Failing requests are returning 400 Bad Request.

Cloudflare is investigating an increased rate of HTTP 530 errors specifically affecting ".cloud" and ".tech" traffic routed through our Atlanta (ATL) data center. We are working to identify the root cause and will provide updates as they become available

Cloudflare is investigating an issue causing increased latency for the Workers API

We confirm there is a problem with our main HiBob application, and we’re working to resolve it.

We are aware that customers are receiving authorization failure errors when trying to connect to the Slack MCP server. We are currently investigating the issue and will provide an update as soon as more information becomes available. We're very sorry for any inconvience this may be causing your business. 

We are investigating reports of impacted performance for some GitHub services.

Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. Customer Symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

Customers may experience some delay in ingestion and alerts. We are currently burning the backlog

Cloudflare is investigating issues with Network Performance for customers in the Jakarta area We are working to analyze and mitigate this problem. More updates to follow shortly.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of degraded performance for Git Operations

Cloudflare Pages API is seeing increased error rate. This affects the Workers & Pages section in the Cloudflare Dashboard, as well as Workers Builds. Deployed Workers and Pages projects are unaffected

We are investigating reports of impacted performance for some GitHub services.

Cloudflare is investigating an increased rate of HTTP 530 errors specifically affecting traffic routed through our Atlanta (ATL) data center. We are working to identify the root cause and will provide updates as they become available.

Cloudflare is investigating network performance issues that may impact a subset of users in Mumbai, India. Some users may experience increased latency or intermittent errors. We are actively working to mitigate this problem. More updates to follow shortly.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating an issue where processing of Load Balancing health events is degraded, leading to delays in notifications and analytics regarding Load Balancing health monitoring, as well as delays in steering decisions for some customers.

We have mitigated an issue in one of the Cloudflare Los Angeles POPs causing performance degradation between 20:32 to 20:53 UTC

Cloudflare is investigating reports of increased 300* errors for WAF Challenges, and Turnstile Challenges

Cloudflare has identified and resolved an issue impacting the Pages API, Pages Builds and Workers Builds. Customers may have experienced an elevated number of 500s or build failures. Customers may have seen impact from 18th March 2026 20:22 UTC to 20:50 UTC

Investigating issues with logging into the Dashboard silently failing, especially via SSO

Cloudflare is investigating issues with Cloudflare Dashboard and related 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 Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.

We are investigating reports of degraded performance for Webhooks

Some R2 customers may experience incomplete assets and broken connections during 206 responses

Users of GraphQL API may experience issues reaching certain datasets in US region. The team is investigating the issue with the underlying platform. Data might be delayed.

We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Cloudflare is investigating an increased level of HTTP 520 errors, specifically affecting HEAD requests. We are working to analyse and mitigate this problem. More updates to follow shortly.