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%)
• Web Tools (14%)
• Hosting (11%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	18 days ago
Angers	Cloud Services	29 days ago
London	Domains	1 month ago
Noida	Hosting	1 month ago
Jewar	E-mail	1 month ago
Braga	Web Tools	1 month 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:

• 
  Camilo Peñalver (@camilopenalver) reported 0 seconds ago

  Cloudflare blocks AI bots by default without asking you first, and that's bad.

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 2 minutes ago

  The fix: → Blocked the IP range in .htaccess and CSF firewall → Added rate limiting via mod_ratelimit: 100 requests/minute per IP → Enabled Cloudflare Bot Fight Mode (free on all Cloudflare plans) → Added robots.txt rules to block known commercial scrapers → Enabled Cloudflare's "I'm Under Attack" mode for 24 hours Bot traffic: dropped to near zero within 4 hours. Bandwidth: back to normal the next week.

• 
  Price Action Lab (@priceactionlab) reported 9 minutes ago

  @boleroo Bots are a huge problem and Cloudflare is doing a good job, but no one understands the second order effects.

• 
  SHELBY (@Precious_Ngan) reported 10 minutes ago

  If the website uses a CDN (Content Delivery Network) server like Microsoft Azure CDN, Fastly or Cloudflare, the DNS server will send the IP address of the CDN server instead of the website's original IP address.

• 
  Aryan (@aryan_xv) reported 13 minutes ago

  @Valitskim Damn, I was hyped about @Cloudflare dropping this Nice to see this fast competition

• 
  Thomas Ankcorn (@thomas_ankcorn) reported 17 minutes ago

  @uphiago @LukeberryPi This site would be free on Cloudflare no issue

• 
  ZEE (@CodeWithZeee) reported 19 minutes ago

  @oljimenez @NathanFlurry I mean with companies like Cloudflare especially but also true for some AWS and GCP services, the tech and infra line is pretty blurred which adds to the conversation… take a message queue or distributed event bus for example you could argue you could augment the infra with the tech, use a library that’s backed by a specific platforms infra but in reality using something like googles pubsub over aws SQS isn’t going to be plug and play there’s a level of lock in regardless so it feels like fighting the fight is kinda pointless. the alternative is significant investment in abstraction which any good software engineer knows can be a curse if reached for too early into a product or companies life cycle. So yes lots of nuance but I still stand by it being something that isn’t as big as people make it out to be… dig in focus on solving the problem

• 
  Hajime Hoshi (@hajimehoshi) reported 19 minutes ago

  @Piechutowski * GitHub Pages requires GitHub Actions YAML, which is difficult to test on local machines * GitHub Actions is sometimes down * Cloudflare Pages' loading speed is way much faster * Cloudflare Pages supports redirections

• 
  Jen (@atryeu1) reported 20 minutes ago

  @CriterionDaily @THR Fix or get rid of CloudFlare! Started locking me out with "browser not supported" 9 out of 10 tries to load the site but works fine the 1 try. My browser is up to date & fine. CloudFlare is a broken piece of crap everywhere it's used.

• 
  Vikas Kumar (@Kumar_Vikas__) reported 26 minutes ago

  i'm building on @Cloudflare right now. Workers for hosting, D1 for the database, R2 for object storage, KV for caching. but i'm not trusting any of it to stay forever. every service sits behind an adapter in my architecture. app logic never talks to D1 directly, it talks to a data layer that happens to be backed by d1 today. same story for R2 and KV. if any one of these becomes a problem later, cost, limits, whatever, i want to swap it out without touching a single line of business logic. decoupling isn't glamorous work. you don't get to show it off. but it's the difference between a migration and a rewrite. if you've done this on Cloudflare before, tell me what broke.

• 
  Echoes of Strength 💪🏾 (@telymn_ent) reported 28 minutes ago

  Cloudflare Careers For Support, Security, Engineering.

• 
  JustSomeGuy (Bi) 🇿🇦 (@JustSomeGuy2705) reported 29 minutes ago

  @VixenCurious Just use a VPN to get around in. Warp is a free VPN by Cloudflare its safe and should fix this

• 
  John Serrao (@serraotweets) reported 31 minutes ago

  @powerbottomdad1 I think it probably comes down to how long investors allow those hyperscalers to be cashflow negative. Maybe another year or two? The real alpha is who can do inference cheaply and generally have an agentic friendly platform. Cloudflare and Vercel seem like the two most likely winners on that front, IMO.

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 34 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Quis ut Deus? (@HierB4TheAC) reported 43 minutes ago

  @Dimi7ri @realsedepicante A pen name on the internet is irrelevant. Even if you use a VPN youre not anonymous. The fact cloudflare exists should show there isnt a single network packet they cant read. They know everything everyone does on the internet.

• 
  codellyson (@codellyson) reported 44 minutes ago

  @Cloudflare social login is not working. thank you

• 
  Mills (@MillsNotMiles) reported 44 minutes ago

  @Kolar_Dev @softwareengng @EOEboh Yeah Cloudflare free tier doesn’t support this

• 
  Vivek Kotecha (@vbkotecha) reported 45 minutes ago

  In 1995, the HTTP 402 status code was written into the specification. "Payment Required." Nobody implemented it. In 2025, Coinbase revived it. In 2026, Cloudflare, AWS, and the Linux Foundation all built production infrastructure around it. x402 has now processed 169 million payments across 590,000 buyers and 100,000 sellers. Not projections. Settled transactions. A 31-year-old placeholder in a protocol document became the payment layer for machine commerce. The infrastructure was always there. It waited 31 years for a customer that wasn't human.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 45 minutes ago

  @nithitsuki cloudflare tunnels solved the no public ip problem for every indian homelab, genuinely

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 46 minutes ago

  The fix: → Blocked the IP range in .htaccess and CSF firewall → Added rate limiting via mod_ratelimit: 100 requests/minute per IP → Enabled Cloudflare Bot Fight Mode (free on all Cloudflare plans) → Added robots.txt rules to block known commercial scrapers → Enabled Cloudflare's "I'm Under Attack" mode for 24 hours Bot traffic: dropped to near zero within 4 hours. Bandwidth: back to normal the next week.

• 
  Manfred Neustifter (@supermanfredX) reported 46 minutes ago

  @Cloudflare The worktree name (which is the issue name)

• 
  Alex Prompter (@alex_prompter) reported 48 minutes ago

  Cloudflare opened a waitlist that lets you charge AI agents every time they touch your API, your dataset, or your content. The tool is called the Monetization Gateway, and the waitlist opened on July 1. Any web page, dataset, API, or MCP tool sitting behind Cloudflare can carry a price. Cloudflare checks for payment at the edge when an AI agent requests one, before the request reaches your server. Payment runs through x402, an open protocol built on a part of HTTP that's sat unused for about three decades. The server answers a request with a price instead of the resource. The agent pays in stablecoins and sends the same request again with proof attached. Prices can run down to fractions of a cent, since payment adds almost no overhead to the request. There's no checkout page, no account, and no API key required. This isn't Cloudflare's first swing at this. Pay Per Crawl already let site owners charge crawlers for scraping their content. The Monetization Gateway extends the same idea to any caller and any resource, not only crawlers. AWS added a similar payment layer to CloudFront a few weeks earlier, so this is turning into a race between the two biggest edge networks, not a one-off experiment. Charging an agent per request only works if the agent's owner lets it pay instead of finding a way around the paywall. Cloudflare can enforce the toll at the edge. It can't force an AI company to route its agents through the paid path instead of the free one. If you run an API, a dataset, or a paid tool, this is worth watching instead of dismissing as another crypto payment gimmick. The waitlist is open. Will AI labs let their agents pay the toll, or keep finding ways around it?

• 
  Ifee Anthony (@IfeeDev) reported 48 minutes ago

  @levelsio @Cloudflare Didn't get into gmail or didn't enter inbox? If you set up postfix+dovecot, and encryption properly and do your dns setup, you should at least be able to get the email sent. If it gets sent back, check the bounced email log for the reason. And also ensure your host doesnt block email port. Many hosts do this I can help you set up email service on your machine. This will be able to send and receive. Also for me, I configure mine in a way I can use Gmail as sending client via IMAP, and also forward to Gmail too. This is convenient so I dont need to install another mail agent just for reading or composing. I will do this for a fee though. When I am done whatever you like you give me.

• 
  Salina Mendoza (@inababi) reported 49 minutes ago

  @Cloudflare @OpenAI Damn what a loss. What does this mean? I hope this doesn’t mean we all signed up to share our data with OAI. I will need to reevaluate my entire stack if so.

• 
  Shinjae Kang (@zemnanet) reported 50 minutes ago

  Workers Cache changes the deploy check: a cache hit means your Worker never runs and CPU time stays at zero. So the proof is not just “URL works” — verify headers, tags, purge path, and the first miss. Which one do you test first? #cloudflare

• 
  Dino-Man (@DinoMan389961) reported 51 minutes ago

  @Cloudflare I could never change something that is a banger, localhost forever

• 
  Bhaskar Thakur (@BTofficiel) reported 53 minutes ago

  @NirantK @immortaldip @Cloudflare Can't you rename the older versions? Would that be a problem with compliance?

• 
  Codemonger (@codemonger00) reported 54 minutes ago

  Startup Founders Pack - Claude = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build .

• 
  Piyush Chandwani (@piyushxcreates) reported 58 minutes ago

  @kalashvasaniya @scrolllaunch I'd suggest buying an vps and installing coolify, hardening it by no root login and passkey based ssh and adding cloudflare tunnel in front... I've an 8 gb ram and 150gb ssd, which hosts 3 next js apps, 4 static sites and I pay $10/month with max security via this setup

• 
  Vishwanath Patil (@patilvishi) reported 59 minutes ago

  Sysatem desing fundamentals - Day 26 CDN Explained: Why Netflix, YouTube & Amazon Feel Fast Everywhere Have you ever wondered... Why does a website hosted in the US load quickly in India? Or why does Netflix stream smoothly even though its servers aren't in your city? The answer is: CDN (Content Delivery Network) What is a CDN? A CDN is a network of servers distributed across multiple geographic locations. Instead of every user requesting content from one central server... They receive it from the nearest edge server. Origin Server │ ┌─────────┼─────────┐ ▼ ▼ ▼ Edge US Edge EU Edge India │ │ │ Users Users Users Without a CDN Every request travels to the origin server. India User │ │ 12,000 km ▼ US Server Higher latency. Slower page loads. With a CDN The request goes to the nearest edge location. India User │ ▼ CDN Edge (Mumbai) │ (Cache Hit) Much faster response. What Does a CDN Cache? ✔ Images ✔ CSS ✔ JavaScript ✔ Videos ✔ Fonts ✔ PDFs ✔ Static APIs (where appropriate) Instead of downloading these files repeatedly from the origin... The CDN serves them locally. Cache Hit vs Cache Miss Cache Hit User │ ▼ CDN Content is already cached. Very fast. Cache Miss User │ ▼ CDN │ ▼ Origin Server │ ▼ CDN Cache Updated The CDN fetches the content once, stores it, and serves future requests locally. Real-World Examples - Netflix Movies are cached on edge servers close to viewers. - Amazon Product images and static assets are delivered from nearby CDN locations. - React Applications Files like: main.js styles.css logo.png are commonly served through a CDN. Popular CDN Providers - Cloudflare - Amazon CloudFront - Akamai - Fastly - Google Cloud CDN - Azure Front Door Key Takeaway A CDN doesn't replace your server. It reduces the distance between users and your content. Less distance means lower latency, faster page loads, and a better user experience. Tomorrow we will answer a question many developers ask: Browser Cache vs CDN vs Redis - What's the Difference?