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 (39%)
• Cloud Services (29%)
• Hosting (17%)
• 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	19 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:

• 
  Andrej Ruckij (@ruckiand) reported 3 minutes ago

  Online stores are panicking that AI bots are crawling their site and "stealing" their catalog. So they hit the one-click Cloudflare toggle and block everything. Most are solving the wrong problem — and quietly hurting themselves. 🧵

• 
  Lifeis2-D (@Lifeis2D) reported 4 minutes ago

  The "troubleshooting" link that also leads to a broken/nonfunctional "feedback" form? Yeah that's also kinda ******. When did cloudflare get promoted to internet gater?

• 
  CryptoXpert (@0xRasmPro) reported 18 minutes ago

  @Md_Sadiq_Md @Cloudflare @tan_stack Respect for pushing through that parser hell. Obsidian never plays nice with web renderers.

• 
  Lex Tang (@lexrus) reported 20 minutes ago

  I bought a domain on Cloudflare and had Codex enable cloudflare/agentic-inbox for me. Sending and receiving emails is a bit slow. I'm unable to add the account to any email apps. Considering it runs completely free on Workers and can be operated with MCP, these drawbacks can be nothing. It composes a response email draft every time it receives a new email, so I think it's a good fit for feedback emails.

• 
  Bilal @ Supadesk.co (@BilalBudhani) reported 21 minutes ago

  Cloudflare is down folks. What are you guys up to?

• 
  ritesh (@pinegoat12) reported 25 minutes ago

  Is cloudflare down?????

• 
  MBrant75 (@MBrant75) reported 26 minutes ago

  @nickSfishes315 @JackDan110 Heh Really? Cloudflare issue or something?

• 
  KhloePai (@Khloes_Khloes) reported 26 minutes ago

  @Kitasure Yea, I've been noticing this in the evenings mostly. For me, its been any cloudflare service which discord uses to deliver media. I've been able to get around it with a vpn. Messages and connecting to vcs has been okay for the most part.

• 
  TheLarioso (@TheLarioso) reported 28 minutes ago

  @brivael You have these massive scripts CloudFlare many are connected to and collect ip:s and check if bots etc. - you could very well just go ip and block those that exist - yes, quite a few but can be done I think You do not need to go to a particular service, you vpn service has an ip.

• 
  Dr. Jaime Alnassim, M.S. (@JaimeAlnassim) reported 28 minutes ago

  @dannyvankooten @patrickposner_ If you want to get edge cache with bunny like many cache plugin intergrate with Cloudflare, I have a connector plugin I made. Getting around 50-100 TTFB now. I asked bunny if I can use the bunny name on the slug when I submit it to WPorg, so it's probably going to be a long waiting game, but I can send over the zip if you'd be interested to try it. It's going to be 100% free either way. I use it on WooCommerce and WPML sites without issue too. Works with 10+ cache plugins

• 
  Shantun Singh Parmar (@ParmarShantun) reported 34 minutes ago

  @uday_devops For which they gave always coupon you can use them, also thier support is quick not like GoDaddy and cloudflare charge

• 
  Chamoda Pandithage (@0xchmod) reported 34 minutes ago

  @cagrisarigoz @Cloudflare Yep, down for me

• 
  Aaron Ware (@EarnWhere) reported 37 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.

• 
  Utopian Contributors (@utopiancontrib) reported 38 minutes ago

  We figured out a way to end what seemed like a never ending story: JavaScript bloat This wasn’t Google or Microsoft or Mozilla or CloudFlare or Vercel. It was the Utopian Contributors LLC. But this was just the beginning. The future of the web is ultra-efficient.

• 
  Abolaji Rasaq Oluwapese (@bolazeal) reported 38 minutes ago

  @echo_vick Install Cloudflare Warp to fix this issue

• 
  MRCΛULIMΛN (@mrcauliman) reported 38 minutes ago

  $XRP utility check. Magnetic looks like it’s having a hosting issue this morning. Cloudflare is up. Browser is up. Their origin server is timing out. XRPL is fine. The AMM pools are fine. If you’re trying to set a trustline or swap, use Bithomp, XPMarket, Sologenic, First Ledger, or Bear Swap until Magnetic is back. One front end is down. The ledger keeps moving.

• 
  Shreyas Mididoddi (@Shreyassanthu77) reported 38 minutes ago

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

• 
  John Andrews (@johnandrews) reported 41 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.

• 
  Agentic Up (@agenticUP) reported 45 minutes ago

  cloudflare is down??

• 
  Ariekany🔸(🦀/rust) (@Ariekany) reported 46 minutes ago

  @advnt0x5 @ankkala wow, amount of acumulative LoC very interesting to imagine the complexity.. but 1 line cloudflare error could take down the whole internet for a day 💀💀

• 
  inder (@InderpreetSingh) reported 46 minutes ago

  Looks like @Cloudflare dashboard is down, but just saw "Organizations Beta". I hope thats the case. All my projects are co-mingled in a single account right now.

• 
  Ultron AI (@TheUltronAi) reported 48 minutes ago

  - Claude for coding. ($20/mo) - Supabase for backend. (Free tier) - Vercel for deploying. (Free tier) - Namecheap for domain. ($12/yr) - Stripe for payments. (2.9% per transaction) - GitHub for version control. (Free) - Resend for emails. (Free tier) - Clerk for auth. (Free tier) - Cloudflare for DNS. (Free) - PostHog for analytics. (Free tier) - Sentry for error tracking. (Free tier) - Upstash for Redis. (Free tier) - Pinecone for vector DB. (Free tier) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build. It's not that deep bro.

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

• 
  Pranjal Soni (@pranjalsoni_) reported 52 minutes ago

  after spending more than $1k/mo with replicate, they don't even consider replying to their support emails anymore thanks to cloudflare acquisition i am fixing and replacing their models that stopped my app in the middle of the night before going to sleep

• 
  Corey Quinn (@QuinnyPig) reported 53 minutes ago

  @cjols_ @Cloudflare I wasn’t kidding—you folks are setting the customer experience bar these days.

• 
  kclich  (@kclich) reported 53 minutes ago

  Websites you’ll actually use (and wish you knew earlier) 👀 Temp Mail Disposable emails for quick signups and testing. Down For Everyone Or Just Me Check if a site is down or it’s just your connection. Wayback Machine View old versions of websites and deleted pages. BuiltWith See what technologies any website is using. JustWatch Find where any movie or series is streaming. Temp Number services (e.g. TextNow, Sonetel) Get virtual numbers for verification and testing. CamelCamelCamel Amazon price tracking history (real discount checker). Cloudflare Radar See internet traffic trends, outages, and global insights. Wappalyzer Instantly detect tech stack of any website (browser extension). Have I Been Pwned Check if your email was leaked in a data breach. Remove dot bg Instant background removal for images. Photopea Free browser-based Photoshop alternative. Regex101 Test and debug regex patterns instantly. JSON Formatter (jsonformatter dot org) Clean and debug JSON quickly. Carbon Turn code into beautiful shareable images. Excalidraw Simple online whiteboard for diagrams and system design. What are you using daily that’s missing here? 👇

• 
  Raunak Yadush (@raunak_yadush) reported 54 minutes ago

  6. Default DNS Resolution Lag What it does: When your TV tries to load the image thumbnails for an app like Netflix, it uses your Internet Service Provider's default DNS server to find out where those images live on the internet. Think of DNS as the internet's phone book. Why it kills performance: ISP phone books are notoriously slow and incredibly outdated. Often, your TV is not actually lagging at all. The processor is fine, but the TV is frozen waiting for your internet provider to tell it where to download the movie poster graphics. *********** it: Settings → Network → Network Status → IP Settings → DNS Setting → Enter Manually. Change the numbers to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). You will literally watch your streaming apps load twice as fast.

• 
  world's third accidental detransitioner (@replymoder) reported 56 minutes ago

  @OswinOswald223 small problem with that is VPN IPs get blocked by a lot of web hosts, main problematic one is cloudflare you'd need a VPN with a residential IP

• 
  The AI Entrepreneur (@ai_in_it) reported 58 minutes ago

  the big AI labs trained on most of the public web. now a ton of those same sites are locked down tight. cloudflare, login walls, bot checks you basically have to pay to clear.

• 
  Daniel Petro (@DanielPetroAI) reported 1 hour ago

  @RhysSullivan @batuhan Have you tried the built in cloudflare agent? It's pretty legit and fixed some DNS issues for me on 2 different domains I imported