Cloudflare Outage Map

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:

• 
  Corey Quinn (@QuinnyPig) reported 4 minutes ago

  @KhalidWarsa @Cloudflare The trick is to actually be a customer of the things you shitpost about, otherwise it's just noise.

• 
  二次裏@あいもげ (@nijiurachan) reported 7 minutes ago

  @Cloudflare Shut down the server

• 
  hide.me VPN (@thevpncompany) reported 11 minutes ago

  Scale check: Cloudflare blocked 20.5M DDoS attacks in Q1 2025. The biggest on record hit 31.4 Tbps. No home connection survives that. The goal isn't being unkillable. It's never handing over the address they'd aim at.

• 
  Dorian (@Dorian251362) reported 15 minutes ago

  @RococoRomance It really, really does 🥲💔 It might be a location issue (or device+location) issue since I have heard a few other foreigners having similar problems. But it doesn’t seem like there is any way around it if the cloudflare just decides you are evil 🥲💔

• 
  Titanium (@akinkunmi) reported 24 minutes ago

  @Kolar_Dev Vercel has a **** ton of features and it still looks good. Same as Posthog. Even CloudFlare. So that's not even an excuse.

• 
  Kaspar Poland (@kasparfp) reported 26 minutes ago

  @QuinnyPig @vmg__0 @Cloudflare They just imported the AWS Account problem and ignored the GCP Solution.

• 
  George Apostolakis (@Apostolakis_Geo) reported 27 minutes ago

  @YashHustle_22 I used netlify for small projects in the past until I realised that it sucks so I switched to cloudflare

• 
  अमित रंजन I Amit Ranjan (@DrAmitR) reported 28 minutes ago

  Is anyone else facing issues with the #NBEMS #AI_in_MedicalEducation final assessment? Very slow loading throughout, and after 22 questions I got a Cloudflare Error 524 and could not proceed. Have others been able to finish the assessment? What should we do next?

• 
  Jims (@JimsYoung_) reported 29 minutes ago

  Anyway, checking in at 20k registered users. 🎉 Some recent takes: — Agents are massively underestimated. Given how fast context windows are evolving, something like Fable can now grind on a task for a full day, fast and good. You can already offload the vast majority of your work to it. The real bottleneck is that most agent runtimes and multi-agent workspaces on the market are way too complex to set up, so the number of people who can actually use them is tiny. The ones who can are using them every single day, but even they keep getting bogged down by runtime and agent management. — One very tangible shift: a lot of legacy infra just can't keep up anymore. Cloudflare outages, for example, have gotten noticeably more frequent. Agent traffic to websites has already surpassed human traffic, and it's only going to grow from here. Infra needs a new foundation. I've got friends already building new switch programming, even chip-level protections. — Defining the problem clearly matters far more than execution. The longer I do this, the more I disagree with certain bets: a) "Agentic payments will necessarily be small-amount, high-frequency." Probably the most off-base one. Agents are going to take a meaningful chunk of transactions, regardless of size or frequency. Say an agent transfers money for you based on an invoice — the amount doesn't matter at all, it's just whatever the invoice says. No reason it has to be small. And frankly there's a whole class of demand here we never even anticipated. b)"Agentic payments must use stablecoins." Not strictly necessary. But a substantial portion will be stablecoins — it really depends on how you define agentic payments… c) "Agentic payment = using an agent to shop for people." Feels like there are ten thousand AI shopping assistants that can already do this — see Shopify's UCP — and after all this time, basically nobody uses it. A lot of the time people just can't articulate their own needs. We need much better ways to collect context. — A lot of the big players really are all talk, surprisingly slapdash. When we were running our security rotation, a prompt injection straight-up exfiltrated the agent wallet private key from a major company whose name starts with "S"… The biggest security problem in agent payments isn't in the payment — it's in the agent. Which is exactly why the right environment and guardrails matter so much. — Whether agents use cards is a genuinely interesting question. If you're ambitious enough, there's a real shot at building a new rail in virtual environments that kills the card networks entirely. At its core, payment is just an authorized, trust-based act of bookkeeping. What cards fundamentally provide is convenience — not having to type in a bank account, being able to complete a transaction at a terminal, a fixed network of transfer channels and information exchange. Every one of those things can be solved by agents instead. Honestly, you can let your imagination run wild here.

• 
  Josh (@josh_nimako) reported 29 minutes ago

  What Outranking a $1B Company Taught Me Before My 1.7M User SEO Project Died One of my first serious SEO projects is dead now. Before it died, it reached over 1.7 million active users, gave me my first million clicks, and for about a month, and even outranked a company doing around $1B in revenue. But the failures were louder than the losses. The real lesson came after the rankings started working, because traffic showed me every weak part of the site, the server, the content, the tracking, and my thinking at the time. I knew enough to build the site, publish content, target searches, add schema, work on image SEO, and chase fresh demand, but I did not yet understand what happens when the traffic actually lands. Getting traffic is one problem. Surviving traffic is another. The site started as a normal beginner project. Some of it worked faster than I expected. I learned that image SEO can be a serious traffic source when the niche has visual demand, schema can help Google understand the page faster, and freshness can matter more than authority when a search window opens for a short period of time. I also learned how powerful Reddit can be. We used Reddit as part of the distribution layer, not because it was magic, but because Google already trusted the platform and certain threads could rank fast when the query had the right shape. That was my first real lesson in parasite SEO. Sometimes the fastest way to appear in search is not to wait for your own domain to build trust, but to place the right content on a platform Google already trusts, then use that page to capture demand while your own asset grows. That does not replace building your own site. It teaches you how distribution actually works. For about a month, that kind of thinking helped me outrank a company with far more money, authority, and resources than me. I was not better than them. I was just closer to the search. I understood the timing, the page format, the image demand, the freshness window, and the exact thing the user wanted in that moment. That changed how I saw SEO. Big companies can win on authority, but small operators can still win narrow battles when they move faster, match intent better, and understand the search better than the bigger player does. Then the site started breaking. During traffic spikes, pages would freeze, the server would throw 502 and 504 errors, and the site could be unavailable for long periods while I tried to work out what was happening. At the time, the server was exposed directly to the internet, so every request hit the origin server. Real users hit it. Scraper bots hit it. Aggressive crawlers hit it. Bad traffic hit it. Everything hit the same machine. The PHP-FPM pool started choking, Apache logs showed worker thread errors, and the server ran out of breathing room because it was trying to handle too many requests at once. That was the first time I understood that infrastructure is part of SEO. If Google sends traffic and the site falls over, that is not only a server problem. It becomes a crawl problem, a trust problem, a user problem, a revenue problem, and eventually a search problem. The worst issue was inside the theme. The site used Themify Ultra, and one function was checking images through full public URLs instead of local file paths. That sounds small until traffic hits. One page view could cause the server to make extra HTTP requests back to itself to inspect images, so instead of one visitor creating one normal request, the server created more work for itself while also dealing with real users and bots. It was a self-DDoS loop. The site was not only being hit from outside. It was also wasting resources calling itself. We fixed it by bypassing the image-checking behaviour and adding a local hosts shortcut so the server could resolve itself internally instead of going out through the public internet. That one bug changed how I think about performance. Performance is not just a page speed score. Performance is what happens when the whole system is under pressure. Then we put Cloudflare properly in front of the server. Before that, the origin IP was exposed, which meant bots and scrapers could hit the machine directly. Now Cloudflare became the front line. It hid the real server IP, cached static assets like images, CSS, and JavaScript, and challenged or blocked bad bot traffic before it reached the server. That took pressure off the origin. The server no longer had to serve every image to every visitor, and it no longer had to take every bot request directly. Now, if I build a site that depends on organic traffic, I do not treat Cloudflare, caching, bot filtering, and origin protection as extras. They are part of the build from day one. I also learned that bots are not a small issue. Some were scraping content. Some were hammering pages. Some were burning CPU without acting like users. They did not convert, subscribe, read properly, or add anything useful. They just created load. That forced me to learn server logs, Nginx logs, Apache errors, PHP worker limits, caching, bot protection, and traffic spike behaviour, because Analytics could tell me people were visiting, but the server logs showed what was actually hitting the machine. That changed how I use SEO tools too. Ahrefs and Semrush are useful, but they are not the market. In this niche, demand could spike fast when new content appeared, and a page could get thousands of clicks in the first hour before the window closed. A third-party tool might not show that properly because the demand moved too quickly. Search Console showed what Google actually sent. Analytics showed what users did. Server logs showed what hit the server. No single tool had the full truth. I also made quality mistakes. One of the biggest was allowing an unmoderated comment section. At the time, I thought comments were harmless because they added more text and activity to the page. That was naive. Spam, thin replies, irrelevant text, and messy user-generated content made pages worse. The site had traffic, but parts of it started to look lower quality than they should have. That taught me that more content is not always better. More indexable text is not always better. If the page is the asset, you cannot let random people lower its quality. Now I think about SEO very differently. Before this project, I thought SEO was mostly about ranking pages. Now I think it is about building systems that can turn search demand into something useful without breaking. That means the page has to match intent, the content has to be controlled, the server has to survive traffic, the logs have to be watched, the origin has to be protected, and the traffic has to lead somewhere beyond a graph inside Analytics. The site is dead now. Some reasons were strategic. Some were technical. Some were niche specific. All were my fault in the end. But I do not see it as wasted work. It taught me how real traffic behaves. It taught me that a page can rank and still be fragile. It taught me that a site can have users and still be a weak asset. It taught me that small operators can beat giants in narrow search windows and that Reddit and parasite SEO can move fast when the query fits. It taught me that Cloudflare can be the difference between traffic and downtime and that server logs tell a different story from dashboards. It taught me that the next problem starts after the ranking works. That is the part I carry into every project now. I do not just ask: Can this rank? I ask: Can it survive the traffic? Can it stay clean? Can it handle bots? Can it load under pressure? Can it earn trust? Can it turn attention into users, leads, revenue, data, authority, or another asset? My first serious SEO project is dead. But it gave me the lessons I needed. And those lessons are now part of how I build.

• 
  MaiKaun (@MaiKaun415422) reported 29 minutes ago

  @vanyaSile The thesis is sound: AI agents are scraping the web at scale, publishers are watching referral traffic collapse, and there’s no clean way to charge a bot for access. Cloudflare already launched pay-per-crawl, the x402 payment standard exists, and people are betting on agent-to-machine micropayments. The hard parts, honestly: You’re picking a fight with adoption on both sides at once. Publishers need to install you AND agents need to pay through you. That two-sided cold start is brutal, and the side with leverage (the big AI labs) has every incentive to route around you or strike direct licensing deals, which is what’s already happening (Reddit-Google, OpenAI-publishers). Whoever owns the chokepoint wins, and right now that’s CDNs and identity layers. Cloudflare sits in front of ~20% of the web and can bundle this for free. A standalone infra startup has to explain why a publisher adds another vendor instead of flipping a switch on infrastructure they already run. The defensibility is thin unless you own either the bot-identity/verification problem (hard, valuable) or become the default settlement rail (network effects, winner-take-most). “We let sites charge agents” as a feature gets absorbed. Where I’d actually look: the verification and pricing layer, not the toll booth. Knowing which agent is asking, on whose behalf, and what the data is worth dynamically is the genuinely unsolved part. The payment plumbing is becoming a commodity standard fast. For Transparency: Ofcourse I validated the idea with AI and added some of own flavor!

• 
  Komal Sibraan (@KomalSibraan) reported 31 minutes ago

  1/ The woman was Michelle Zatlyn. The company was Cloudflare. This came out in a viral VC horror story thread on X this week and I genuinely had to put my phone down.

• 
  Aaron Ware (@EarnWhere) reported 35 minutes ago

  @Cloudflare 's PDF endpoint is so good. I spent hours trying to speed up PDF creation inside of my architecture and did so much hacky **** to achieve a decent-enough UX. Just implemented Cloudflare's endpoint and happily ripped all that out for substantially better results.

• 
  Interfacing Linux (@intlinux) reported 39 minutes ago

  Cloudflare Dashboard is down and now Facebook is exploding. Going to be an interesting Friday.

• 
  Aryan Esfandiari (@arian88) reported 40 minutes ago

  Never push to main on a Friday @Cloudflare