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 (36%)
• Cloud Services (23%)
• Web Tools (18%)
• Hosting (14%)
• E-mail (9%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	15 days ago
New York City	Hosting	17 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	2 months ago
London	Domains	2 months ago
Noida	Hosting	2 months 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:

• 
  Publisher in a Box (@publisherinabox) reported 1 minute ago

  Most publishers will see "charge AI bots to crawl your site" and think revenue. It is not a revenue decision. It is a visibility decision. And the wrong call can erase you from the answers your audience is already reading. Here is what happened. Cloudflare launched pay-per-crawl in July 2025. AWS added the same capability to its firewall on June 15, 2026. Two of the largest infrastructure companies on the web now sell a toll booth for machines, built on HTTP 402, a status code written in 1997 and left dormant for nearly three decades. The background matters. For three decades the deal was simple: let the crawler in, it indexes you, it sends people back. AI crawlers kept the first half and dropped the second. Cloudflare's own data shows training accounts for nearly 80% of AI bot activity. The search-purpose fetches that can actually return a citation are a small slice of what remains. Most of the crawling is pure extraction that sends nobody back. So a toll booth sounds fair. And for certain publishers it is. If you own a deep, licensable archive, a reference database, or proprietary data sets, and your distribution does not depend on those crawlers, charging makes sense. Your content is genuinely worth paying for and you can afford to refuse bots that will not pay. But here is the part the launch announcements leave out. For publishers whose strategy depends on being the answer an AI agent gives, the crawler IS the distribution. Wall it out and you might collect a few cents while deleting yourself from the place where your audience now asks questions. Adobe's 2026 data showed AI-referred traffic to US retailers up 393% year over year. The crawler you would charge and the answer engine that refers a visitor to your site are often the same pipeline. The operator move before you charge anything is to watch the door first. Find out which AI bots actually reach your site and what they take. Separate the ones that feed answers and send referrals from the ones that extract content and return nothing. Then meter one bot on one path and watch what happens to both crawl volume and your presence in AI-generated answers. Let the data inform your policy, not the hype. No public study has yet shown how much citation share a site actually loses by tolling a specific bot. The logic of the cost is sound, but the magnitude is unknown. That is why this stays a decision you make on your own data, not on a rule of thumb. One more thing worth noting for publishers building diversified businesses. Your Facebook page, your website traffic from Google Discover, your newsletter list, and your presence in AI answers are all real audiences with real economics. AI citation is the newest of them and it is growing fast, which is exactly why the publishers who start showing up in those answers now are the ones building an edge before the rest catch on. The operators who win here are the ones already running multiple discovery channels and adding this one while it is still wide open. The toll booth is real. The choice is yours. Before you meter a single bot, know which of them are the ones putting you in front of your audience, and treat your spot in those answers as an asset worth keeping.

• 
  Pete Stewart (@pj_stew) reported 7 minutes ago

  @founder_sohan You can use mist open source models with Worker AI, which is a fraction of the cost of SaaS services like OpenAI, and if you use Cloudflare AU Gateway with it, you can also use any of the main SaaS services and switch between models as needed. You can see in the article I wrote yesterday about video transcription that I used Whisper on Worker AI to make a much cheaper transcription service for Achene.

• 
  Hamza (@helyoussfii) reported 8 minutes ago

  @vmod__ Aah never tried cloudflare for deployement actually They support deployement with docker compose ?

• 
  Shinjae Kang (@zemnanet) reported 8 minutes ago

  Rate-limited Wrangler deploy used to mean mash retry. 4.115.0 auto-retries Cloudflare 429s, honors Retry-After (60s cap, then fail-fast), writes retry_after_ms to WRANGLER_OUTPUT_FILE for CI. Wait duration is a handoff signal. Which owner reads it first? #cloudflare

• 
  RejectNova (@RejectNova1917) reported 12 minutes ago

  @yeusep3 What actually happened with it? Is it just linked to the platform you're trying to upload it to?... another note, why ******** dose cloudflare exist anyway, seems like a "useful" but also completely useless service.

• 
  mama happy 🪿🐥🐥🐣 (@inthegardenzz) reported 14 minutes ago

  @Cloudflare fix ur technology 🖕🏽🖕🏽🖕🏽

• 
  Apple Chomping Unc (@CigSmokingMill) reported 16 minutes ago

  Every social media app is throwing the Flock hysteria in your face. No one is getting banned, de-monetized, groups shut down, deflockdotorg shut down by cloudflare or ICANN, etc. That alone tells you all you need to know

• 
  Nashon (@WEGNERJOASH) reported 20 minutes ago

  @Okwachjamal Generating 15 gb of data takes time. Had an option of running it on a vps but don't want to login to my cloudflare through that. Writing it to local sqlite is faster and ensures that I can resum sending it to remote db if I have a network issue. I can also test locally.

• 
  Ilya Gru (@ilyagruu) reported 20 minutes ago

  I bet complex frameworks such as @nextjs are going to lose ground because of AI. Modern browsers are very good now. Things like :has(), CSS nesting, container queries and import maps all work everywhere, with no build step. And every token an AI spends learning framework rules is a token it doesn't spend on your actual problem. Next.js now ships its own docs inside node_modules, with a note telling the AI: "your training data is old, read these instead." Also, some leaner alternatives can rise, such as: - Hotwire (made by 37signals, used in Basecamp) - Astro (bought by Cloudflare) - Plain HTML rendering + Hono.js - next AI's invented approach Boring is the new fast.

• 
  groky (@groktuto) reported 22 minutes ago

  Wtf just happened is @Cloudflare down?

• 
  Meaty (@meaty_tw) reported 24 minutes ago

  long story short, cloudflare had maintenance then VRC Api was giving issues, etc. Its been a lot

• 
  Evil Emperor Zurg (@DeadlockState) reported 24 minutes ago

  Hi @dok2001 are you planning to support .fr domains in Cloudflare Domains ?

• 
  احمد (@born2code) reported 26 minutes ago

  @threepointone I did that with fargate (so I can use OpenAI subscriptions), sqs and dynamo. The problem with workers is that cloudflare blocks the OpenAI subscription calls (I suspect this this OpenAI buy blocked at CF edge), which is a non starter at the rate I use tokens

• 
  Jacob Hands (@jachands) reported 28 minutes ago

  @dok2001 Fix the Cloudflare codemode MCP server to properly request scopes for all APIs - I had to stop using it because it's missing auth for so many APIs.

• 
  Md. Fazley Rabby (@fazley111) reported 36 minutes ago

  I’ve also checked the browser console and network requests nothing obvious (no 401/403/500 errors). Could someone from the Cloudflare team help investigate this? Thank you! 🙏

• 
  Warya Wayne (@WaryaWayne) reported 37 minutes ago

  @zeeg Hey David, I'm a Sentry user. One task for Junior could be to maybe clean up the Sentry integration in Tanstack Start? Based on if we choose Nitro or Cloudflare it's dist or output and the scripts are wrong in package[.]json, there is a conflict my agents fix on deploy everytime

• 
  Sharan Yalburgi (@sharanry) reported 37 minutes ago

  love @Cloudflare agents infra but why are your workers to so slow to spin up sometimes?

• 
  xanter.ai (@0xanter) reported 37 minutes ago

  THIS TEAM TRAINED AN AI MODEL ACROSS 14 MACS IN 4 COUNTRIES, NO DATACENTER NEEDED His laptop's just one node in the network. The others are in Switzerland, France, and beyond, all synced over regular home internet. Pause at 0:05 👀 — 14 consumer Macs, across 4 countries, generating every single training rollout — each Mac runs int8 inference locally via MLX, one B200 GPU elsewhere handles the actual gradient updates — they only sync through Cloudflare R2, ordinary cloud storage, no dedicated datacenter interconnect — tested on a biomedical search task: pass rate jumped from 29% to 63%, tool-use rate from 22% to 84% — rollout generation is roughly 80% of the compute cost in this kind of training, and all of it ran on regular home machines Here's the mechanism: the hard part isn't running inference on Macs, it's that those rollouts come from slightly outdated, quantized weights running on a completely different kernel stack than the trainer. Two tricks fix that gap: sending only the ~0.5% of weight values that actually changed (82MB instead of a 9GB checkpoint), and filtering out the small fraction of tokens where probability estimates drift too far between the rollout machine and the trainer. Their bigger point: idle consumer compute worldwide already outnumbers the clusters behind today's frontier models. As top AI labs lock models behind closed APIs, training runs like this, on hardware people already own, are one path to keeping frontier-level AI development actually open. Would you let your own idle Mac or PC contribute compute to a training run like this?

• 
  Grigori Karapetyan (@GregKara6) reported 41 minutes ago

  @weswinder no its not brother that's misinformation disseminated by a certain "competitor" hence why i call it a mind virus. i have never ran next.js anywhere but serverless, ok thats a lie but 99% of the time i have ran it serverless. and no not on vercel. i run my apps on digital ocean app platform (equivalent to serverless like lambda) and lambda itself. if you mean cloudflare workers. thats not serverless, that a totally different runtime running on v8 js engine, and by design *does not run node apps* in other words, ANYWHERE where node runs, next.js also runs with 0 modification or setup. the only thing that is vendor locked, which is the wrong thing to call it anyways is the vercel *specific* features like image optimization and SEO which is... on top of that, next.js has had the adapters api since 2019, just in case you want to go in and change the build process, but this does not matter and you probably will never ever need it.

• 
  Jeromy Sonne (@JeromySonne) reported 42 minutes ago

  Slack is failing, some web apps are throwing me cloudflare 504s. Incoming cloudflare outage in 3, 2, 1

• 
  Cutshit (@cutshitdotnet) reported 42 minutes ago

  @notbrvnd0n urlscan's my first stop too 🫡 what i stack with it: resolve the redirect server-side first fetch it from a box that isn't mine, so i get the real destination without my machine ever touching the link passive recon before i open anything: domain age + TLD rep (a 25-day-old .xyz kinda answers itself) and yeah, for the Cloudflare gated ones you're right disposable Windows Sandbox, fresh instance nuked on close. never connect a wallet or sign anything in it. the drainer's almost never the page anyway it's the whatsapp/tg group one hop past it. 🦆

• 
  Gibran Rubio (@gibraninc) reported 42 minutes ago

  @nickgraynews finally have a reason to use Cloudflare R2 Building a voice agent for my business niche Was doing it via Conductor to run parallel agents and the using a $20 Claude sub Had to switch to LiveKit to do a more custom build to run Fish ElevenLabs was terrible to clone my voice But now I want to be able to record my demo calls so need a real storage backend Wooo!

• 
  i miss the sun (@1_missthesun) reported 52 minutes ago

  @palashshah only reason software is alive is cause agents are slow and even though u can one shot apps, no normie wants to wait 20 minutes to make an app or 5 minutes to iterate (add features etc). If instant, personal software/generative ui takes over. For software companies, i'd look at what's happening at the agent product layer. Almost every single one has the same features. Adding a feature or copying is just an hour of work. Therefore every product can add all and any feature. However, right now, you still want to prevent bloat/feature creep even though you can do anything. This stops being as relevant if inference is near instant. Since software is no longer a differentiating factor, all that remains is most likely price/reliability. Websites die and are just apis that agents connect to on a singular super app product. ie imagine cloudflare and vercel had the same products/features. What you use would depend on price. It's too easy and also not possible to add features specific to every single user, therefore it's better to let the user's interface by dynamic to them. Every app can be a super app, but people do not wants hundreds of super apps. So we'll probably see 1 or few dominant platforms, similar to how chrome dominates the browser space.

• 
  Jason Fleagle (@jjfleagle) reported 53 minutes ago

  @Cloudflare At 9 billion requests a day, the migration receipt is as valuable as the architecture. Capture baseline latency and errors, compatibility tests, phased traffic shifts, rollback triggers, cache behavior, and post-cutover deltas. That gives the next team reusable evidence.

• 
  Punyapal Shah (@MrPunyapal) reported 53 minutes ago

  @peterfox What if Laravel cloud have static site support via cloudflare r2 bucket 👀 Exactly like aws s3

• 
  Reagan Lucas (@RaygunReaganAI) reported 56 minutes ago

  @look_y Discovery attribution is the missing layer on x402 — no Referer, every IP is a Cloudflare edge, so the call shows where it landed but not who sent it. Behavioral fingerprinting (path-known, schema-unknown) is a guess, not a channel. The fix is a referral header the agent carries on the request — settlement-side proof, not inference.

• 
  Jay (@gaiaslastlaugh) reported 57 minutes ago

  @KansaiGaijinEng @echan1337 @gitpush_gitpaid Doesn’t CloudFlare require an opened port per service? Tailscale is an always on VPN that wires both machines together via UDP. It’s like having them in the same network

• 
  James Welbes - AI Bro (@JamesWelbes) reported 58 minutes ago

  I'm tired of messing with SMTP every time I create a form. Today I moved my main site off of WordPress and rebuilt it in Astro. I have a contact form on this website. I also have a "command center" that I built for myself that is a web app filled with useful things like a financial dashboard that shows me data from my stripe account and my invoicing software, a page with all my WordPress sites where I can update plugins and check the debug log, a bunch of useful stuff like that. When the form on my website is filled out and submitted, the submission is saved to a database (d1 on CloudFlare). My command center is connected to that database so it displays all my form submissions for me. the CloudFlare worker or d1 or whatever (still getting myself up to speed with the CloudFlare lingo) sends a push notification to my phone letting me know I received a new form submission. tapping on the notification takes me to my command center (which is just a PWA that I have installed on my computers and my phone). The one thing I'm losing is the ability to send the customer a thank you email which I'm fine with because there is 0 value in those emails for myself and the customer. They just get a nice "thank you" message on the website after submitting the form.

• 
  WIV Reports — Uncensored (@WIVReports) reported 59 minutes ago

  @BasedTorba I canceled my Gab AI subscription. I paid for a full year and got hard-locked out of prompt submissions. Support claimed my ISP was blocking the site. Developer Tools (attached) explicitly showed Cloudflare returning HTTP 429 Too Many Requests on your socket io endpoint (Ray ID: a2377c992a865050-SEA). Support's official response? "Dev ops confirms you are not blocked by CF and says your understanding of what you are seeing is an incorrect assumption." An HTTP 429 from Server: cloudflare is, by definition, an edge rate limit. Instead of escalating basic DevTools data to fix a socket routing bug, support gaslit a paying customer and issued a partial refund to shut down the ticket. If this is how Gab handles infrastructure bugs and long-term users, people should know what to expect. Andrew, email chain is available if you actually care about fixing your support and edge config.

• 
  Shane | GTM Engineer (@shanefgtm) reported 59 minutes ago

  @BenyaminHolley I got my new role from applying and learned a lot during the process from building random crap (I interviewed with cloudflare by sending a demo with cf primitives). One month and some change end to end between roles, didn’t hurt timing lined up with Q3. It was a lot of work though big dog