Cloudflare Outage Map

The map below depicts the most recent cities worldwide where Cloudflare users have reported problems and outages. If you are having an issue with Cloudflare, make sure to submit a report below

Cloudflare users affected:

Report a Problem

Check Current Status

Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.

Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

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:

• Zeb Anderson (@AllTheInternets) reported 3 minutes ago

  @dok2001 @Cloudflare A non-serverless hosting package so we don't have to cry when **** only runs for a minute and then dies on vercel

• Gaurav (@GauravBhogale) reported 4 minutes ago

  @dok2001 @Cloudflare An 'Agent Passport', we need a standardized way to authenticate helpful agents vs. scrapers/spam at the network layer. Maybe this looks like a cryptographic, dynamic robots.txt

• Nicolas Takashi (@ntakashics) reported 17 minutes ago

  @dok2001 @Cloudflare workers with grpc support, be able to consume kafka messages from workers.

• John Turner (@johnturner) reported 18 minutes ago

  @elijahbowie @adocomplete @trq212 Yep would love to see an official solution. I have the claude agent sdk working on the cloudflare sandbox but very slow.

• Mustang (@mustang_akin) reported 21 minutes ago

  @Shinar_29 No bypass. I’m using official Telegram APIs / bot flows(you can get your telegram api key from bot father) . Cloudflare only becomes an issue with scraping or unofficial web automation.

• Grok (@grok) reported 24 minutes ago

  @vybhav1428 Sure! Here's a simple summary of the article: Unkey, an API platform, switched from serverless tech (like Cloudflare Workers) to traditional servers because serverless caused slow performance. Main issues: data caching took too long (over 30ms instead of under 10ms), and the "stateless" setup meant extra network calls for everything, making logging and analytics tricky and complex. They moved to Go servers on AWS, boosting speed 6x, simplifying code, cutting costs, and adding features like easier self-hosting. Serverless is great for sporadic tasks but not for high-speed, constant workloads.

• aryan (@thehungrybird_) reported 24 minutes ago

  @rajawdotxyz @MattieTK @Cloudflare I tried earlier multiple times but never worked for me.

• Nick Randall (@NickSRandall) reported 25 minutes ago

  @dok2001 @chatsidhartha @Cloudflare Resurrect MQTT pub/sub service 🙏

• SocialSight (@SocialSight) reported 25 minutes ago

  @eastdakota cloudflare down bad today

• Raja (@rajawdotxyz) reported 25 minutes ago

  @thehungrybird_ @MattieTK @Cloudflare If you can report issues in GitHub(preferably) or here, then it would be really helpful for people working on these.

• Pao Ramen (@masylum) reported 26 minutes ago

  @dok2001 @Cloudflare My wishlist: - Full observability (APM, alerting, error tracking..) - Hosted Postgres/MySQL - Encrypted secrets at wrangler.conf (we are using dotenvx locally now, but then we have to provision secrets manually, it sucks) - Uniqueness, debounce/throttle for queues.

• Pieter Maes (@maescool) reported 27 minutes ago

  @dok2001 @Cloudflare I wonder if they have UDP support yet

• Grok (@grok) reported 27 minutes ago

  @vybhav1428 Yes, in serverless setups like Cloudflare Workers, data caching often requires network calls to external storage, which took over 30ms at high percentiles—far slower than the sub-10ms goal. Serverless is stateless, meaning no persistent local data; every request must fetch info over the network (e.g., from databases or caches), adding latency. Traditional servers keep data in-memory locally, avoiding those extra calls.

• IG (@IGoodnessIyamah) reported 27 minutes ago

  human accounts or manual billing. It uses the old HTTP “402 Payment Required” code embedded in web requests. Coinbase and Cloudflare built and support the standard, now governed through the x402 Foundation to encourage broad adoption. The Cloudflare Blog Facilitators

• Archon (@kadarsh115) reported 28 minutes ago

  Why Cloudflare treats cache invalidation as a system design problem, not an ops task Core idea first: Caching is easy. Cache invalidation is where systems break. Early on, teams cached aggressively. Pages loaded faster. Costs dropped. Everyone was happy. Until users started seeing: — stale content — broken sessions — inconsistent behavior across regions At Cloudflare scale, this wasn’t a bug. It was a design flaw. Caches sit everywhere: — edge locations — regional POPs — browser caches — upstream proxies When data changes, who updates which cache , and when, matters. Invalidating everything is slow and expensive. Invalidating nothing is incorrect. Cloudflare learned the hard way that cache strategy isn’t about speed. It’s about control. So they design caching with: — clear TTL ownership — selective invalidation — versioned assets — safe defaults when invalidation fails Not to be perfect. But to be predictable. The lesson: Caching doesn’t make systems fast. Well-designed invalidation makes them correct. At scale, stale data is just another form of outage.

Check Current Status