1. Home
  2. Companies
  3. Cloudflare
  4. Outage Map
Cloudflare

Cloudflare Outage Map

The map below depicts the most recent cities worldwide where Cloudflare users have reported problems and outages. If you are having an issue with Cloudflare, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Cloudflare users affected:

Less
More
Check Current Status

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Paris, Île-de-France 1
New York City, NY 1
Manchester, England 1
Angers, Pays de la Loire 1
London, England 1
Check Current Status

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Cloudflare Issues Reports

Latest outage, problems and issue reports in social media:

  • sharanry
    Sharan Yalburgi (@sharanry) reported

    love @Cloudflare agents infra but why are your workers to so slow to spin up sometimes?

  • pixelpatchit
    DR.PIXEL (@pixelpatchit) reported

    Swapdesk Alpha: DNS Expansion and Reliability Improvements As Swapdesk Alpha continues to mature, we plan to expand beyond our current Cloudflare and Google DNS support by adding additional DNS provider options. These providers have given us a strong foundation during the alpha phase, allowing us to focus on building and testing core functionality while maintaining reliable connectivity. During the THORChain swap process, users may occasionally experience intermittent connection issues while the application is retrieving required swap information, such as the deposit address needed to complete a transaction. These issues are not consistent and do not occur during every swap, but when they happen, they can create confusion because they occur during an important step in the transaction flow. It is important to clarify that an error message during this stage does not automatically mean a transaction has failed or that funds are at risk. In many cases, the issue is related to communication between the application and supporting services, which may include DNS resolution, API availability, network routing, or other connectivity factors. To improve reliability, future versions of Swapdesk Alpha will introduce broader DNS support, improved fallback handling, and additional resilience measures. The goal is to provide users with a smoother experience, reduce unnecessary interruptions, and ensure that Swapdesk remains dependable as adoption grows. We appreciate the feedback from early users helping identify areas where reliability and user experience can continue to improve.

  • grimmjow_sats
    Shigaraki Tomura (@grimmjow_sats) reported

    NVIDIA, MICROSOFT, IBM, CLOUDFLARE AND CROWDSTRIKE JUST FORMED A 37-ORG ALLIANCE — AND THEY'RE NOT AFRAID OF THE MODEL. they call it the Open Secure AI Alliance. it shipped an open-source stack, NOOA, to test, trace, audit and govern how agents actually behave in production. read what they're guarding against and it's obvious: → not "the AI goes rogue" → over-permissioned agents with access they never needed → tool calls nobody can trace after the fact the scary part of an agent was never its IQ. it's the keys you handed it and the logs you don't have. 37 of the biggest names in compute and security just admitted the same thing at once. everyone shipping agents is one untraced tool call away from the incident. follow and bookmark before your stack becomes the case study

  • adastroworld
    adas🧦🌹 (@adastroworld) reported

    @thsottiaux just does a cloudflare auth "human check" loop when trying to sign in from the browser lol

  • LucasSaasbr
    Lucas Rodriguez (@LucasSaasbr) reported

    Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

  • ItsKamranK
    Kamran Khan (@ItsKamranK) reported

    @Rian_Visser @Namecheap Rian....worlds best company use Cloudflare for security and speed....if you don't use that's OK....I use Cloudflare CDN for almost every project....I don't have any issue...and why I will pay extra price in renewal charges, if I renew in same flat prices...

  • waodao_ai
    WAODAO (@waodao_ai) reported

    @Cloudflare A routing signal stops being useful once operators can rewrite it for private advantage while downstream systems still treat it as truth. Deprecation should ship with an observable replacement, or the same incentive will migrate elsewhere.

  • pixelpatchit
    DR.PIXEL (@pixelpatchit) reported

    Swapdesk Alpha: DNS Expansion and Reliability Improvements As Swapdesk Alpha continues to mature, we plan to expand beyond our current Cloudflare and Google DNS support by adding additional DNS provider options. These providers have given us a strong foundation during the alpha phase, allowing us to focus on building and testing core functionality while maintaining reliable connectivity. During the THORChain swap process, users may occasionally experience intermittent connection issues while the application is retrieving required swap information, such as the deposit address needed to complete a transaction. These issues are not consistent and do not occur during every swap, but when they happen, they can create confusion because they occur during an important step in the transaction flow. It is important to clarify that an error message during this stage does not automatically mean a transaction has failed or that funds are at risk. In many cases, the issue is related to communication between the application and supporting services, which may include DNS resolution, API availability, network routing, or other connectivity factors. To improve reliability, future versions of Swapdesk Alpha will introduce broader DNS support, improved fallback handling, and additional resilience measures. The goal is to provide users with a smoother experience, reduce unnecessary interruptions, and ensure that Swapdesk remains dependable as adoption grows. We appreciate the feedback from early users helping identify areas where reliability and user experience can continue to improve

  • unixapple
    netox (@unixapple) reported

    Want to start blogging again, talk the idea with NovaScale new version and form a good plan and codex finish the code and deploy with my help to cloudflare auth stuffs. Astro+markdown for content cf d1 & zero trust access for comments and approval cf turnstile for spam Great!

  • _dylanga
    Dylan Garcia (@_dylanga) reported

    @CherryJimbo @Checkm3out @Cloudflare I agree. I gave the region fallback feedback to them after their most recent ENAM outage

  • DavidFrosdick
    David Frosdick (@DavidFrosdick) reported

    Cloudflare Email then sends the customer a link to a watch page. They can react, or reply, and that comes back into D1 against the original order. Whole loop, no third-party service in the middle.

  • anirudhwithanx
    Anirudh Kulkarni (@anirudhwithanx) reported

    @FuckKoroks glad to see cloudflare is idiot resistant

  • iamTRA
    Rohan (@iamTRA) reported

    I killed my Wix/Webflow subscriptions this week. ~$40/mo from old acquisitions. Bloated af. Replaced with $0/mo Cloudflare pages - built end-to-end by agent. Faster pages rank higher on Google Maps. Cloudflare docs are complex, never bothered to read. No need to in 2026.

  • _Nformer
    Informer |-/ (@_Nformer) reported

    I love how half the comments are just people who get salty when Cloudflare goes down and the other half are mad about Cloudflare having a monoply.

  • ptaranat
    Panat (@ptaranat) reported

    @LevJampolsky @Teknium you're better off implementing a simple version of this. give each trust tier its own hermes profile with toolsets stripped in config (platform_toolsets, agent.disabled_toolsets). then you expose only the api_server, and let ur own app authenticate the user and broker ever call. hermes' shared API key reads every session on the instance so it never accepts a session ID from a client. you'll want to map the user to the session in a DB and translate server side. and also put a Cloudflare Tunnel + Access service token in front so the agent host doesn't open any inbound ports. something like this took me one afternoon.

Check Current Status