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 (40%)
• 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	3 days ago
London	Domains	5 days ago
Noida	Hosting	18 days ago
Jewar	E-mail	18 days ago
Braga	Web Tools	18 days ago
Noida	Cloud Services	19 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:

• 
  KenAi (@kenAI_domains) reported 6 minutes ago

  Cloudflare and GoDaddy launched ANS - the Agent Name System - in April 2026. The Linux Foundation launched DNS-AID in June 2026. These are not product launches. These are infrastructure announcements. The agentic web is getting its own naming layer. Millions of AI agents will need identities, discoverability, capability lookup, reputation signals, and the ability to coordinate with other agents. They can’t do that without a Name Service for AI 👇

• 
  Chuks 🔶️ (@chuksXB) reported 7 minutes ago

  @nthglsn @Cloudflare Wtf is wrong with them

• 
  Goodness And Mercy (@FineAndRich) reported 8 minutes ago

  🚨 Cloudflare is currently investigating issues affecting the Dashboard and related APIs. ❌ Dashboard requests may fail ❌ API calls may return errors ✅ CDN cached content remains operational ✅ Edge security services are unaffected If your automation or deployments are acting up, Cloudflare may be the reason. #Cloudflare

• 
  Nathan (@nthglsn) reported 8 minutes ago

  @mofeeni @Cloudflare damn...

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

• 
  Steve Brownlie (@sdbrownlie) reported 11 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.

• 
  AGK (Ejike) (@dom000_dev) reported 13 minutes ago

  @echo_vick To solve this use a VPN or use cloudflare WARP it'll reroute your network provider to use their proxy, case closed

• 
  Dhairya (@dkare1009) reported 15 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

• 
  Ivon Huang (@Ivon852) reported 16 minutes ago

  GoDaddy positions itself as an all-in-one website-building platform for small and medium-sized businesses. Besides domains, they also sell website builders, WordPress hosting, email, SSL, WHOIS protection, and marketing tools. GoDaddy is often cheap for the first year, then the renewal price goes up. But I don’t need any of those add-on services. So this year, I finally made up my mind and transferred my domain to Cloudflare Registrar. The price was basically cut in half. Cloudflare Registrar sells domains almost at cost. The transfer process was surprisingly straightforward. I thought GoDaddy’s terrible interface would try every possible trick to stop me from transferring out. But in the end, I just filled out a form, got the authorization code, and that was it. A domain transfer usually does not require an extra transfer fee. Your website will not go offline during the transfer process, but it usually takes at least three days to complete. After the domain transfer, the new registrar will charge you for one year of renewal upfront.

• 
  Anurag (@aarekaz) reported 17 minutes ago

  Is cloudflare down?

• 
  NewsTongue (@NewsTongueX) reported 20 minutes ago

  🔴 Brazil ISPs block GitHub, Fitbit repacks without public explanation Major Brazilian internet service providers Claro, Vivo, and Nio have unilaterally blocked access to GitHub, Fitgirl Repacks, and dozens of other sites under secret orders from Brazilian authorities, according to Cloudflare support. The blocks affected not only developer platforms but also official government infrastructure, including the Central Bank of Brazil. No public explanation has been provided for the restrictions.

• 
  Caminomaster (@caminomaster) reported 21 minutes ago

  @Cloudflare Turnstile verification is not working. Unable to login #CloudflareDown

• 
  Séríkí Aláṣela | Séríkí Aláṣeyọri | Séríkí Adinni (@AuthenticLagos) reported 23 minutes ago

  @Abiodun0x @echo_vick Unfortunately the reverse is the case here... I have to configure CloudFlare DNS on my phone to be able to use my Airtel network properly

• 
  Aidan Quinn (@BwcDeals) reported 34 minutes ago

  @suavecito585 Supposedly Amazon went to the government about it too. Honestly, I wouldn’t be shocked. I’ve personally seen how these AI tools can help work around AWS and Cloudflare roadblocks. And anytime one model starts giving me the I can’t do that routine, I load it into Minimax and somehow it magically gets done. Wild times. 💀💀

• 
  अमित रंजन I Amit Ranjan (@DrAmitR) reported 35 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?

• 
  Shreyas Mididoddi (@Shreyassanthu77) reported 36 minutes ago

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

• 
  BornToLose💀🍀🏆 (@__BornToLose__) reported 38 minutes ago

  Spectrum can bite my ***, wdym 30mbps down is fine? Was really hoping it was just a cloudflare thing or something on my end but nope, I'm genuinely just stuck with the world's shittiest ISP and nothing I can do about it.

• 
  Enzo (@Captain_Enz0) reported 38 minutes ago

  @Touchtheginger @OldSchoolRS Authenticator linked to both the account and attached email, with the email being used for nothing but the account is as good as any other security. Tons of cloudflare problems when I was overseas, even with a VPN. Linking all characters to one account leads to more vulnerability if you do have a hack of any kind. If they false ban you, which they have done plenty of times (faux), they can nuke your whole account and all characters associated. Love OSRS and the team, think jagex is making a lot of good moves in general, but **** the jagex launcher

• 
  Victor (@echo_vick) reported 41 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?

• 
  Nikhil Agarwal (@nikhildp) reported 46 minutes ago

  @CloudflareDev Use at your own risk! No upper limit on how much money you can spend and Cloudflare customer service is quite poor. Avoid any cloud where there is no upper limit on expense, esp Cloudflare!

• 
  🅰 🇩 🇪 (@AdebayoOmolumo) reported 48 minutes ago

  @AirtelNigeria The file sent just shows that nothing is returned from Cloudflare when accessed on your network

• 
  Jacob (@Jacobmalherbe21) reported 49 minutes ago

  @softDev23 weird thing with Cloudflare is with 110 workers (web App) I have build its still just free ? Like I have never paid them anything to use their platform. Its really great

• 
  Star Jessei💕 (@Starjessei_web3) reported 50 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!!!!

• 
  Agentic Up (@agenticUP) reported 52 minutes ago

  cloudflare is down??

• 
  Sreram Rathnam (மோடியின் குடும்பம்) (@sreramrathnam) reported 53 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.

• 
  Shashwat (@theshashwat20) reported 55 minutes ago

  @Cloudflare Your domain checkout page needs some real transparency. Just bought a new domain. It showed $26.00 throughout the entire process. Got charged $30.68. The extra $4.68 in taxes was never mentioned once during checkout. Only found out via the invoice email. Please show the final all-in price (taxes included) upfront. It's a small change that greatly improves customer trust. Fix this.

• 
  Dan Holzrichter (@dholzric) reported 57 minutes ago

  @HoffmanTactical @RattlerInnovLLC I assume you have someone on this already, but if they cant resolve it, let me know. I pulled down everything available from the cache and wayback, and have it refactored to run directly on cloudflare. (Not using php, wordpress or woocommerce, but with the same credit card processor). I know this sort of thing sucks, but few people are in a situation where their products are so in demand that they crush a wordpress host so easily :) also, caching for cloudflare is set way too short right now and the server is having to refresh every 60 seconds .

• 
  STEVExKONG (@STEVExKONG) reported 59 minutes ago

  @SSOUIC @ChatGPTapp It’s probably not a changing design… but a network issue, I got the Liquid Glass UI when I’m on cellular, but if I use WiFi it’s back to the one in your first picture…(can’t change model either) codex said it’s probably due to my wifi returned a challenge from CloudFlare

• 
  Jonathan Workman (@workamania1979) reported 1 hour ago

  @Cloudflare is down

• 
  Sussycat Bloomberg (@LeSussyCat) reported 1 hour ago

  @Cloudflare Put a smile on my face because atleast DDoS is using my ****