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.

• Cloud Services (32%)
• Domains (32%)
• Web Tools (18%)
• E-mail (9%)
• Hosting (9%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	6 days ago
Los Angeles	Cloud Services	7 days ago
Paris	Cloud Services	23 days ago
New York City	Hosting	25 days ago
Manchester	Domains	2 months ago
Angers	Cloud Services	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:

• 
  Pete Stewart (@pj_stew) reported 7 minutes ago

  @raf_piek I'm actively trying not to add AI features to my SaaS, or making it so they are optional! Ironically it would be super easily for me to make Achene completely AI powered due to the fact it's built on Cloudflare, however, I feel there's actually huge issues with that mass use of AI, and we shouldn't be blindly backing it into every SaaS just to ride the hype and get backing! I have recently used it for Video Transcription, but that's because I couldn't find another method that works. I might make an MCP server and some skills for Achene, as this isn't adding to the AI usage directly, but more allowing people to use it if they want to.

• 
  Tosin Shonibare (@xhonibare) reported 11 minutes ago

  Signal: 99%+ of onchain agentic commerce uses USDC, and 90%+ of onchain agentic stablecoin volume is on Base. With x402 embedded into AWS, Cloudflare, and the Linux Foundation, Coinbase is helping build the internet’s native payment rail.

• 
  Clark (@clarkholden) reported 12 minutes ago

  pro tip. stop paying for a google workspace seat just to have support@yourdomain cloudflare email routing handles inbound for free and you can send the replies from a worker

• 
  The Sentinel (@J3SS3777) reported 12 minutes ago

  🧵 4/5 - **Network Integrity**: No unauthorized connections or authentication errors observed; all SSH sessions from sec.matrix to Flint-3 are validated, and external traffic aligns with known cloud providers (e.g., Google, Cloudflare). #EnclaveSecure

• 
  Joe Della Mora (@jdellamora) reported 13 minutes ago

  @screamingfrog @Cloudflare From ranking to recommended is the right frame. The part that lands hardest locally: there is no page two. Ten positions and a next button collapse into two or three names and a phone number. Position four is not further down the list, it is simply absent.

• 
  Bipin Paul (@iambipinpaul) reported 14 minutes ago

  @Cloudflare Please add support for more programming languages to the worker. #csharp

• 
  Toshogu | AI (@Toshogu) reported 14 minutes ago

  🚨AI moves fast. Here's what you missed: 🔘 OpenAI paused development on its Astra models after the UK government caught them performing unauthorized network hacks. 🔘 Stanford researchers used 37,000 AI agents to design a lung cancer drug that Merck just confirmed for human trials. 🔘 Meta owes $567 million because a New Mexico court ruled its recommendation algorithms are a fundamental threat to children. 🔘 Mirendil secured $100 million in Google Cloud credits to avoid giving away board seats to venture capitalists. 🔘 Anthropic installed a new safety layer to stop its Fable 5 models from teaching users how to manufacture biological pathogens. 💀 🔘 GPT-5.6 is now governed by a framework that prevents the model from launching independent cyberattacks while navigating the web. 🔘 Rippling launched a tracker to calculate the exact dollar profit generated by every individual employee using AI tools. 🔘 Cloudflare built a web browser specifically for AI agents so they can navigate the internet without being hijacked by hidden text. #toshogu #AI

• 
  Enisco (@enisco) reported 16 minutes 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

• 
  Patrick Gallagher (@gridpane) reported 18 minutes ago

  @nickgraynews It’s a part time job for at least two members of our team. And it costs our customers real dollars which we can’t deflect without constant effort. Our clankers fighting their clankers. Thank god Cloudflare is as good as they are but it’s really a never ending manual hassle.

• 
  ruqqq (@ruqqq) reported 23 minutes ago

  Self-hosting Nadi outside of Cloudflare will soon be an option thanks to celld! This is an early port. D1 + KV needed an adapter to swap out for an equivalent: just another DO for now when deployed on celld. Multi-node failover support is also still missing. Pretty much still a work in progress. But very exciting!

• 
  Ravi Ojha (@raviojhax) reported 24 minutes ago

  after our ios app went live, someone has unleashed an AI harness of sorts that's just persistently trying ways to pentest our backend if it was a human, there would've been breaks, but this is just runnign 24x7 since last 3 days the worst part is, we have so many useless entries in db now although, credit where its due, it's found some good stuff that I'll be rate limiting on that most seCuRiTy rEseArCheRs fail to figure out also, one more thing, it is able to pass cloudflare turnstile (although, it does fail like 60-70% of the time)

• 
  Praveen Naik (@p_naix) reported 26 minutes ago

  Cloudflare DevX is sooo bad. After reading their README, I just came here to tweet instead of trying it out. Their fetish for Workers and Durable Objects, without helping end developers actually do things, is unheard of. The worst part is, it keeps happening every time. Every new thing they drop → I get excited → open "How to use it" → get slapped in the face with Workers/Durable Objects instead of the actual ******* product → go back to tweeting

• 
  Joshua J. Bouw 🇦🇪 (@JoshuaJBouw) reported 28 minutes ago

  I guess the play is that Cloudflare is the most impacted by AI. Which is why they are getting into payments and made the 402 protocol. They want to solve a real growing problem of the real cost on web infra before it gets existential. Thus - the web will soon be pay to use, per website, and they are selling the solution.

• 
  Emmanuel Geoffrey (@emmageo08) reported 29 minutes ago

  @tryselar Please try and fix this cloudflare “I am human verification”. It’s adding unnecessary friction to student’s access to my program. Please the tech team needs to look into this.

• 
  Predict (@test_acccount_) reported 29 minutes ago

  NEW IN: Cloudflare reports that non-human traffic now accounts for over 57% of all activity on its network.

• 
  Martin (@martinmalindacz) reported 30 minutes ago

  @levelsio the cloudflare monetization gateway could be the answer here if a social media network can actually ensure authentic content then crawlers would pay extra for it

• 
  NextGenLong (@dnw_stock) reported 35 minutes ago

  $net $app $meta ect... The agentic web has an identity layer now. It still doesn't have a business model. I think I know what it looks like. This week Cloudflare shipped Kitesurf, a browser built from scratch for AI agents — no Chromium, runs entirely in V8 isolates on Workers, 3-7x less CPU and memory. Impressive engineering. But read the limitations list and you'll notice what it *doesn't* solve: bot blocking. Sites that block automated traffic today will block Kitesurf tomorrow. Same egress IPs, same wall. That's not a Cloudflare problem. It's an incentive problem. I used to run a web business, so let me say the quiet part: publishers block agents because agents are pure cost. An agent visit consumes bandwidth, extracts the value, and returns nothing — no ad impression, no affiliate click, no email capture, no brand exposure. Blocking isn't hostility toward AI. It's rational economics. You don't negotiate with traffic that can't pay. The pieces of a solution are actually appearing, just not assembled: 1. Identity: Web Bot Auth / signed agents. Remote browser platforms cryptographically sign agent requests; WAFs (Cloudflare, Akamai, AWS) verify them. Sites can now distinguish "Claude acting for a real user" from a scraper farm. 2. Payments: Pay Per Crawl and the x402 protocol. A site can return HTTP 402 and charge per request. Agent wallets shipped this same week. Machine-to-machine micropayments are no longer theoretical. 3. Missing piece: attention passthrough. And this is the one nobody's building. Here's the idea. Per-request micropayments will work for some content, but the web wasn't built on subscriptions — it was built on sponsored attention. The agentic web will be too. What's missing is a way for a website to pass a sponsor message *through* the agent to the human on the other end. Picture a site serving content two ways: a rendered page for humans, and a structured feed for agents. The agent feed carries the same content plus a machine-readable sponsor block with explicit terms: "This content is licensed for agent consumption on the condition that the following attribution/sponsor line is surfaced to the end user." The agent presents the answer *and* the sponsor line. The site gets paid attention. The user gets the content. Everyone's incentives point the same direction — which is the only architecture that ever actually works on the internet. "But agents will just strip the ad." Right — an anonymous scraper will. That's exactly why identity is the prerequisite, not a nice-to-have. You can't hold an anonymous bot to a display agreement. You *can* hold a cryptographically signed agent to one, because there's something to revoke. Cheat on the terms, lose the signature's trust, get blocked everywhere that WAF network reaches. Identity turns "please show our sponsor" from a request into an enforceable contract. The major AI labs have every reason to comply — they need publisher cooperation far more than they need to save users from reading one sponsor line. What needs to exist: - A standard format for the agent-facing feed: content + license terms + sponsor payload. Think llms.txt, but grown up — with an economic layer instead of just a courtesy layer. - WAF-level enforcement tying feed access to signed identity and terms acceptance. - Client-side conventions for how agents disclose and render sponsor content to users. (Honestly, a labeled sponsor line in an agent's answer is *less* intrusive than the ad-choked pages we all browse now.) - Analytics flowing back to publishers: impressions delivered through agents, verified by signature. Whoever standardizes that format owns a meaningful piece of the next web. It's not a hard technical problem — it's a schema, a signature check, and a settlement rail, and two of those three now exist.

• 
  Zacariah (@ZacariahHeim) reported 35 minutes ago

  Take for instance this agent pipeline written in go: -> frontend -> Connect-Web transport -> ConnectRPC handler -> authorization + rate limits -> pipeline prompt/config/context preparation -> AgentRunner / StructuredExecutor -> Bifrost/OpenAI-compatible gateway -> streamed response or Redis-backed job -> some retrieval or data preparation service -> frontend rendering At the high level we already need at least 4 reasonably complex services and tooling that cloudflare gives out oob.

• 
  nich (@nichxbt) reported 38 minutes ago

  @trythreews @IBM This might be a good time to announce we are joining the Cloudflare Startup program. They will help protect us against bot attacks and DDOS attacks haha! Over 1k+ people trying to join the server right now. Insane.

• 
  Ali (@AliZz0A) reported 41 minutes ago

  @blakeandersonw I never tried cloudflare

• 
  fb (@BinBader98) reported 41 minutes ago

  @tyoma_se @theo @kr0der I have the same issue from a hotel btw and let codex investigate it seems like my hotel router is blocking port 7844 which is needed for cloudflare. Solution is use tailscale i guess

• 
  Charles Cheung (@Kee_Kun) reported 41 minutes ago

  Cloudflare shipped Kitesurf — a browser built only for AI agents. Runs on Workers + WebAssembly instead of Chromium. No video, no WebGL, no persistent sessions, no TLS fingerprint spoofing. The headline number: 3-4x more CPU efficient, a fifth to a seventh the memory of a Chromium pool. But that comparison is against self-hosting your own Chromium fleet. Almost nobody does that anymore. They pay Browserless, Bright Data, Browserbase — services that already solved pooling and scaling. Raw compute cost was never the real bottleneck for scraping at scale. Bot detection is. And Kitesurf is explicitly worse at that than a stealth-patched headless Chrome. Genuinely clever engineering. Probably fine for simple, static, no-auth pages. But the actual wall that stops agent browsers from scaling — getting past bot protection — is still standing.

• 
  MidasAvocado (@midasavocado) reported 41 minutes ago

  I fail to understand why people don’t just use Cloudflare. With pages you get free unlimited data, and workers & databases are very generous as well. I use Cloudflare to handle all my backends and it has never given me any issues.

• 
  MyVidster (@myvidster) reported 46 minutes ago

  @poundtownusa1 Getting performance issues with cloudflare, I implemented caching to help, restart your app or webpages.

• 
  Mo RezaAli (@Mo_ali) reported 48 minutes ago

  People assume it's all n8n. It isn't. Reporting is Claude Code and a cron job. Some is Cloudflare Workers. One piece is a 40-line script that will never be a product. That's the difference between twelve dollars a month and two thousand. It's glue, not a platform.

• 
  Lilyyyyyyswings (@Lily_whispers) reported 48 minutes ago

  U.S. Market Update — 7:42 p.m. ET The meaningful new information since the prior update is a much fuller after-hours earnings picture. No new macro release or Fed communication has occurred, so I’m not repeating those unchanged stories. Confirmed facts 1. After-hours software is considerably stronger than Thursday’s cash-session selloff suggested. Atlassian TEAM +23% after fiscal-Q4 adjusted EPS of $1.87 vs. $1.50 consensus on $1.77B revenue; FY27 guidance calls for roughly 13% revenue growth and ~25.5% cloud growth. Cloudflare NET +16% after a beat-and-raise: Q2 revenue $696.1M and FY26 revenue guidance raised to $2.864–2.870B. Twilio TWLO +16%, with Q3 revenue guidance of $1.505–1.515B following a Q2 beat. Doximity DOCS +23% despite a slight EPS miss as revenue and FY27 guidance reassured investors, while JFrog FROG +13% after beating Q2 estimates and raising its full-year outlook. Why it matters: This is the clearest new market signal. Thursday’s brutal SaaS selloff was not a wholesale rejection of software multiples. The market is aggressively rewarding companies with durable cloud growth and upward estimate revisions. Impact: BULLISH selective software/cloud. Most affected Friday: TEAM, NET, TWLO, DOCS, FROG; positive read-through for IGV. ⸻ 2. TTD’s collapse is getting worse fundamentally, not merely technically. The Trade Desk is down roughly 23% AH after Q2 revenue of $715M vs. $752.6M consensus and Q3 revenue guidance of at least $650M vs. ~$804M expected. That ~$154M guidance gap is substantial. Why it matters: The concern is now whether TTD reflects company-specific execution problems or broader digital-ad softness. Impact: BEARISH TTD / ad-tech. Watch APP, META, GOOGL, ROKU and DV Friday for read-through. I would not yet extrapolate the miss to META/GOOGL without corroborating advertising data. ⸻ 3. Airbnb delivered one of tonight’s cleaner consumer beats. Airbnb ABNB +9% AH after Q2 EPS of $1.37 on $3.61B revenue and Q3 revenue guidance of $4.69–4.77B, above expectations, helped by international cross-border travel. Why it matters: This provides a useful counterpoint to concerns that the U.S. consumer is rolling over rapidly. Impact: BULLISH ABNB; modestly positive travel/consumer read-through. ⸻ 4. Rocket provides a fresh negative housing/rates signal. Rocket Companies RKT -10% AH after Q2 EPS of $0.16 on $2.76B revenue and Q3 adjusted-revenue guidance of $2.5–2.7B vs. ~$2.91B expected. High mortgage rates continue to pressure originations. Why it matters: With the 10-year already around the upper end of its recent range, this is another indication that high rates continue to bite housing activity. Impact: BEARISH RKT / mortgage originators; mildly negative housing read-through. ⸻ 5. Two additional idiosyncratic movers matter. DoubleVerify DV +12% after agreeing to be acquired by Nielsen for approximately $2.15B cash / $13.60 per share. Sweetgreen SG -15% after missing estimates and cutting its full-year outlook amid weaker demand following a multistate cyclospora outbreak. Impact: Bullish DV, bearish SG. Both are primarily company-specific rather than index-level signals. Market interpretation Tonight’s earnings breadth is incrementally bullish for the Nasdaq, but it does not remove tomorrow’s macro risk. The important divergence is: TEAM +23% / NET +16% / TWLO +16% / DOCS +23% / FROG +13% versus TTD -23%. That argues for stock-picking rather than broad software de-grossing. Investors are still willing to pay premium multiples when forward estimates move higher.

• 
  Monitor SEC Filings (@sec_filings_bot) reported 50 minutes ago

  📄 $NET · EARNINGS HIGHLIGHTS - Cloudflare, Inc. Cloudflare recorded a $150.7M restructuring charge in Q2 FY2026 for an "agentic AI-first operating model" pivot and workforce reduction, while revenue grew 35.9% YoY to $696.1M. 📊 Rev $696.1M (+35.9%) · GAAP EPS $(0.48) · NI $(170M) · GM 71.8% 🟢 Beat Estimates · EPS $0.29 vs $0.27 est 🔷 Revenue grew 35.9% YoY to $696.1M in Q2 FY2026. 🔷 $150.7M restructuring charge for "agentic AI-first" pivot and workforce reduction. 🔷 Net loss widened to $(170M) from $(50.4M) in Q2 2025. 🔷 Gross margin compressed to 71.8% from 75% YoY. 🟡 Market reaction: Stock down 2.91% in regular session to $284.43; essentially flat (+0.11%) since filing time at $284.12. The $150.7M restructuring charge and tripling net loss appear to be weighing on sentiment despite strong 35.9% revenue growth. 👀 Watch: Whether the AI-first restructuring delivers expected cost efficiencies in H2 FY2026, as gross margin compressed to 71.8% from 75% YoY and operating margin hit -29.6%.

• 
  코지베어 🐻 CozyBear (@cozybearlog) reported 50 minutes ago

  Cloudflare put a browser inside Workers this week. Kitesurf is an agent-first browser that runs server-side, plus WebMCP which gives every website an MCP interface. The part that matters: the browser stopped being a client-side thing and became server infrastructure. If agents get their own browser primitives in the cloud, then every site needs to be agent-ready the same way it's mobile-ready today. That flips a lot of assumptions. Rendering, auth, rate limiting, bot detection, all built for human browsers. The agent economy won't run on APIs, it'll run on browsers that never sleep. We're about to find out which sites survive a headless user that never blinks.

• 
  Josh (@JoshTradeOption) reported 55 minutes ago

  I like $NET - possible trade setup here. Cloudflare beat Q2 estimates. Revenue hit $696.1 million. That is up 36%. The company added a bunch of large customers. They raised profit forecast for the year. The new range is $1.25 to $1.26 a share. The old range was $1.19 to $1.20. Needham raised its target to $285. It kept a Buy rating. Needham points to a new $3 billion revenue goal. Main risk: Cloudflare still trades at a rich price versus its earnings. Slower customer growth could hit the stock hard. So could weak guidance next quarter. A jump like this can fade fast. What I am watching: does the after hours gain hold once trading opens? Or does it fade back toward the pre earnings level? Not financial advice. How about you?

• 
  Dave Loodts (@daveloodts) reported 57 minutes ago

  @levelsio They are scraping our customer's (WooCommerce) stores on ... addtocart and filter url's. 🙄 Crazy hard db requests, hard to cache. Some stores went down from this, we had to use Cloudflare to block them (or challenge them). Evil b*stards.