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
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:
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 |
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:
-
swisscheese (@swisscheese4299) reported@OpenAI image generation is still throwing intermittent 520 errors through cloudflare.
-
T_T🏴☠️XMREscrow (@xmrescrow) reportedThings people usually have to take on faith, that you can check here: Our node relays every transaction through Tor, so payouts do not enter the network from a clearnet address tied to this service. We do not store IP addresses. Anti-abuse uses a keyed HMAC that cannot be reversed. Web-server error logs can hold an address transiently and are deleted within two days - it is on our legal page because saying "we log nothing" would be a lie. No accounts, no email, no KYC. An escrow is two private links and a PIN each. The onion carries no third-party code at all. The clearnet is Cloudflare-fronted for DDoS and we say so
-
Chris O'Rourke (@RsThrive) reported@HackingDave I get these where they’re like “hey I can get up to 20 million seed funding to support you at Cloudflare” … thanks bro but we’re publicly traded and I have 0 to do with that.
-
Kainoa Newton (@KainoaBHN) reported@leodev add support for cloudflare to sandbox sdk
-
DR.PIXEL (@pixelpatchit) reportedSwapdesk 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.
-
Michael Timbs (@michael_timbs) reported@thdxr Hahahahha. Improbable. One of the many reasons there’s very serious applications deployed on Cloudflare. Primitives are just wrong with terrible APIs the entire way down
-
ZEE (@CodeWithZeee) reportedI have this sneaking suspicion there’s someone at Cloudflare building what I’m building at I’m not sure if that’s a good thing or a bad thing ha
-
Grant Mucha (@grantmucha) reportedOrdering $50,000 in server hardware today and reflecting on a post I read earlier that asked, "Why is it so difficult to build a genuinely good X, Y, or Z, and why do so many products remain 'good enough' for half a decade without ever becoming great?" The answer, in most cases, is not capability. It is priorities. One company pushes X, another pushes Y, and another pushes Z, all because each benefits the seller. I see **** like this every day, it's not what's best for the owner, but rather what's best for the seller. In my experience, greed and ego explain a large percentage of mediocre products and services. Companies CAN build something better, take starlink, starship, building quality is a decision. Most prioritize profit first, investors second, and customers last. Take hosting. I do not need to: > Invest in quality servers > Pay 40k per month for Cloudflare Enterprise > License LiteSpeed Enterprise > Include real WordPress management > Promise zero technical debt > Maintain 90 days of redundant backups I could operate with a fraction of that investment and significantly increase my companies profit. I choose not to because I know exactly how this industry operates. I know companies still running production servers from 2013 on outdated kernels. Can they upgrade? Absolutely. Will they? No. Most people are not aware that Cloudflare Enterprise is modular. Contracts are assembled like Lego blocks. One company may technically offer "Cloudflare Enterprise" with a single component, another may have a handful, and others may have more than 100 enterprise features and configurations enabled. All of them advertise the same label, yet they are not remotely the same product. Now consider the customer's side. Within 48 hours, I can move a business owner into what is effectively a top 1% WordPress hosting environment, complete with real WordPress management, for $1,490 per year or about $124 per month. Consider for a moment that some companies charge $200/mo or more for WordPress management alone, and let that sink in for a minute. No technical burden. No infrastructure management. All existing technical debt resolved. Full WordPress management. No worrying about backups, performance, security, updates. etc. Owners focus on business, and for $124/mo, this is a joke to the vast majority making money, every day, 365 days a year. Circling back to mindset, I believe the people who fail to see it are often operating from the same greed-and-ego framework. They have to sell X, so they recommend it to everyone relentlessly, whether it's right or not. And the why is simple! It comes down to what you choose to prioritize, the decisions you make, and whether you are willing to put quality ahead of profit. More importantly, it is whether you are willing to put the customer ahead of yourself and your business, and prioritize a genuine win-win relationship. At which point, I believe there is no limit in business.
-
Bryan Jones (@bdkjones) reportedExplaining an Outage 101: @Cloudflare: "John uploaded a bad config file at 08:24:47.252 UTC. It flipped bit 0x00007FF6E4D316D0 in datacenter 49 and brought down the whole Internet. This is unacceptable. We know you count on us. John has been shot." @Apple: "Some users may have been affected by a service 'problem'. Pray we do not affect you further."
-
Matt (@meszmatew) reportedIs anyone else having issues with cloudflare billing?
-
Toolport (@toolportapp) reportedCloudflare's CTO, Dane Knecht, emailed their entire customer list about running every AI agent through MCP portals, with scoped tool access and a Code Mode they say cuts token costs ~93%. We build Toolport. This is our exact category. A few notes from the small end of the pond. 1. The announcement is two products wearing one trenchcoat. AI Gateway is a model-layer proxy. It routes your OpenAI/Anthropic calls and meters model spend, same lane as OpenRouter or LiteLLM. MCP portals are the tool layer, deciding which servers and tools each agent can touch. Different problems, different failure modes. If you're evaluating either one, don't let the bundle blur that line. 2. Their ~93% Code Mode number lands in the same range we've been measuring with lazy discovery for the past year. Loading dozens of tool schemas into context on every request was always the wrong default. It's nice that it's no longer just indie gateway builders saying so. 3. The structural difference. Their portals require being a Cloudflare customer and routing agent traffic through their edge. Toolport runs on your own machine and works with Claude Desktop, Cursor, and 25 other clients, with no vendor in the traffic path. When the traffic is your prompts, your credentials, and your tool outputs, where it flows is not a detail. 4. Scoped access is becoming table stakes. The harder question is whether the tool you approved yesterday is the same tool running today. Toolport pins tool integrity, quarantines drift, and scans for injection. A DLP scan on the wire doesn't catch a server that changed underneath you. Watching a giant walk into your category is a strange feeling. It's also the strongest signal yet that this layer needs to exist. We just think it should live on your machine, not in someone else's cloud.
-
Santosh Yadav (@SantoshYadavDev) reported@thdxr I never got comfortable using wrangler, I think I dont like it. otherwise cloudflare has a great DX
-
Blue Pastel (@CoyotlCompany) reportedStopping the bad guys with Cloudflare: 376 malicious requests blocked or challenged in the last month #cloudflare
-
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.
-
haden staab (@staabse) reported@Porkbun @baiaphilia Firstly, I never said there was something wrong with you. You’re more than welcome to give us your pitch. Why should I use Porkbun over Cloudflare?