Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (38%)
• Cloud Services (30%)
• Hosting (18%)
• Web Tools (10%)
• E-mail (5%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Angers	Cloud Services	4 days ago
London	Domains	6 days ago
Noida	Hosting	19 days ago
Jewar	E-mail	19 days ago
Braga	Web Tools	20 days ago
Noida	Cloud Services	20 days ago

Full 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:

• 
  Dane Knecht 🦭 (@dok2001) reported 5 seconds ago

  @Nateemerson @ritakozlov @Cloudflare None of those. Technologist that love customer and understand developers.

• 
  Jeff Needles (@jsneedles) reported 7 minutes ago

  @Hussain_Joe @_ceifa Well, the key is its pretty much managed, just not e2e. Like it's Cloudflare Workers + pipelines + queues -> CH cloud. All managed services! Just the raw volume makes most "pure" managed analytics providers extremely prohibitive -- like prob 10x the cost at least. Of course, there's other options that are really self hosted that are less analytics-focused... or things that rely more on object storage as the source of truth (like R2 SQL, which would actually prob be cheaper) But I've put in maybe 10 hours of necessary maitenance in the last year, occasionally the analyst who uses the system will ping me for questions/advice etc -- but raw infra/system wise, like 0 issues!

• 
  Dhairya (@dkare1009) reported 9 minutes ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Prince mendiratta (@PriMendiratta) reported 12 minutes ago

  @threepointone Relevant to this! We hit "other side closed" errors with buffered LLM calls (stream: false). Root cause: Cloudflare egress kills TCP connections idle for ~300s. Buffered calls keep the socket silent until done, so long generations get killed mid-flight. TCP keepalives don't help, only real data resets the timer. For large AI tool calls this can hit 10+ mins. Does your resumable buffer approach handle this?

• 
  Aryan Esfandiari (@arian88) reported 12 minutes ago

  Never push to main on a Friday @Cloudflare

• 
  Dmitrii Malakhov (@malakhovdm) reported 13 minutes ago

  @AISGateway An agent can't tell "the site is slow" from "the site blocked me." Mine spent 20 minutes retrying a Cloudflare challenge it couldn't even see.

• 
  Jaid (@JaidCodes) reported 14 minutes ago

  I have dozens of personal SPAs not worth setting up a deployment pipeline to GitHub Pages or Cloudflare Pages for. There are a lot of situations where I just want to quickly one-shot a tool and drop the Vite build to a service that gives me a random public domain.

• 
  Star Jessei💕 (@Starjessei_web3) reported 16 minutes ago

  What if your next customer isn't a person? AI agents are already buying compute, APIs, and services autonomously and @WalletConnect & @base Pay just built the rails for it. Here's what's actually happening onchain right now: ➫ Stablecoins cleared $46T in 2025 and for context, that's more than Visa moved all year. ➫ Base is holding $4.7B in stablecoin supply and pushed $2.5B plus through WalletConnect Pay in Q1 2026 alone. ➫ x402 lets AI agents hit an endpoint, get a payment request, sign a USDC micropayment, and keep moving. No unnecessary back and forth And it's not some niche crypto experiment because, Google, Microsoft, AWS, Visa, Mastercard, Shopify, and Cloudflare are all behind it. Additionally, Ingenico, the company powering payment terminals in 32 countries, has already integrated WalletConnect Pay. This is reaching physical retail now. WalletConnect Pay is the underlying wallet layer. 500M users. 700+ wallets. One integration. Commerce is going onchain and Base is where it's landing. It doesn't matter if the buyer is a person tapping their phone or an agent finishing a task at machine speed, WalletConnect Pay is how they connect to it. This is the future!!!!

• 
  Josh W (@ItsWelford) reported 17 minutes ago

  @Cloudflare cc: @dillon_mulroy do you know anyone that can help me with this?

• 
  Victor (@echo_vick) reported 17 minutes ago

  I can’t seem to access CloudFlare using my MTN network, but it immediately opens once I switch to Airtel. Does this happen to anyone else?, is this common?

• 
  Axel Hardy (@fraxool) reported 21 minutes ago

  Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expiring token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

• 
  Sreram Rathnam (மோடியின் குடும்பம்) (@sreramrathnam) reported 22 minutes ago

  Bro, let's understand how server infrastructure and network security policies actually work. If someone tries to flood a website with over a million artificial hits using automated bots or scripts, the Hosting Server Provider and Cloudflare would immediately flag it as a malicious volumetric attack, suspend the URL, or ban the site entirely to protect hardware resources. However, the website has been completely active and up for almost a week without a single second of downtime. This is because Cloudflare Edge Servers have thoroughly cross-verified all incoming concurrent traffic using unique IP addresses and request headers, authenticating it as human traffic. If it were automated bot traffic, Cloudflare's built-in Automated Bot Management system would have instantly mitigated and blocked it at the network layer before it even registered on the telemetry dashboard. Basic server provider policies and network protocols confirm that this volume is fully validated, bro.

• 
  Stock Report (@StockReportt) reported 24 minutes ago

  3: $NET — Cloudflare They protect and accelerate internet traffic for millions of websites. Cloudflare's massive global edge network acts as a shield against DDoS attacks, keeping corporate AI applications online.

• 
  surya murugan (@SuryaMurugan_) reported 25 minutes ago

  @elithrar @dok2001 @Cloudflare Please add support for r2 data localization in India. Cannot use r2 for any DPDP act complaint services. 🙃

• 
  Kaspar Poland (@kasparfp) reported 25 minutes ago

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

• 
  Josh (@josh_nimako) reported 27 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.

• 
  Axel Hardy (@fraxool) reported 28 minutes ago

  Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expired token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

• 
  Nikhil Agarwal (@nikhildp) reported 31 minutes ago

  @ade_oshineye Won't it be better to fix the obvious billing issue first so that startups can use cloudflare peacefully? How can there be no limit on expense? Company should not have bear insane expense because of a dev mistake which causes dynamic workflow to go in infinite loop.

• 
  Joshua Farrel (@joshuafarrel) reported 35 minutes ago

  @FM_Assist Would love to, but I can't seem to register myself on the forum...Cloudflare verification error, and can't sign in with Socials as well..

• 
  Jacob MG Evans (@JacobMGEvans) reported 36 minutes ago

  "Why do you hype up Cloudflare so much still, you don't work there..." It was never because I worked there lol

• 
  KAMWI TECHNOLOGIES (@kamwifi) reported 37 minutes ago

  Stopping the bad guys with Cloudflare: 159 malicious requests blocked or challenged in the last month #cloudflare

• 
  Colleen (@PiedViper) reported 41 minutes ago

  @LiberN8 @yacineMTB Who is "they"? Unless you're talking about Cloudflare, who has significant legal and economic constraints on how aggressively they can take down sites, blacking out a random social media site worldwide requires cooperation and can be a game of whack-a-mole, especially if some servers stop accepting certain servers' pushes. The entire key-signing rituals of ICANN are only meaningful if most people accept them as authoritative. If they start messing around with letting one country dictate policy for the world, there's not going to be one main internet any longer.

• 
  Gene (@cogentgene1) reported 41 minutes ago

  @araseb_ I’m using Cloudflare. Bad idea?

• 
  andrew johnson (@rsdworker) reported 41 minutes ago

  @RailDepartures @bustimes_org could be as facebook is back up thats might be cloudflare issue that is affecting other sites

• 
  Steve Brownlie (@sdbrownlie) reported 46 minutes ago

  @asaio87 For some things I found it more annoying than opus lol. I'm sure it was smarter - it realised some bug I was trying to solve was actually a cloudflare temporary/transient issue and it was right it went away by morning. gpt-5.5 didn't think to check that... but... other than that i agree it wasn't very different.

• 
  John Andrews (@johnandrews) reported 49 minutes ago

  I was on one of these lists and it was very unfair.... a test QnA site deployment I can *almost* understand spamming, but even our best hardened instance in production was such a target, I eventually shut it down, rather than have it consume all backend attention and eventually pay Cloudflare to protect it. 30,000 useless test attacks per hour at one point... about 98% of actual traffic. And that was in the days when 80% of the script kiddies were manually starting/stopping their runs.

• 
  Miss Latin (@duchesslatinxo) reported 54 minutes ago

  @ritakozlov @Cloudflare How about we hire someone who can actually fix all the API issues. Someone who can get the code from a-z without it bouncing back? Because my company is seeing a 30% decline in profit for the last 6 months due to increasing outages. Cloudflare is always late to report on their own outages. It’s been unstable since the 1st of April… Essentially speaking I’m 100% certain the new integrity verification measures placed on meta has caused major outages on cloudflares CDN. Let’s get this fixed??

• 
  Corey Quinn (@QuinnyPig) reported 56 minutes ago

  Since the way AWS employes used to act (read as: deeply caring about the customer experience) is how @CloudFlare employees currently act, here are annoyances I wish CF would change. A thread.

• 
  Shreyas Mididoddi (@Shreyassanthu77) reported 56 minutes ago

  @joshmanders Primcloud sucks we should delete all of it and rewrite it in cloudflare

• 
  Dorian (@Dorian251362) reported 57 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 🥲💔