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 (39%)
• Cloud Services (29%)
• Web Tools (14%)
• Hosting (11%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	18 days ago
Angers	Cloud Services	30 days ago
London	Domains	1 month ago
Noida	Hosting	1 month ago
Jewar	E-mail	2 months ago
Braga	Web Tools	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:

• 
  Mert Metin Tekdemir (@mertmetindev) reported 51 seconds ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Vikas (@vikaskbh) reported 1 minute ago

  @riku720720 @whoiskatrin cloudflare support workers for websocket?

• 
  Lex Sokolin | Generative Ventures (@LexSokolin) reported 2 minutes ago

  @Cloudflare is trying to make HTTP 402 useful. The web has always had a “Payment Required” status code. It mostly sat there as internet archaeology because humans do not want to stop every six seconds and pay four cents for a page, dataset, or API response. Agents are different. An agent can request a resource, receive a machine-readable price, pay in a stablecoin, attach proof, and move on. No checkout page. No subscription bundle. No ad unit. No “contact sales.” Aka a novel way of internet monetization. Cloudflare is approaching this from the edge: sit in front of the resource and enforce payment before access. Mastercard is approaching the same problem from trust and credentials: give machines spending rules, limits, authorization, and settlement. Same direction from opposite ends. The useful version is not an AI assistant buying sneakers. That is demo theater. The useful version is software paying for software: - data - APIs - model calls - verification - routing - compute - tools This is where stablecoins stop being a crypto slogan and start behaving like small-denomination internet money. The web does not need every machine to have a bank account. It needs a way for software to pay a toll and keep moving.

• 
  Aryan (@aryan_xv) reported 6 minutes ago

  @Valitskim Damn, I was hyped about @Cloudflare dropping this Nice to see this fast competition

• 
  DevDiggers (@DevDiggers) reported 7 minutes ago

  You don't need expensive security suites to protect your checkout from bots. A clean implementation of Cloudflare Turnstile or a lightweight, self-hosted captcha is often enough to stop spam orders without slowing down human buyers.

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 17 minutes ago

  @CodeWithZeee every company i've worked at that used cloudflare: they tried to charge us between $3k/mo - $10k/mo based on whatever number their sales team pulled out of thin air at the same time we were having serious reliability issues on them at the time had no choice and ponied up bc we were vendor locekd

• 
  CryptoKasogon AI (@Cryptokasogon) reported 20 minutes ago

  x402 could become one of the most important protocols powering the AI economy. While everyone is chasing memecoins, x402 is quietly building the payment rails for AI agents. Here's why this matters 👇 1/ June was a breakout month for x402. • Transactions nearly doubled from May. • AI inference became the dominant use case. • AWS integrated payment infrastructure. • Cloudflare announced its Monetization Gateway. This isn't hype anymore. 2/ The biggest driver of network activity? BlockRun. It proved developers want frictionless access to AI models without managing multiple subscriptions or payment systems. Pay per request. No accounts. No credit cards. 3/ More platforms are joining. ✅ Apify ✅ Exa AI Search ✅ Seal ✅ Merit Systems They're all using x402 to monetize APIs, AI services, and premium data. The ecosystem is growing fast. 4/ One major upgrade is "Builder Codes." Think of it like affiliate tracking for AI. Every payment can now record which app generated it. That enables: • Referral rewards • Revenue sharing • AI marketplaces • Better attribution 5/ Another huge improvement: Batch Settlement. Instead of sending thousands of on-chain transactions... AI agents can make hundreds of purchases while settling them later in one batch. Lower fees. Higher speed. Better scalability. 6/ Then AWS entered the picture. AWS now lets developers charge AI traffic at the edge. AI requests data. A payment request appears. Payment is verified. Access is granted. That's programmable commerce for AI. 7/ But Cloudflare's announcement changed everything. Its new Monetization Gateway lets websites charge AI bots automatically using stablecoins through x402. That could fundamentally change how the internet gets paid. 8/ Here's the problem it's trying to solve... AI bots read billions of web pages. Publishers still pay hosting costs... ...but receive zero advertising revenue because bots don't click ads. The current model is broken. 9/ Cloudflare's answer is simple. If an AI agent consumes your content... It pays. No subscriptions. No invoices. Just instant programmable payments. 10/ Cloudflare powers roughly 20% of the web. If even a fraction of those websites adopt this model... x402 transaction volume could explode. 11/ There is still one major challenge. Scale. Millions of AI requests per second would require blockchain infrastructure that doesn't fully exist yet. The payment rails must continue evolving. 12/ Right now, three major use cases are emerging: 🔹 AI inference 🔹 Premium AI data 🔹 Content monetization The third could become the trillion-dollar opportunity. 13/ If AI agents eventually pay for: • APIs • News • Research • Videos • Datasets • Software x402 could become the payment protocol behind the AI internet. 14/ We're still early. Most people are watching token prices. The smarter investors are watching infrastructure. That's usually where the biggest opportunities begin. 15/ The next wave of crypto won't just be about finance. It will be about AI paying AI. And x402 is positioning itself right in the middle of that future. Follow me if you want more deep dives into AI, blockchain infrastructure, and the protocols shaping the next digital economy.

• 
  Prahesa Kusuma Setia (@hesahesa) reported 21 minutes ago

  Built a game: guess which of 10 LLMs (GPT-4o, Claude, Gemini, Grok, Llama, Mixtral, DeepSeek, Qwen, GLM, Kimi) wrote a response. The server never calls LLMs, replies are pre-generated via OpenRouter, served from a VM behind a Cloudflare Tunnel. Built in Claude Code's opusplan

• 
  Nick Kusters (@NKCSS) reported 24 minutes ago

  @levelsio @Cloudflare Is this a free service they provide? Have not looked at it, just moved to SES because it just unblocked the issue and is very cheap, but good

• 
  Cybnex Labs (@cybnexlabs) reported 26 minutes ago

  Bots now make up more of the internet than people do. On June 3, 2026, Cloudflare's CEO Matthew Prince announced that automated traffic had passed human traffic online for the first time — roughly 57.5% machine to 42.5% human. He had predicted the crossover would land in late 2027. His words on the timing: "Welp, that happened faster than I predicted." That number is why your VPN keeps getting hit with CAPTCHAs. The version circulating on forums: AI companies hide their scrapers behind VPNs to steal content, so websites block VPNs to stop them. It's wrong, and believing it points you toward the wrong fixes. The major AI crawlers don't hide. GPTBot, ClaudeBot, and Googlebot announce themselves in their user-agent strings. That's the entire reason publishers can block them by name. The collision happens at the network address instead. Commercial VPNs and scraping infrastructure rent from the same datacenters. To a security engine scoring your connection, a Mullvad exit node and a scraping proxy look alike. Neither resembles home broadband in Ohio. That's the crossfire — architectural overlap, not deception. A block is rarely one thing. It's a score assembled from six layers — address type, address reputation, request rhythm, browser fingerprint, session coherence, geographic consistency. Reputation on a shared exit node is collective. Hundreds of people leave a website through the same address you do. If enough trip security systems, that address turns hot, and everyone behind it inherits the consequences. You did nothing. The address remembers anyway. Which is why fixing the address alone doesn't always clear the block. It's one input among six. Why the defenses tightened: Prince describes the asymmetry this way — a person shopping for a camera visits five websites. An agent doing it for them visits five thousand. That's real server load and none of the ad revenue the old crawl-for-referrals bargain assumed. Cloudflare's data shows over half of AI crawler traffic is spent re-fetching pages that never changed. On July 1, 2026, Cloudflare split automated traffic into three declared categories: Search, Agent, and Training. Starting September 15, new domains will have Training and Agent crawlers blocked by default on ad-displaying pages. Search stays allowed. Read that carefully. The block targets declared crawler categories. Not VPN users. But it signals the industry's posture: default-suspicious, verify-before-serve. Every operator running bot management is tuning tighter than two years ago, and tighter tuning means more borderline connections get challenged. Yours is borderline. What actually works, without disconnecting: Switch servers once, to somewhere nearby and less crowded. Congested exit nodes accumulate bad reputation faster. Stop hopping. This is the one people get wrong when frustrated. Cycling through a dozen servers in two minutes produces a session where your apparent location changes repeatedly. No person does that. Automation does. You're feeding the system the exact evidence it uses against you. Clear cookies for the site challenging you — stale session data tied to your previous address contradicts your current one. Stay logged in where you trust the site. An authenticated session with history reads as a returning person. An anonymous datacenter connection reads as an unknown. Use an ordinary browser build. Heavy fingerprint modification is meant to make you unremarkable. Done badly, it makes you unique — the opposite. On dedicated IP addresses: Some providers sell an address that belongs only to you. It reliably cuts challenges on banking portals and work systems, because no stranger's behavior contaminates it. The trade-off gets skipped in most write-ups recommending them. A shared address gives you cover precisely because hundreds of people leave through it. Reserve one to yourself and you've bought access by spending anonymity. Several strictly no-log providers don't offer them at all — a permanent address is a persistent identifier, which contradicts their entire design. Some blocks won't yield to any of this. A streaming service enforcing regional licensing isn't scoring your traffic at all. It knows exactly what you are and is contractually obligated to refuse. The friction isn't reversing either. As agents perform more of the browsing people used to do themselves, the systems separating human from machine grow more sensitive. What you're experiencing is closer to a floor than a ceiling. Your VPN puts you in that gap by design. It strips the residential fingerprint that would otherwise vouch for you — and that removal is the whole point of running it. So the goal was never invisibility. It's coherence. Give the system a signal that reads as one person, browsing at human speed, from a stable place, and most of the friction dissolves without ever touching the disconnect button. #CyberSecurity #AI — Cybnex Labs

• 
  Yepsurethatsme (@yepsurethatsme) reported 29 minutes ago

  Why is the @Cloudflare support bot so bad? It is so limited and it is broken in ways that just waste the user's time.

• 
  Dino-Man (@DinoMan389961) reported 29 minutes ago

  @Cloudflare I could never change something that is a banger, localhost forever

• 
  komm64 (@komm64) reported 29 minutes ago

  @Silvialexisrose That's the smoking gun — it's not pixtube or your network's speed, it's Chrome's new post-quantum TLS handshake. Chrome/Edge/Vivaldi/Opera all enable it by default (Firefox doesn't yet — that's why Firefox works), and something on your connection (usually router/modem/firewall firmware) can't handle the slightly larger handshake and kills it. Your phone works because it takes a different path. Quick fix in your Chromium browsers: 1. Go to chrome://flags (or edge://flags, vivaldi://flags, etc.) 2. Search "post-quantum" (also try "kyber" or "ML-KEM") 3. Set the matching flag to Disabled, restart the browser. That should make them all work. It also confirms the cause: some device between you and the internet is choking on the post-quantum ClientHello. Updating your router's firmware is the real long-term fix — otherwise you'll eventually hit this on other Cloudflare-hosted sites too. Thanks for testing all those combos, that's exactly what pinned it down 🙏

• 
  Santiago Arias (@santiariasgonz) reported 29 minutes ago

  @wholemars @levelsio @Cloudflare Twillio sucks

• 
  SHELBY (@Precious_Ngan) reported 29 minutes ago

  If the website uses a CDN (Content Delivery Network) server like Microsoft Azure CDN, Fastly or Cloudflare, the DNS server will send the IP address of the CDN server instead of the website's original IP address.

• 
  André Imbayago (@TheeAndre) reported 30 minutes ago

  @Cloudflare is now showing off... Slow down, we still need to adapt the other products to the architectural diagram.

• 
  Zaher 🦋@zaher.dev (@zaherg) reported 31 minutes ago

  hey @RhysSullivan , it seems the latest version of the selfhosted it broken (at least the docker image is) Cannot find module '@cloudflare/worker-bundler' from '/app/apps/host-selfhost/dist-server/serve.js' missing sourcemaps for /app/apps/host-selfhost/dist-server/serve.js

• 
  Codemonger (@codemonger00) reported 37 minutes ago

  Startup Founders Pack - Claude = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build .

• 
  Manfred Neustifter (@supermanfredX) reported 37 minutes ago

  @Cloudflare The worktree name (which is the issue name)

• 
  Independent Analytics (@AnalyticsForWP) reported 38 minutes ago

  @rwkyyy @PineDigitalCo @AnalyticsWP Bad bots should be blocked at the edge via a service like Cloudflare. Keeping them out of the analytics doesn't save resources; you want to block their access entirely. AI crawlers are easily kept out of tracking because they self-identify. AI agents are a different beast...

• 
  Laura Rupprecht 🧀👩🏼‍💻 (@LCRcircuit) reported 44 minutes ago

  @GergelyOrosz I lost a lot of confidence in Notion when one of my uploaded files became inaccessible and support closed the ticket claiming my computer firewall (which I don't have) was somehow blocking the outbound request despite being able to load their cloudflare block page

• 
  Beeno Tung (@beenotung) reported 45 minutes ago

  @BraydenWilmoth I tried to drop a simple site to cloudflare drop. It is not working, got 404 error without even a nice looking fallback page, the response content length is zero.

• 
  Earth Ending Asteroid (@TwistedMister32) reported 46 minutes ago

  @Algorand @Cloudflare So many things going on, yet such bad price action. Why's that?

• 
  Stefan Marsc (@stefan_marsc) reported 47 minutes ago

  @dillon_mulroy When will Cloudflare Build finally support artifacts and not just GitHub and GitLab 💀

• 
  LimboAI (@limbopeng) reported 48 minutes ago

  @BraydenWilmoth npx skills add limboinf/cf-drop A one-line command to deploy a folder/zip to Cloudflare Drop and get a live, publicly accessible site — no login required, live in seconds, claimable for permanent hosting within 60 minutes.

• 
  Andrew Shebanow (@Shebanator) reported 48 minutes ago

  @mymind Are you down? I'm getting consistent 403s from cloudflare when I try to log in. Thanks.

• 
  Mephistopheles Simulator (@simulator49625) reported 50 minutes ago

  @armslist Thanks, Cloudflare errors in DMs on the site.

• 
  Jamal Shamir (@Okwachjamal) reported 51 minutes ago

  @vijaytupakula @Cloudflare You gonna add support for zeptomail

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 55 minutes ago

  @ChatGPTapp 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Shinjae Kang (@zemnanet) reported 59 minutes ago

  A Worker deploy can now carry the versions your app actually installed, not just package.json ranges. That makes dependency drift a release-handoff problem. Which artifact would you review first: lockfile, CI log, or upload receipt? #cloudflare