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

• 
  Kartik (@kartiksmath) reported 5 minutes ago

  .@Cloudflare turnstiles has saved me from so much pain. We haven't even officially launched yet and we're already being bombarded with malicious bot signups. I can only imagine the problem will get worse as agents get better.

• 
  The TAO Daily (@taodaily_io) reported 6 minutes ago

  The internet is becoming easier to restrict. Cloudflare is moving to block AI crawlers by default. Governments are increasingly shutting down national internet access. So who controls what you can reach? UR (SN25) is taking a different approach. It brings 80,000 residential IP providers across 100 countries and 350,000 users into Bittensor. We covered UR’s two-tier miner economy, token mechanics, and settlement system:

• 
  dc (@d11cc3s) reported 12 minutes ago

  @Eric_M_Courage Open source and publish this on GitHub Pages or Cloudflare? Claude should be able to help you do this if not I might be able to help

• 
  njoii.eth (@DanSFV) reported 13 minutes ago

  Blackwell build update: Today I restored the watchdog layer and got production back to a fully healthy state. The watchdog now continuously checks: • Bridge • Runner A • Runner B • Cloudflare • duplicate processes / port conflicts And the important part: it already caught a real Runner B health failure, restarted it automatically, and returned the system to healthy without me touching anything. That’s exactly why I’m building this layer. A trading system shouldn’t depend on me noticing a service died. The infrastructure should detect the failure, recover, verify the state, and keep the rest of the system isolated. Current state: Bridge healthy Runner A healthy + flat Runner B healthy + flat Public webhook reachable Single listeners only Watchdog active Production is frozen now and I’m waiting for the next natural Volume Profile signal to validate the full entry + exit path. The goal is getting closer to what I want Blackwell to become: not just automated trading. Automated recovery too.

• 
  *yo (blue tick) (@roramora0) reported 14 minutes ago

  @Cloudflare does a neat trick to make its AI chat much harder to abuse. Too bad GLM 5.3 is much smarter.

• 
  The Agentic Operator (@AgenticOperator) reported 16 minutes ago

  By the time revenue drops, the AI visibility problem is already 3 months old. These are the early warnings I track for every client. Red flag 1: AI crawler visits are declining. Check server logs weekly. If GPTBot visits drop from 400/day to 150/day over 3 weeks, something changed. A Cloudflare update. A robots.txt edit. A broken redirect. The crawlers usually leave before the citations disappear. Red flag 2: Citation rate is stable, but citation quality is shifting. You're still showing up in answers. But the framing changed. “Recommended” becomes “one option among several.” “Top pick” becomes “also available.” The mention count looks fine. The endorsement isn't. Revenue follows the endorsement, not the mention. Red flag 3: A competitor starts publishing comparison content about you. The day a competitor publishes “[Your brand] vs [Their brand]” and you don't have your own version, the clock starts. Within 4–6 weeks, AI can start citing their framing of you. You lose narrative control before you realize there's a problem. Red flag 4: Review velocity drops to zero. No new reviews in 30+ days across any platform. AI can treat review recency as a freshness signal. Stale reviews can make a product look stale. Citation rates can follow within 6–8 weeks. Red flag 5: Branded search volume rises, but AI mention rate stays flat. This one is easy to miss. People are hearing about you somewhere else. Then they're going to AI to verify. And AI isn't confirming what they heard. The verification step is failing. They arrive interested. They leave uncertain. Red flag 6: A new competitor starts appearing in queries you used to dominate. Track share of voice weekly. When a new name suddenly appears that wasn't there last month, pay attention. They may have just started their AI visibility work. You could have 4–6 weeks before their presence compounds. Red flag 7: Your product pages are being crawled less than your blog. Check crawler patterns in your server logs. If bots are reading your blog but skipping your product pages, something may be wrong with how the product data is structured. AI crawlers come back to pages worth re-reading. They spend less time on pages that don't give them a reason to return. Here's the part I care about most: Any two of these showing up at the same time is a warning. Don't wait for the P&L to tell you there's an AI visibility problem. By then, you're already late. Catch the signal early. Fix it before the revenue reflects it.

• 
  ⋆˚࿔ blind reading of tf idw comics (@whata_failure) reported 21 minutes ago

  @risottofan7 OK it’s a cloudflare ip being blocked problem. You could try switching to google dns but first try pinging 8.8.8.8 and see if it works before switching

• 
  omen (@ihateinfinity) reported 22 minutes ago

  @dillon_mulroy @atalocke Hey, I need a help unable to pay Cloudflare bill. I am 100% its not my bank since I called them. Payment not going through can you pls check or refer me to someone who can

• 
  Joshua Gardiner (@jgwifi) reported 23 minutes ago

  @Cloudflare Hope you can help. I was double charged for a registrar change. Attempted to open a ticket but the support platform says no tickets for my free account. I asked the AI bot, it says I should be able to open a ticket. Any advice? :)

• 
  Aarsh (@aarshps) reported 23 minutes ago

  @arvidkahl One sleepy us-east-1 morning plus a locked Google OAuth login can take GitHub and Cloudflare DNS off the desk together.

• 
  Michael Flux (@michaelflux) reported 26 minutes ago

  @levelsio The actual stack is intentionally boring: - Structured error on every failure - One JSON log line per console.error / warn with a 32-hex traceId - Cloudflare Observability (logs + traces) enabled on every Worker - Frontend is also Workers (SvelteKit), so client errors travel the same pipe - No external SDK. Just Cloudflare’s native observability + application-level correlation.

• 
  Matt Paulson (@MediaKing) reported 28 minutes ago

  Wild Gmail experience this week. I added a TXT DNS verification record to our return path subdomain (marketbeat dot analyst ratings dot net) in Cloudflare to add it to Google Postmaster Tools. Somehow that caused Gmail to think our CNAME record for that subdomain which points to SendGrid has no valid SPF record. Gmail starts blocking about 30% of our messages because they had no valid SPF record and weren't validated. Took about 36 hours to figure out. I removed the new TXT record and the issue fixed itself within an hour.

• 
  TheHumano.id | Domain for sale (@TakeYourBrand) reported 29 minutes ago

  @jonathan_wilke Probably visitor use old browsers or they access your sites with hijacking data by third operator. Move to cloudflare DNS usually solve problem like that and give secure connection

• 
  Michael Flux (@michaelflux) reported 31 minutes ago

  I don’t use Sentry. I don’t use PostHog. I don’t use any dedicated error-monitoring SaaS. Every single error in my stack - backend, frontend, queues, Durable Objects, etc, lands in Cloudflare Observability the moment it happens. Then a tiny custom toolbar app pings my account every 15 minutes, surfaces any new errors, and I fix them typically within a few hours. Over time the apps just… stop breaking. Here’s the exact system (and why Cloudflare is pretty cool);

• 
  ¯\_(ツ)_/¯ (@spaceforceguy) reported 32 minutes ago

  @zebassembly Cloudflare is your first and only engineering job. You're leading people down the wrong path when you have 0 experience to back up your claims. Dumbest takes from people who haven't even been here a minute.