Incident History

Cloudflare WARP: Issues with msn.com

This incident has been resolved.

1770655157 - 1770715681 Resolved

Cloudflare GraphQL API Issue

Between 2/7/2026 10:30 - 2/9/2026 03:20 UTC some customers may have experienced elevated timeouts using some GraphQL datasets. This issue does not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.

1770614007 - 1770614007 Resolved

Workers KV

Cloudflare identified an issue in our Cloudflare One Gateway product that resulted in an increase level of errors. Customers that rely on identity based traffic policies in Zero Trust may have experience errors during this time.

Impacted products: Zero Trust, Browser Isolation, WARP, Access

Start of Impact: 16:42 UTC End of Impact: 16:52 UTC

1770570889 - 1770570889 Resolved

Increased HTTP 500 Errors

This incident has been resolved.

1770430383 - 1770439410 Resolved

Elevated errors in Ashburn, VA

Between 02:50-03:00 UTC customers reaching Ashburn, VA would have experienced an elevated number of errors.

1770348462 - 1770348462 Resolved

DNS Resolver issue

This incident has been resolved.

1770261359 - 1770274132 Resolved

Cloudflare DNS

This incident has been resolved.

1770228996 - 1770230408 Resolved

Newark (EWR) Datacenter Increase in HTTP Request latency

This incident has been resolved.

1770226196 - 1770241769 Resolved

Cloudflare Stream Issues

This incident has been resolved.

1770223515 - 1770226634 Resolved

Newark (EWR) Datacenter Increase in HTTP Request latency

Cloudflare has detected and resolved an issue regarding elevated latency affecting a subset of HTTP requests in Newark, NJ. The issue occurred between 15:00 and 20:20 UTC on February 3rd. Performance has returned to baseline levels, and we are continuing to monitor the region to ensure stability.

1770206027 - 1770206027 Resolved
⮜ Previous Next ⮞