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 (38%)
• Cloud Services (30%)
• Hosting (18%)
• Web Tools (10%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	4 days ago
London	Domains	7 days ago
Noida	Hosting	19 days ago
Jewar	E-mail	20 days ago
Braga	Web Tools	20 days ago
Noida	Cloud Services	21 days 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:

• 
  MRCΛULIMΛN (@mrcauliman) reported 6 minutes ago

  $XRP utility check. Magnetic looks like it’s having a hosting issue this morning. Cloudflare is up. Browser is up. Their origin server is timing out. XRPL is fine. The AMM pools are fine. If you’re trying to set a trustline or swap, use Bithomp, XPMarket, Sologenic, First Ledger, or Bear Swap until Magnetic is back. One front end is down. The ledger keeps moving.

• 
  Kaspar Poland (@kasparfp) reported 8 minutes ago

  @QuinnyPig @vmg__0 @Cloudflare They just imported the AWS Account problem and ignored the GCP Solution.

• 
  Pieces by Julian Undav (@piecebyjulian) reported 8 minutes ago

  I also understand that some of the words on pallets changed. PLEASE NOTE THAT the words were minted onchain, so your words are safe! We shifted the hosting site to Cloudflare after so many api calls (why the site was down for a couple of days) Please bear with us. working hard right now

• 
  MaiKaun (@MaiKaun415422) reported 9 minutes ago

  @vanyaSile The thesis is sound: AI agents are scraping the web at scale, publishers are watching referral traffic collapse, and there’s no clean way to charge a bot for access. Cloudflare already launched pay-per-crawl, the x402 payment standard exists, and people are betting on agent-to-machine micropayments. The hard parts, honestly: You’re picking a fight with adoption on both sides at once. Publishers need to install you AND agents need to pay through you. That two-sided cold start is brutal, and the side with leverage (the big AI labs) has every incentive to route around you or strike direct licensing deals, which is what’s already happening (Reddit-Google, OpenAI-publishers). Whoever owns the chokepoint wins, and right now that’s CDNs and identity layers. Cloudflare sits in front of ~20% of the web and can bundle this for free. A standalone infra startup has to explain why a publisher adds another vendor instead of flipping a switch on infrastructure they already run. The defensibility is thin unless you own either the bot-identity/verification problem (hard, valuable) or become the default settlement rail (network effects, winner-take-most). “We let sites charge agents” as a feature gets absorbed. Where I’d actually look: the verification and pricing layer, not the toll booth. Knowing which agent is asking, on whose behalf, and what the data is worth dynamically is the genuinely unsolved part. The payment plumbing is becoming a commodity standard fast. For Transparency: Ofcourse I validated the idea with AI and added some of own flavor!

• 
  ︎Ronnie 👨‍💻 (@rxnnie_tech) reported 10 minutes ago

  @echo_vick reverse is the case here i can only access the cloudflare dashboard with mtn network

• 
  zeb (@zebassembly) reported 11 minutes ago

  @astuyve @boristane Yeah we aren't happy that the limitation has existed for so long either. We're working hard to try to not paint ourselves into a corner when the o11y platform we've built for Workers expands to being used for other products. There are many shortcuts we could have taken to got this shipped sooner but they may have put us in a state where we later couldn't reconcile it with tracing for another product. We're really going all-out for the o11y platform we're building within Cloudflare and that'll inevitably slow things down by preventing us from taking the easy paths.

• 
  Lifeis2-D (@Lifeis2D) reported 20 minutes ago

  Cloudflare: BOTS HAVE OVERTAKEN HUMANZ USING THE INTERNETS FOR THE FIRST TIME Also Cloudflare: *ASSUMES ALL VPNS ARE BOTS, ****** "VERIFICATION" CHECKBOX FAILS* Gee, do we think this "assume vpn users are bots, verification broken" thing and the first thing could be related?🤔

• 
  Sadiq (zk arc) (@Md_Sadiq_Md) reported 20 minutes ago

  @0xRasmPro @Cloudflare @tan_stack Quartz solves 95% of the problems, but the math renders took a ton of time for me to solve

• 
  pathik (@pathikghugare) reported 20 minutes ago

  @NotRoodraksh @4k_isn not working on cloudflare warp

• 
  Jake (@JakeKing) reported 24 minutes ago

  @Cloudflare lead the charge dogfooding their own tools: locked down ALL external AI tool access internally at end of 2025, before their controls were even fully built.

• 
  Josip Petric (@JoPetric) reported 27 minutes ago

  @alex_lrz_nmv As I work in early mornings before my 9-5, I have around 1.5 to 2 hours each morning (+ I have to help with kids and all so, not a lot of time unfortunatelly). So it took me 2 mornings to create a page, find and buy a domain, connect it to Cloudflare, connect to an email client, and connect to Web3Forms. Would it be faster with bitlist?

• 
  Iqra (@AiWithIqra) reported 28 minutes ago

  6. Default DNS Resolution Lag What it does: When your TV tries to load the image thumbnails for an app like Netflix, it uses your Internet Service Provider's default DNS server to find out where those images live on the internet. Think of DNS as the internet's phone book. Why it kills performance: ISP phone books are notoriously slow and incredibly outdated. Often, your TV is not actually lagging at all. The processor is fine, but the TV is frozen waiting for your internet provider to tell it where to download the movie poster graphics. *********** it: Settings → Network → Network Status → IP Settings → DNS Setting → Enter Manually. Change the numbers to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). You will literally watch your streaming apps load twice as fast.

• 
  Jason Fleagle (@jjfleagle) reported 29 minutes ago

  @Cloudflare A 10x scan throughput gain only matters if the downstream loop keeps up: prioritization, owner routing, safe remediation, validation, and evidence that the fix actually reduced exposure.

• 
  𝗕𝗮𝗻𝗸XRP (@BankXRP) reported 29 minutes ago

  @Xaif_Crypto Big names. Bigger signal. 👀 AWS, Coinbase, Amex, Circle, Cloudflare, Google all backing x402 and XRPL just plugged into that same rail via t54. $XRP & $RLUSD now settle AI agent payments on the exact infra these giants are building on.

• 
  Florian E. (@fl_rn_st) reported 32 minutes ago

  @adamc0dez This is a CRAZY price tag. A $5 Hetzner VPS would run this without breaking a sweat. - VPS from Hetzner + Docker (maybe something like dokploy or coolify for automated deployments) - Cloudflare Tunnels for reverse proxy + SSL - Tailscale for SSH (I'd block all open ports on the VPS) Also **** MongoDB, ask Claude to move your application to pg.

• 
  Corey Quinn (@QuinnyPig) reported 33 minutes ago

  Since the way AWS employes used to act (read as: deeply caring about the customer experience) is how @CloudFlare employees currently act, here are annoyances I wish CF would change. A thread.

• 
  Jeff Gray - Cyber Advisor, OT Training Veteran (@JeffGrayCyber) reported 35 minutes ago

  Anyone else get 521 errors when using Cloudflare with Hostinger? very frustrating .

• 
  inder (@InderpreetSingh) reported 36 minutes ago

  Looks like @Cloudflare dashboard is down, but just saw "Organizations Beta". I hope thats the case. All my projects are co-mingled in a single account right now.

• 
  Dorian (@Dorian251362) reported 37 minutes ago

  @RococoRomance It really, really does 🥲💔 It might be a location issue (or device+location) issue since I have heard a few other foreigners having similar problems. But it doesn’t seem like there is any way around it if the cloudflare just decides you are evil 🥲💔

• 
  Yuvi Lightman | Quantus (@YuviLightman) reported 41 minutes ago

  @MooseProductio2 @QuantusNetwork Quantum tech does in fact exist. You are already late. Your original argument was that banks and personal data are more vulnerable. This is false, as I explained. Over half of human generated internet traffic is already post-quantum, secured by CloudFlare. Signal and iMessage are also post-quantum and have been for years. You then said Bitcoin devs have been working on making Bitcoin quantum proof for 8 years, which is also false, but even if it were true it would actually make them look quite bad because you don’t need 8 years to add a new address type. So why don’t you want Bitcoin to upgrade? What is your motivation?

• 
  brale (@brale_xyz) reported 41 minutes ago

  his is not just a blockchain story either. @NIST finalized three post-quantum standards in 2024. @Cloudflare says more than two-thirds of TLS traffic through its network now uses post-quantum key exchange. The migration has already started.

• 
  Adrian Fritz (@adrianwjfritz) reported 42 minutes ago

  5/ Governments and major tech companies are already moving. Most blockchains are catching up. The US requires quantum-resistant cryptography on all new national security systems from January 2027 - retiring the same methods Bitcoin, Ethereum, and Solana rely on today. Cloudflare, Apple, Signal, Microsoft, and AWS are already deploying upgrades. 24 of the top 26 blockchain protocols still rely entirely on methods being phased out elsewhere.

• 
  Turac (@TuracTheThinker) reported 44 minutes ago

  Deploy plane decoupled: Arcane GitOps, HA GitOps, Cloudflare Pages. Agent never touches what it changes.

• 
  UwU Underground (@uwu_underground) reported 47 minutes ago

  @Bluewall [Intro] Private party. Public problem. Wrong target. Watch. [Verse] Velvet rope, clean badge, curated sin, Glass in your hand, don’t ask what’s in, Smile for the brand, behave, obey, Keep it quiet, look away. We brought a fix for a silent crime, You brought optics and a closing line, Director eyes, “not in here,” Funny what “safe” means when fear’s sincere. [PRE] You guard the door, not what’s inside, Polished floors, but rot won’t hide, Call it policy, call it rules Say it clean while you play the fool. --- [Chorus] Kick us out—lights go down, Raise the risk, burn the ground, Call it “ads,” call it noise You just silenced the wrong voice. Hands off—look away, Safety out, keep drinks in play, Let them run it, shift the blame Just to guard your poisoned name. --- [Post-Chorus] Cloudflare! who you protect? (Your brand) Cloudflare! what you block? (Nothing) Don’t act clean—we know the play Still hosting **** you won’t betray. [Instrumental fill] --- [Verse] Sticker on a cup, hit a nerve inside? Or the truth in the room you can’t sanitize? Liability wrapped in a tailored suit, Kick out the fix, keep the threat “cute.” Security theater, scripted lines, “Everything’s safe”, till it’s headline time, “Just infrastructure”, draw the line, Meanwhile threats ride backbone spine. Traffic flows, you don’t intervene, "Not our role", keep optics clean, Till it trends, till it’s seen Then you rewrite what 'neutral' means. --- [Pre] You look away while you harbor threats, Metrics green, but the floor stays wet, Say "not allowed," push us aside Akira, Medusa still inside. --- [Chorus] Kick us out, lights go down, Raise the risk, burn the ground, Call it "ads", call it noise You just silenced the wrong voice. Hands off, look away, Safety out, keep drinks in play, Let them run it, shift the blame Just to guard your poisoned name. --- [Post] Cloudflare, route it through (Still alive) Cloudflare, what you do? (No chill) "Not our job", but dont ask why Till it hits your bottom line. [Breakdown] Simple fix? put it in their hand, Cover the cup? give control, take a stand, Low cost, fast, no need to debate, You killed the fix just to protect your name. We brought a shield, you spun a smear, Turned up the noise so truth won’t steer, Weaponized takes, fed them the line All to keep your optics aligned. While you blocked it, others said "go" Doors stayed open, let protection flow, Gained that ground, built real trust Real ones act, you posture for buzz. --- [Bridge] Real harm’s quiet, you know that part, Doesn’t trend, doesn’t chart, When it mattered, you chose the brand Let safety die right in your hands. --- [Flow Switch] Neutral! till it hits your name, We remember: say it plain, Write it down: we keep the score, Rot runs deeper than before. --- [Chorus] Kick us out, lights go down, Raise the risk, burn the ground, Call it "ads", call it noise You just silenced the wrong voice. Hands off, look away, Safety out, keep drinks in play, Let them run it, shift the blame Just to guard your ******* name. [Finale Chorus] Kicked us out, say it straight (Yeah!) Director call seal the gate (Hey!) Handing out covers, that’s the "mistake"? That’s the move you chose to make. Hands off! no disguise (No!) Said “not here”! no replies (Go!) We showed up, you shut it down Now this is how your name goes down

• 
  Lifeis2-D (@Lifeis2D) reported 48 minutes ago

  The "troubleshooting" link that also leads to a broken/nonfunctional "feedback" form? Yeah that's also kinda ******. When did cloudflare get promoted to internet gater?

• 
  SpikeViper (@spikeviper) reported 59 minutes ago

  I am once again asking @Cloudflare for a response on why their support is radio silent on what is now a shady billing situation

• 
  Didier Lopes (@didier_lopes) reported 60 minutes ago

  For all the talk there is on Saaspocalypse - this is a refreshing take by @danshipper . "Sasspocalypse is dumb" Earlier in the podcast he also talks about his experience using SaaS where more and more of it is being driven by utilizing Codex. I can related with this a lot, as now a lot of times I have Codex open in a specific browser page and I'm working with that app from within codex. IF they support MCP, then I connect MCP as the agent is more efficient by doing so. If they don't, I just let it check the UI view (the same way I do) take screenshot and then click/drag/hover around. It's been interesting to do work this way. It's like I'm looking above the shoulder a pro at something I don't know about - e.g. setting up a Cloudflare environment. Not just it's doing the task but I'm learning from it because I can see what is happening.

• 
  kclich  (@kclich) reported 1 hour ago

  Websites you’ll actually use (and wish you knew earlier) 👀 Temp Mail Disposable emails for quick signups and testing. Down For Everyone Or Just Me Check if a site is down or it’s just your connection. Wayback Machine View old versions of websites and deleted pages. BuiltWith See what technologies any website is using. JustWatch Find where any movie or series is streaming. Temp Number services (e.g. TextNow, Sonetel) Get virtual numbers for verification and testing. CamelCamelCamel Amazon price tracking history (real discount checker). Cloudflare Radar See internet traffic trends, outages, and global insights. Wappalyzer Instantly detect tech stack of any website (browser extension). Have I Been Pwned Check if your email was leaked in a data breach. Remove dot bg Instant background removal for images. Photopea Free browser-based Photoshop alternative. Regex101 Test and debug regex patterns instantly. JSON Formatter (jsonformatter dot org) Clean and debug JSON quickly. Carbon Turn code into beautiful shareable images. Excalidraw Simple online whiteboard for diagrams and system design. What are you using daily that’s missing here? 👇

• 
  Sameer Khan (@sameerr_dev) reported 1 hour ago

  Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

• 
  Jake (@JakeKing) reported 1 hour ago

  Surprised to see that only 50% of internet traffic is now automated. the old "human good, bot bad" binary is dead. @Cloudflare scores every request 1-99 on behavioral trust instead.