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:

• 
  Sherlock | DeFi Researcher (@Sherlockwhale) reported 4 minutes ago

  At $139.26, $SPCX is still 3.2% above the offer price, so it has not actually undercut its IPO price yet. But I still don't think it's cheap at $139. For my research, I looked at 31 major tech listings, including Amazon, Nvidia, Google, Tesla, Meta, Alibaba, Uber and Airbnb. Three of them, Spotify, Palantir and Coinbase were direct listing (not a normal IPO), so the final sample was 28 companies. Out of those 28 IPOs: 17 traded below their offer price within one year. 20 fell at least 20% below their first public close within one year. 16 fell at least 30% below their first close. 13 fell at least 40% below their first close. Only eight of the 28 held above the initial closing price during their first year: Nvidia, Google, ServiceNow, Shopify, Zoom, Cloudflare, Unity and Airbnb. Now compare that with the actual IPO price and these eight companies have never traded below it: Nvidia, Google, ServiceNow, Shopify, Twilio, Zoom, Datadog and Airbnb. Now for the actual $SPCX price levels. The median first year low among the 28 traditional IPOs was 37.76% below the first close: $160.95 × (1 - 0.3776) = $100.17 The full 31 company sample and the closest mega platform group both will give you almost the same level, around $100.90. There is also a second way to calculate it. The median first year peak to trough decline was 56.75%: $225.64 × (1 - 0.5675) = $97.59 So, two completely separate measurements converge around $98-$101 and that is why I think $100 should be your first serious bid. If I only use the IPOs launched since 2017, the typical company traded 43.4% below its first close during year one. Applying the same decline to $SPCX gives a price of roughly $91. And among the most heavily hyped listings, the typical decline was around 54.3%, which would put $SPCX near $74. Using its listing high instead gives similar levels around $86 and $79. That is why I see $75-$100 as the most reasonable accumulation zone. The valuation story is also another reason to wait. At $139.26, SpaceX is worth roughly $1.82 trillion, or 97.5 times its 2025 revenue. Even at $100, it would still carry a $1.31 trillion valuation and trade at around 70 times revenue. So, SpaceX could become one of the greatest company ever built, but even a great company can be a bad investment at the wrong price.

• 
  OnlyAWassie (@onlyawassie) reported 12 minutes ago

  @CryptoTomYT @vladtenev Lockin? builders getting Problems because of the copyrights from Rh cloudflare shutting them off if they get reported how you wanna Build something on this chain

• 
  justinmiller's cat (@___727__) reported 13 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Sherif Peterson (@sherifpeterson) reported 14 minutes ago

  Bots just passed humans on the web. Cloudflare puts it at 57.5% of all traffic, a year before they expected it. Run that forward 5 years: browsing mostly disappears. Sites will turn into machine-readable endpoints with a thin human front. Agents do the visiting. Everything gets abundant except attention. Scarcity moves to the human side. Verified-human platforms. Content with a person visibly behind it. Same thing that happened to handmade goods after factories the cheap version wins volume, the human version wins price. At that point a company's personality isn't branding. It's the moat. Creating has never been this cheap. Getting noticed has never been this expensive. Most people will scroll past this stat. That's kind of the point

• 
  Chris AR Blauvelt (@arblauvelt) reported 14 minutes ago

  @Raminson17 @Raminson17 have you had this issue again? From my team “We've tested this, and everything is fine on our end. From **** and dev servers. Could be that in that moment, CloudFlare, reCAPTCHA, or Turnstile took a bit more time to resolve, and the actual donation request afterwards timed out and didn't go through.”

• 
  Shirsha Ghosh (@ghoshshirsha) reported 20 minutes ago

  In September, the sources that teach AI about your brand start disappearing. Nobody's talking about what that means. Cloudflare is rolling out granular AI bot controls. Site owners can now separately allow or block search crawlers, agent crawlers, and training crawlers. And starting September 15, all new domains will block agent and training bots by default on ad-supported pages. The coverage frames this as a publisher-rights story. Fair - publishers are tired of being scraped for free. But run it forward one step, because there's a second-order effect nobody's pricing in: AI doesn't invent what it says about your brand. It assembles it - from comparison articles, review sites, directories, community threads, and third-party guides. Most of which you don't own and never wrote. Now imagine a meaningful chunk of that source layer quietly going dark to AI crawlers. - The comparison page that put you in the top three? Blocked. - The review roundup where you beat a competitor? Blocked. - The directory listing with your current pricing? Blocked. The model still answers the buyer's question. It just answers it from a thinner, more arbitrary slice of the web - whatever's left after the blocking. And nobody sends you a memo when the source that made you look good stops being readable. This is the part that should worry marketers: your AI reputation is built on infrastructure you don't control, and that infrastructure is being renegotiated right now, by other people, for reasons that have nothing to do with you. The brands that survive this won't be the ones with the best SEO. They'll be the ones who actually know which sources feed their AI answers - before those sources go dark. September 15 isn't a publishing story. It's a visibility story with a deadline.

• 
  NOXA (@Noxa_Fi) reported 20 minutes ago

  @jimmy_sjm looks like cloudflare whoopsed on us a bit and the domain went down looked up again a few minutes ago we are investigating why thaey have been blocking ips, but this is also why we have been developing a decentralized solution an interface hosted on ipfs via ens domains, uncensorable

• 
  Ernest Provo (@ernesttheaiguy) reported 23 minutes ago

  A 200 OK status does not mean complete data. Cloudflare found a race condition in hyper that truncated responses silently. Data leaders: never trust status alone. Verify payload integrity. #ResponsibleAI #DataStrategy

• 
  Atharva Verma (@atharva_again) reported 24 minutes ago

  Gpt 5.6 sol just deleted the *** worktree it was working in and tried reading the code from another worktree. On top of that I'm seeing frequent websocket and cloudflare errors. I saw fewer websocket errors in 5.5 and NO cloudflare errors.

• 
  Saint John: Evernode 1:1 Freedom (@AverageJohnEVR) reported 27 minutes ago

  @BitcoinBombadil It has nothing to do with payments x) It actually originate from the creator of BitcoinJS and its purpose is to allow decentralized executions on-chain (multisign) Back in the days people wanted to automate functions, so for example, if you wanted to send fiat to a paypal account and get bitcoin automatically on your bitcoin wallet, then you would need a way to make that into an automated thing. This method would also allow to replace human beings and the human factor from standing in the way. A lot about Bitcoin originates to payments, when it came people wanted to use it for purchases and automated operations. Evernode solves these challenges without interfering with the original technology, it just executes whatever you want, based on whatever you chose. It also replaces traditional hosting with decentralized hosting (instead of having **** behind cloudflare and on jeff bezos servers, you spread it across the globe)

• 
  Stake Exposed ⚖️ (@formatpal) reported 30 minutes ago

  @Stake Code Segregation and Infrastructure Concealment To protect the development team and systematically obfuscate the physical location of the backend infrastructure, a highly secure code-deployment strategy is enforced: Siloed Access (Microservices Dependency): No individual developer in Belgrade has access to the complete monolithic codebase. Tasks are strictly divided: one engineer manages the wallet integration, another maintains a specific game, and a third works on the Risk Engine. Automated CI/CD Pipelines: Code written in Belgrade is committed to enterprise GitHub/GitLab repositories and deployed automatically via secure pipelines (using Docker, Kubernetes, and Terraform). The code is deployed directly to cloud servers hosted by Amazon Web Services (AWS) located in Frankfurt (Germany) and Dublin (Ireland) to minimise latency for European and Middle Eastern players. Cloudflare Enterprise Cloaking: The backend servers are never directly exposed to the public. All incoming traffic is routed through Cloudflare's Enterprise reverse proxy, which masks the real AWS IP addresses. When users attempt to trace the platform's servers, they see IP addresses mapped to the US or Western Europe, completely masking the technical engine room operating from Belgrade.

• 
  Dharmesh Dev (@DharmeshDev) reported 32 minutes ago

  Ran two branches at once today on the AI consultancy business. One track building the website, the other working on the business foundation. Parallel execution instead of sequential — felt like the right call given how much ground both need to cover. Started the website with Codex using Code planning mode to map the build out first. Then implemented the plan and got a working vibe coding prototype up. Version-01 is live and looks solid, though it still needs iterative improvement. A significant chunk is done. Also ran the same website workflow through Claude Cowork and Claude Code specifically to test the Fable-5 model. The output wasn't as impressive as expected — though the problem statement probably wasn't the best test case either. One thing Fable-5 did nail: it suggested a single-page static design with React and Next.js compiled, hosted free on Cloudflare instead of paying for hosting. That's a genuinely useful architectural call worth keeping. On the business side, Claude on Opus 4.6 with medium setting helped identify the 4 key pointers needed to launch the consultancy. Starting with the "Foundational Layer" setup — that's the next piece alongside continuing the website design.

• 
  Domi (@domirosari0) reported 33 minutes ago

  @eastdakota @Cloudflare Just hire me Problem solved 🥸

• 
  Delali (@delali) reported 34 minutes ago

  @DanielSmidstrup Even Vercel, Cloudflare, et al have challenges. For us founders, it never ceases. But I get your point. Let's keep pushing…

• 
  Nick (@heyiamnick_) reported 34 minutes ago

  I needed better media storage for the library. Cloudinary was fine, but the credit-based pricing could get expensive as bandwidth grows. So I moved everything to Cloudflare R2: - Around $0.015/GB - Zero egress fees - Works for images, videos, ZIPs, PDFs, and backups The only problem... R2’s UI is painfully basic. I had to open files one by one just to preview them or copy the URL. So I asked Claude to build a custom media dashboard. Now I can preview everything, browse folders, copy URLs instantly, and automatically sync local media to R2 after every *** commit. Cheap storage + a custom AI-built interface. That is the kind of AI development that is actually useful.