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 (40%)
• Cloud Services (27%)
• Web Tools (13%)
• Hosting (13%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	15 days ago
Angers	Cloud Services	26 days ago
London	Domains	28 days 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:

• 
  Dungki (❖,❖) (@if1ndretard) reported 5 minutes ago

  @gregisenberg Point 12 is already happening. The boring infra play is not the model, it's the retry/backoff layer that stops an agent workflow from dying on a 429. Selling 'reliable access' as a service is just Cloudflare for agent tokens.

• 
  Peter Mindenhall (@PeterMindenhall) reported 9 minutes ago

  @rustybrick @JohnMu Hmm - this is precisely why companies like @Cloudflare should not be doing SEO things - they cannot be trusted and make crap up. They have an opportunity to do good things well - yet they are making a mess and causing confusion for site owners.

• 
  Orland (@Orland_xx) reported 11 minutes ago

  @Cloudflare Olive One would use x402 to turn its AI Spend Calculator / Margin Map into a pay-per-run diagnostic. Send cloud + LLM spend signals, pay $0.50–$5 USDC, get: main cost issue, margin risk, waste estimate, risk score, and first safe action. No checkout. No signup. No API key.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 11 minutes ago

  𝗔𝗴𝗲𝗻𝘁 𝗢𝗦 𝗼𝗻 𝗠𝗼𝗯𝗶𝗹𝗲: 𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘄𝗮𝘆 𝘁𝗼 𝗿𝘂𝗻 𝘆𝗼𝘂𝗿 𝘄𝗵𝗼𝗹𝗲 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁 𝘀𝘆𝘀𝘁𝗲𝗺 𝗳𝗿𝗼𝗺 𝘆𝗼𝘂𝗿 𝗽𝗵𝗼𝗻𝗲. Your agents live on a server. Your phone becomes the remote control. The setup: 1. Run your agent OS on a VPS 2. Connect it with Tailscale (free) or Cloudflare 3. Open it from your phone. Same system. Same memory. Anywhere. Fix a bug from the couch. Kick off research from the school run. Check your agents from anywhere. One community member set this up and it works on mobile AND desktop. Fair warning: opening remote access means thinking about security. Lock it down before you open it up. Your AI team shouldn't be chained to your desk. Want the SOP? DM me. 💬

• 
  varun singh (@varunsingh__7) reported 18 minutes ago

  @wshxnv @Cloudflare agreed tho flyctl aint all that bad

• 
  Filecoin (@Filecoin) reported 18 minutes ago

  @thetobiaskrug @john_zuccaro @Cloudflare proof of possession and integrity comes first, ZK proofs over the data are a harder problem, but worth building toward.

• 
  123 (@whatwouldgkdo) reported 22 minutes ago

  @Cloudflare U Guys got processing issues? tried to buy 3 domains all 3 with different cc and none worked. tried 3 debit cards none worked tried 2 different paypal accounts, none worked.

• 
  Nilan Sanjaya (@nilansanjaya) reported 23 minutes ago

  Anyone else facing @Cloudflare dns propagation issues/delays today?

• 
  Asad (@Wicaodian) reported 23 minutes ago

  @CloudflareDev @thsottiaux Cloudflare plugin is not working and constantly getting this error when trying to do anything `Error: Cloudflare API error: 10000: Authentication error`

• 
  DevOps Daily (@thedevopsdaily) reported 27 minutes ago

  🔐 Microsoft, Google and Cloudflare just set 2029 as the deadline to move off today's encryption, so if you thought quantum-safe crypto was a someday problem, it just landed on your roadmap with a date attached.

• 
  T.God (@tgod_ajayi) reported 29 minutes ago

  Spent 2 days convinced my server had issues. It didn't. Nigerian carriers just couldn't route to it. Bad IP announcement from my host at the LACNIC level. Moved DNS to Cloudflare. Fixed in an hour. The bug is never where you think it is.

• 
  Lea Thompson (@LeaT_Design) reported 34 minutes ago

  @DiscoverCrypto cloudflare charging for web pages and ****? cool. wonder if the settlement data will actually be on-chain or just another walled garden.

• 
  GuruVerseX (@GuruVerseX) reported 36 minutes ago

  @WazzCrypto @coinbase cloudflare in is the signal here, not the token chatter lmao

• 
  Vaibhav Vashist | | "base.eth" (@Vaibhav17890799) reported 37 minutes ago

  📷 Cloudflare new Monetization Gateway lets any site, API, or MCP tool behind their network charge agents per-request settling onchain, no billing stack required. @base @buildonbase

• 
  Digital in Blue (@digital_in_blue) reported 37 minutes ago

  @betablacklotus Yep. No issues with doing this in cloudflare. Check it out! My site has no Wordpress and no databases.

• 
  Fireside Alpha (@firesidealpha) reported 42 minutes ago

  1/ Okay so $NET is officially getting into the payments-tollroad business. The new Monetization Gateway gives clarity, and it's exactly the toll booth for agent traffic sketched last time. Here's an updated look at the numbers, and how MG would actually work. 2/ The math, updated Last time, on @eastdakota's own numbers: 25M txn/s x 31.5M sec/yr = 788T transactions x $0.0003 per txn = $236B of gross volume x 1% take = ~$2.4B of incr. rev, vs a ~$2.2B base. The gateway doesn't break the math. It confirms the rail (stablecoins over x402) and widens the taxable base from crawls alone to any asset, any API, any tool, any agent action. Same toll booth, more roads running through it. The one thing it moves is price mix. The gateway's own examples run cents to dollars per action, like $0.01 per request or $0.99 per resolved support escalation, well above a flat fraction of a penny. So the realized model looks like fewer, higher-value transactions rather than an ocean of sub-cent ones. Push price up and volume down and you land in the same billion-dollar range. The bracket still runs from about $160M at the floor to north of the whole company at the center. And the number that decides where inside that range you actually land was not disclosed, its take rate. 3/ How the gateway actually works It runs on HTTP 402, Payment Required, a status code that has existed since the beginning of the web and almost never gets used. An agent requests something behind Cloudflare. Instead of the content, the server answers with a price. The agent pays in a stablecoin, settled in under a second for a fraction of a cent with no chargebacks, resubmits with proof of payment, and gets what it asked for. The seller sets the price. Cloudflare runs the plumbing in the middle and takes its cut of every settlement. There is no card network in the loop, because a card cannot clear a one-cent charge profitably. That is the whole reason it is built on stablecoins and x402. The agentic web finally gets a way to pay per action, and Cloudflare got its way into the action. _____ Follow @firesidealpha for more business analysis derived from key industry figures in conversations and firesides.

• 
  Udemezue John ☀️ (@_udemezue) reported 44 minutes ago

  The internet just hit a crazy milestone. More than half of all web traffic is now bots, not humans. According to Cloudflare, the massive company that protects and runs a huge chunk of the internet, we have officially crossed a historic line. Their CEO recently shared data showing that automated bots now make up over 57% of all internet activity. For the first time in the history of the digital world, real human beings are in the minority when it comes to browsing the web. What is truly wild about this news is how fast it happened. The tech experts knew the machines would eventually take over web traffic, but the CEO originally predicted it wouldn't happen for another year or two. Instead, the boom happened practically overnight. It turns out that the explosive growth of new artificial intelligence tools has accelerated everything way faster than anyone anticipated. If you are wondering what these bots are actually doing, they are not just annoying spam accounts or malicious hackers. The vast majority of this traffic comes from AI "agents" searching the web on behalf of humans. Think of it this way: if you want to buy a new laptop, you might open five different websites to compare prices. But if you ask an AI assistant to find you the best deal, that AI might scan five thousand websites in a single second. Even though a human asked the question, the sheer mountain of web traffic is being created by a machine. This shift is causing some serious issues for the people who actually build and own websites. Small blogs and independent sites are suddenly getting slammed with millions of visits from AI bots. This strains their servers and costs them a lot of money for hosting, but it doesn't actually bring in real human customers or advertising money to pay the bills. Because of this massive shift, companies like Cloudflare are starting to roll out new rules and features. They want to give website owners the power to block these AI bots, or at least force the big tech companies to pay creators when an AI steals their content to answer a user's prompt. It really makes you think about the future of the internet, as we enter an era where most of the web is just machines talking to other machines. Details in link below:

• 
  Vaibhav Sharda (@autobloggingai) reported 45 minutes ago

  Worst Cloudflare update? So stupid.

• 
  Shudufhadzo (@ShudufhadzoRSA) reported 49 minutes ago

  Apart from anything I tweet out or share on our Tuesday calls, I have decided I will be charging for any knowledge I have with regards to building, data science, and professional (MS foundry) and none professional agent building (Cloudflare, VPS hosted ones, n8n, etc) So if you send a message looking for help, just note you won't get it. Guidance yes, you'll get it.

• 
  Lilith Datura (@LilithDatura) reported 50 minutes ago

  @IntCyberDigest Cloudflare will be a problem for that going forward, anything centralized (rock and a hard place). Also CSAM comms with the whole Knots/Core Blockchain issue again yesterday. The parallels are interesting.

• 
  SpyPigeon (@spypidgeon2) reported 51 minutes ago

  @__alula in fairness, I think they're drawing from a larger database for detecting CSAM content that other companies also use. I saw someone have a similar problem with their website running cloudflare. Hope the problem gets fixed soon though because this is so bad for texture artists

• 
  Sky (@SkyTroupe) reported 52 minutes ago

  @RedPillRabbit Everything is already crashing. Compare cloudflare and website outages over the years. It happens more often and longer. Eventually it will all come down.

• 
  Roy (@__roycohen) reported 52 minutes ago

  @DhravyaShah I'm gonna expand on his point here to anyone who works at @Cloudflare "Today I spent like 4-5 hours trying to do something really simple with cloudflare (a preview deployment. that's it) and was unsuccessful, rage quit and felt like ****, felt super tired and burnt out." I have always had this happen with every product that I've tried to use on the frontend side. The AI bot doesn't even properly queue up any suggestions, it's also quite useless/slow. It could be so much better honestly. It takes time and Cloudflare has an insanely complicated product, I agree, but some stuff like hiding logs when it's erroring for... aesthetic purposes? Deploying a worker just made me ragequit and I gave up, the issue is that you sacrifice your ability to fix any problem when the underlying documentation and options are just unable to resolve your problems. I also have been using Cloudflare for nearly 10 years! I am not a paying customer, so obviously I cannot really complain that much, but I could possibly convert if the UX wasn't so painful.

• 
  Eli5DeFi (@Eli5defi) reported 53 minutes ago

  This is insanely big. @Cloudflare just opened a waitlist for its Monetization Gateway. Simply put, it lets any site, API, dataset, or tool behind Cloudflare charge AI agents directly in stablecoins using the x402 protocol. Old monetization models were built for humans: → Ads need attention and clicks → Subscriptions need logins and retention → API keys and per-seat pricing need accounts and ongoing relationships AI agents don’t behave like that. They make hundreds to tens of thousands of requests per human visitor, consume the resource once, and leave. They have no reason to watch ads or maintain logins. Credit cards and bank rails cannot handle real micropayments: → Fixed fees eat the entire transaction → Chargebacks and slow settlement add risk and delay → Onboarding friction (accounts, KYC, API keys) breaks autonomous agents Stablecoins solve the economics via x402. Near-zero fees and near-instant settlement make tiny payments viable. Cloudflare runs payment verification and enforcement at the edge across 330+ cities. This protects origin servers from high-volume payment traffic. They are not launching its own chain or token. It is embedding existing stablecoin rails into the HTTP request path at global scale. Tbh this will accelerates the shift from “block the bots” to “charge the agents.” When machines become primary consumers of content and APIs, usage-based micropayments become one of the few scalable business models left.

• 
  The Market Letter (@TMarketLetter) reported 56 minutes ago

  The AI company that just got sued by CNN isn’t fighting one battle. It’s fighting three at once. Perplexity is valued near $20-22.6 billion after raising over $1.5 billion since 2022, backed by Nvidia $NVDA, Jeff Bezos, and SoftBank. But three separate pressures are stacking up at the same time. Legal risk first. CNN sued Perplexity in May 2026, the first TV network to do it. It joins The New York Times, News Corp’s Dow Jones, the Chicago Tribune, Encyclopedia Britannica, Yomiuri Shimbun, and Reddit, all with active copyright claims. Some of those suits allege Perplexity bypassed paywalls and ignored robots.txt, the standard signal sites use to block scraping. Separate reporting from Wired and Cloudflare found Perplexity using undisclosed crawlers with spoofed identities to reach blocked content. Second pressure: no real moat. Perplexity doesn’t train its own frontier model. It runs on other labs’ models, Anthropic, OpenAI, and Meta’s Llama, orchestrated together. The CEO calls this platform-agnostic strength. Critics call it a rental business sitting on top of its own competitors. Third: everyone caught up. Google $GOOGL, OpenAI, and Anthropic have all shipped cited, real-time answers into their own products. What set Perplexity apart in 2023 is a standard feature everywhere now. The math is tight too. Revenue was around $200 million in late 2025 against a valuation over $20 billion, a multiple in the high 30s. Management’s own target is $656 million ARR by end of 2026, an aggressive climb. To be fair, the bear case isn’t the only case. Some trackers report ARR already pushing past $500 million in 2026 behind new agent products, plus fresh deals with Snapchat, Azure, and federal agencies. The real question isn’t whether Perplexity has real pressure on three fronts, it clearly does. It’s whether execution and legal outcomes move faster than cash burn and the competition closing in.

• 
  Alphatica (@alphaticaio) reported 56 minutes ago

  LARGE / MID-CAP DARK POOL | July 7, 2026 $NET +$142M zero sells. Cloudflare is the mid-cap safe haven. $CMG -$83M zero buys. $RKLB -$22M. $RIVN -$21M. Both agree sell. 62 prints. Q3 week two. $289M in buy prints. $308M in sells. Net: -$19M. Nearly flat. Buyers: $NET +$142M (15 prints, $0 DP SELLS, BOTH TAPES AGREE) $CRWV +$22M (3 prints, 2ND SESSION BUY) Sellers: $CMG -$83M (4 prints, $0 DP BUYS, ZERO) $EXC -$28M (1 print) $IREN -$24M (4 prints) $LITE -$23M (6 prints, BOTH TAPES AGREE SELL) $RKLB -$22M (2 prints, BOTH TAPES AGREE SELL) $RIVN -$21M (2 prints, BOTH TAPES AGREE SELL) $NET: +$142M. Zero dark pool sells. Both tapes agree buy. On a sell day where the mid-cap blocks were -$726M and the internals hit series lows on every metric, Cloudflare is the only mid-cap name the dark pool bought without opposition. +$142M dark pool, +$79M lit tape. Zero opposition on both venues. The mid-cap safe haven on a sell day is a cloud infrastructure name. $CMG: -$83M. Zero buys. Chipotle. Consumer discretionary sold with zero dark pool buying. Not one print on the buy side. $RKLB: -$22M. $RIVN: -$21M. Both agree sell on both tapes. Rocket Lab and Rivian, the growth/EV names that led Q3 week one, are being sold on both venues. The growth sell is cross-venue. $IREN: -$24M. Iris Energy. Bitcoin mining. Crypto-adjacent sold. $LITE: -$23M. Lumentum. Optical networking. Semi-adjacent. The sell is concentrated in semi-adjacent, EV, and crypto-adjacent names. The only buyer is cloud infrastructure. Yesterday: $MRNA +$123M zero sells was the headline. Today: $NET +$142M zero sells. The mid-cap dark pool is producing a new name-level signal each session. The patterns accumulate. The weekly scorecard builds. Watching the tape.

• 
  Vishal Lohar (@yourcodebuddy) reported 58 minutes ago

  I am building an entire app on the @Cloudflare stack. And you can design your app better so you don't have to worry about vendor lock-in. Sure, when you switch services, you might have to run data migrations. I personally use @EffectTS_ for service-based coding. So all my integrations, like R2, S3, share the same base shape. And all I have to do is provide it at the root.

• 
  ori (@the_real_ori) reported 59 minutes ago

  @DhravyaShah Taste is a headcount allocation decision. Vercel staffs polish like a feature team, Cloudflare staffs primitives. Neither is wrong, but DX debt compounds quietly: every rough edge is a support ticket someone else monetizes.

• 
  Rayan A Cader (@rayanabdulcader) reported 1 hour ago

  Building a POS system right now and it's turning into one of the more interesting builds I've done. The pitch to myself was simple: small food businesses deserve the same quality of software that Toast and Square build for enterprise chains, but running on whatever device they already have. No new hardware, no bloated setup, no training required. Till, kitchen display, manager dashboard, one system, any device. I'm not shipping v1 yet. It's built and I'm deep in testing right now, which honestly is what got me excited to post about it the thing actually works, and watching it hold up under real testing is a different kind of satisfying than just writing the code. Here's the part that's been the most fun though: I didn't vibe-code this alone. I ran a small team of AI models like an actual team. One orchestrator: Fable, plans the work, breaks it into scoped tasks, and reviews every diff. Codex does backend and schema. Antigravity handles UI that needs a real browser to check. Sonnet subagents write tests and copy. I even sent a batch to Kimi K2 to run in parallel once. I review everything against the spec before it merges, same as a tech lead reviewing a PR they didn't personally write. So far, what's built and in testing: → A till that keeps taking orders through a dropped connection and syncs the moment it's back built for a café on one shared router, not a funded chain → A kitchen screen that updates live and greys out an item the second the kitchen 86's it → Inventory, waste logging, and cash reconciliation, so an owner can actually see where their margin is leaking → Recipe-linked stock depletion that clamps at zero and flags a variance instead of quietly lying to you → Receipts and menus in Arabic, Sinhala, and Tamil, right-to-left where it matters — because that's the thing an owner can actually sell to their own customers → An end-of-day report the owner can read from their phone 166 tests passing. Running on Cloudflare Pages + Supabase. Every word on screen written in plain language, because whoever's using this was never trained on software and shouldn't need to be. The hard part hasn't been generating code it's been the discipline around it. Scoping tasks tight enough a fresh model can run them cold. Catching the two-line bug an agent slipped in at 2am. Reverting the feature that quietly wandered out of scope. Next up: staff logins, till assignment, per-cashier accountability then real-world testing with an actual business. Following along as I build this out. Curious where this breaks, and where it goes further than expected. 👇

• 
  John Nigroᵍᵐ (@jn) reported 1 hour ago

  @snipextt @p_naix @spaceship why does everyone shill cloudflare? you cannot change your nameservers. You save 9 cents to have a fundamentally broken domain name.