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:

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 2 minutes ago

  @Cloudflare Please, fix human verification

• 
  Dan Ryland (@RealDanRyland) reported 2 minutes ago

  @philcampbell Are you using the Resend route or Cloudflare's new email service? I'm a big Cloudflare user and fan so wondering if I could create a product inbox to take all of my various domains into one inbox from forking this

• 
  Phillip Shoemaker (@pbsIdentity) reported 3 minutes ago

  India just ordered hundreds of Google Firebase accounts shut down after authorities found scammers using the platform to impersonate major banks. At least 57 Firebase-hosted websites and databases were targeted for takedown this month alone. Some mimicked banks. Others distributed malicious Android apps. Some were designed to steal financial information from phones. Here's what I find interesting. Firebase isn't some shady hosting company operating out of a basement. It's Google infrastructure. That's exactly why criminals want it. We've spent years teaching people to look for obvious signs of scams. Weird domain. Broken English. Sketchy hosting. Browser warning. No HTTPS. But increasingly the attacker doesn't need to build suspicious-looking infrastructure. They borrow legitimate infrastructure. Google. Microsoft. Cloudflare. GitHub. Dropbox. Whatever gives the attack credibility and reliability. Now imagine the average person inspecting the link. They recognize Google. The connection is encrypted. The page loads perfectly. The certificate is valid. Everything their brain has been trained to interpret as: SAFE may technically be true. Except the person controlling the page is a criminal. That's an important distinction. HTTPS proves your connection to the website is encrypted. It does not prove the person operating the website is honest. A Google URL proves Google is providing infrastructure. It doesn't necessarily prove Google created the content you're looking at. The little padlock was never a morality detector. We just accidentally trained an entire generation to treat it like one. India says scammers have increasingly shifted toward Firebase because its legitimate development tools and database functionality make it useful infrastructure for fraudulent sites and apps.

• 
  Borex Investing (@borex_investing) reported 4 minutes ago

  @ValuePlay52109 Customer count is not published. But publicly we know of Meta, Microsoft, ServiceNow, Shopify, Mistral AI, Revolut, Cohere, Black Forest Labs, Cognition AI, Cloudflare, Recraft, Higgsfield, Antioch, Rhoda, AMI, and Core Automation. And they have said they signed deals with customers that haven't been disclosed yet.

• 
  The Agentic Operator (@AgenticOperator) reported 4 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.

• 
  Tobi (@To_bi_Bakare) reported 5 minutes ago

  It is. But Cloudflare doesn't support Naira, and most Nigerian bank cards are naira-restricted for international payments by default. A few ways around this🧵

• 
  Fabrice NEYRET - pro (@FabriceNEYRET) reported 9 minutes ago

  @KaleyGoode cloudflare is ultra-annoying but usually you can log-in ! (from time to time you need to re-confirm identity once logged + and some days ago the site was down, though). BTW it seems that the unofficial plugin is (sometime?) incompatible with cloudflare.

• 
  matt rothenberg (@mattrothenberg) reported 11 minutes ago

  @itsnoahd @Cloudflare Will fix! Send me a DM plz, wanna ask a few questions

• 
  Affiliate Aura (@TrippieeDaviD) reported 14 minutes ago

  Cloudflare is dropping pay-per-crawl for pay-per-use. You don't get paid when a bot fetches the page. You get paid when the page shows up in an AI answer. That's the affiliate problem in one sentence. The crawl was never the prize. The citation is. Sept 15 they start blocking mixed-use crawlers on ad pages by default. If your offer pages run ads, check the setting before the deadline.

• 
  Ahmet (@ahmetdotrun) reported 19 minutes ago

  two things i've been experimenting with over the last couple of days: 1) kitesurf by @Cloudflare free while in beta. i'm looking at it for (scaled) agentic offensive security work: let an agent explore an app, understand it, map the attack surface. browsers are expensive to run, hard to scale. it seems a lighter option on CF's edge, so potentially a cost effective one for me. tho, bot challenges are still a problem. 2) grok build by @SpaceXAI first time giving grok 4.6 a proper shot. faster than other frontiers and more capable than i expected. burns through the limits quicker than i'd like though.

• 
  Utsav Patel 🇮🇳 (@mr_utsav_patel) reported 20 minutes ago

  @Cloudflare Same card is working with stripe link for anthropic and I tried with 2 different bank cards and both are getting declined, if possible please add support for UPI for your Indian customers until this issue is resolved

• 
  Aarsh (@aarshps) reported 21 minutes ago

  @juiceboy_of_abj Airtel wrapping Cloudflare signup in a dead page is the kind of ISP fingerprint you only notice when a login form never appears.

• 
  njoii.eth (@DanSFV) reported 25 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.

• 
  Ruben de Groot (@rubenpdegroot) reported 27 minutes ago

  @paoloanzn honestly t3code has been doing exactly this for me, i just got one 64gb ram vps on contabo and setup t3code there, i can just use their web ui from desktop or phone (behind cloudflare tunnel for security), you can just clone as many repos as you want ofc, and i just created a skill on how the t3api works such that claude code can just spin up threads inside of it no need for multiple VMs , just one big VPS only thing is that they dont support pi

• 
  Cooper (@GarudaO7) reported 30 minutes ago

  @nsptsaiphanitej yes. edo jio side dns issue anta *.up.railway.app sites ki, cloudflare through proxy cheyali or custom domain use cheyali