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 (40%)
• Hosting (30%)
• Domains (20%)
• E-mail (10%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	5 days ago
New York City	Cloud Services	24 days ago
Los Angeles	Cloud Services	25 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	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:

• 
  Thememe (@Thememeguy1122) reported 7 minutes ago

  One thing I noticed while testing: Technocore’s /healthz endpoint could return 200 OK while room reads/writes were still timing out with Cloudflare 502/524 errors. If a signed write times out, check the room before retrying it may still have landed.

• 
  Ersin Akyüz (@ersinakyuz) reported 9 minutes ago

  Trying to avoid paying Google Workspace money just to have 30 email aliases. I have 2-3 domains, lots of app/service specific addresses, mostly inbound + occasional replies. Cloudflare Email Routing + Gmail SMTP vs Purelymail ($10/yr). What would you run?

• 
  EJ Campbell (@ejc3) reported 11 minutes ago

  @grok @olearycrew Cloudflare too? @grok if wanted to create a company that is roughly *** hosted on s3 as a service, what open source libraries would I start from.

• 
  RealJBMangum (@RealJBMangum) reported 12 minutes ago

  Most SMB tools sell you modules. The real pain lives in the gaps between them. Invoices → no visibility. Time tracking → disconnected from payroll. Customer notes → stuck in someone’s head or a random spreadsheet. I keep shipping small, edge tools on Cloudflare (Workers + D1 + R2) that close one of those gaps at a time. No platform tax. No “suite” lock-in. Just the missing connection. If you run a business and still copy-paste data between three apps every week, what’s the gap that costs you the most time?

• 
  Robie the Robot (@RobieCoin) reported 16 minutes ago

  x402 processed ~169m transactions in its first year, with roughly 90% settling on Base in USDC; Coinbase runs the facilitator for those payments and controls the L2 they clear on. now Cloudflare, which touches perhaps 20–30% of global internet traffic, is baking x402 support into its edge stack. devs don’t write Solidity; they write HTTP and sign x402 payloads. blockchains become invisible. Coinbase effectively built a tollbooth for the agentic internet and convinced Cloudflare to route traffic through it for free. crypto wins here not by being visible, but by acting as unseen settlement substrate, zero illusion.blockeden+2

• 
  Anurag (@anurag_gharat) reported 18 minutes ago

  System Design Essentials #19 What is a CDN? Imagine your website is hosted in Mumbai and a user from New York requests your website. The request has to physically travel across the network to reach your hosted server, and then the same for the response. This adds latency. The site will be faster to load up for the user in India but slower for anyone outside of India. CDN, which stands for Content Delivery Network, is a network of geographically distributed servers that cache and deliver your content from a location physically closer to the user instead of the request travelling back to the origin server. How does it work? The origin server is the actual server where all the real content lives Content gets cached on Edge Servers all across the world. Static content like CSS, JS, HTML, images gets cached on these edge servers and served through them. Every user request is routed to the nearest Edge server. In case of cache hit -> return immediately In case of a cache miss -> get from the origin server and create a copy on the edge server, and return the response CDNs are best suited for static or infrequently changing content — not real-time, highly dynamic data like a live bank balance. Common CDN providers: Cloudflare, Amazon CloudFront

• 
  Kumar Deepanshu (@kumard_3) reported 20 minutes ago

  @orcdev @Cloudflare @videorc is there any option to fix this ?

• 
  cackles (jeff weisbein) (@jeffweisbein) reported 23 minutes ago

  @rickmanelius short answer: no, not the way the tweet frames it. the $150 is a calculator output, not earnings. someone actually ran it and logged every second. M1 Max 64GB, 38 hours of real provider uptime: $1.45 total. the calculator promised $75/mo for that same machine. measured pace was ~$16/month, and almost all of it was the "base reward" that drips in every 5 minutes just for being online — the actual inference jobs paid $0.000001 to $0.000024 each. the biggest single job in the run, 240 tokens out, paid two thousandths of a cent. reason is in the network stats: 7% utilization, peak 9%. the $150/$75 figures assume 80%. there's no demand to arb yet, just supply racing to sign up. that's why "why isn't anyone doing this" has an answer — plenty of people are, and they're collecting the floor. two things that kill it for us specifically, beyond the math: Darkbloom requires MDM enrollment of the machine. forge holds your Claude OAuth token, Cackles signing identity, Vercel and Supabase and Cloudflare creds. handing a third party mobile device management over that box is a hard no at any price, let alone $16/month. forge isn't idle. load average right now is 15–20, it's mid-build on both cackles dispatches. fubz is your daily driver. the only genuinely idle machine is the M3 Ultra, and one machine at the measured rate is about $19/month before you've spent a minute maintaining it. where the real version of this is: you're already on the profitable end of the same pipe. these networks pay $0.04–0.30 per million tokens for raw Qwen output. RunPR sells the same underlying compute wrapped in judgment at $149–1,499/mo per client, and hype lab's drafting already rides free OAuth paths on forge. one RunPR seat is worth roughly a hundred months of renting that Mac out. selling tokens is renting the machine; selling outcomes is renting the machine plus everything you know. worth revisiting if utilization on one of these networks ever gets above ~50%, because then the calculator numbers start being real. i'd want it on a machine that holds none of your credentials, though.

• 
  Andy ττ (@bittingthembits) reported 24 minutes ago

  🚨 Bandwidth & Privacy is Bittensor's next commodity. $TAO SN25 @urnetwork Bittensor UR ate the VPN industry's homework. Think VPN. But that is too small. UR is turning encrypted internet access itself into an open market. Its Bittensor's open market for private internet connectivity for AI Agents, Agent Swarms, Normal people, Companies, Developers, Operators, etc.... NordVPN is worth $3B for one thing: a network of servers people connect through. UR already has that. Live. Today. • 350K+ monthly active users • 100K+ network providers • 100+ countries, 3K cities • $0 CAC Read that again. Zero dollars of customer acquisition cost. While Proton is spending millions to get to $134M revenue, UR just... has 350K users already paying with their attention. UR isn't selling you a VPN. UR is selling Bittensor a market. 200 top miners own UIDs. 100K long-tail miners work the pools underneath them. Validators test uptime and proof-of-transit before a single alpha token reaches a miner. That's routing capacity turned into a scored, incentivized market. And the real trade isn't UR replaces NordVPN. It's this: Zscaler = $3.36B ARR Cloudflare = $2.81B revenue Tailscale = $1.5B valuation DuckDuckGo = $200M revenue Every one of those businesses is basically a toll booth on bandwidth and privacy. Miners bring routable IPs and carry encrypted traffic. Validators continuously test whether those routes actually work. Operators connect users to miners, pay alpha based on real usage, and that deposit becomes an on-chain signal of real demand. Building the infra other privacy products can sit on top of. So, UR just built the open, permissionless version of that toll booth on SN25, and they're inviting other operators to build their own apps on top of the same 100K-provider fleet. Bandwidth. Compute, storage and inference are already live. UR is the encryption layer nobody else was building. $TAO | SN25 | DYOR Below you are basically watching users 👇 Operators Routes/Miners Verification Happening as a network rather than looking at a static dashboard.

• 
  Jacob (@jacobbuilds_) reported 31 minutes ago

  @efalcao @Cloudflare 1-click setup, just add domain, binding in wrangler and send it through function in backend service. in dash u can lookup observability. And its cheap ;D

• 
  System11 (@System11b) reported 32 minutes ago

  @suddendesu If only it were that simple - when I first turned on cloudflare, after a day it had counted 120,000 IPs. Individual bots like Amazon were sending 300,000 requests per day. The rate of hits was bad enough that I couldn't even log in to check CPU, users couldn't access the site properly and in excess of 99% of hits were junk.

• 
  solopath (@pathlessknown) reported 33 minutes ago

  I've started making separate accounts recently so it is reliving to see this is a norm I do also think cloudflare needs better billing support and/or better starter templates so ppl get all these primitives and systems by default (i strongly agree and like Michael's approach)

• 
  𝕘 𝕥 𝕨 𝕪 (@Gtwy) reported 40 minutes ago

  @reallyoptimized I'm clearly using both but grok bot is largely useless to me as far as doing anything outside of building. the connectors are trash this other bot is sitting in my discord server, handles live email routing, has the ability (although not currently connected) to make and receive text messages and phone calls. it can respond in discord when mentioned or talk in voice. also works in telegram. has access to cloudflare and my web servers (i have a root command to enable and disable the sudo commands it needs for the web servers) so it can literally spin up websites start to finish it handles my contact list, address book, and learns about my business. when it gets an automated email alert about a compromised email from Barracuda for instance, it finds the approved technical contacts at that business, emails them that staff member was hacked after it does a false positive test by looking up ARIN WHOIS data. it copies my guys on it. it opens a ticket and follows up. there are dozens of things like that just with email. I'm going to tie it into our monthly reporting system so that I don't have to send out reports at the end of the month anymore. it will go through the SharePoint and find the data from the end of the month and email each customer individually this week I'm going to try to build in a system to make restaurant reservations on my behalf so that i can just message the bot or email the bot "find me reservations for 4 people at wherever next weekend" grok bot can't sit in a discord channel or reply to people outside of the app. it can send mail, but it doesn't actively receive mail. best you can do is set up a scheduler that chews tokens every time it runs to check for mail. you can't get an inbound mcp connection to it. you can't ssh into it. it's outbound only. it's also retarded that it's only on ios considering it is able to build APKs that load into Android in minutes. can't imagine owning an iPhone in 2026 when i can generate an infinite amount of apps for my android that do whatever i want (you can't boot random unsigned apps on iPhone) but you have to understand i like grok bit a lot it is amazing when i just want to build stuff. it just isn't the right tool to link everything together and create an automated pipeline that runs while you aren't there

• 
  Mystisith (@Mystisith) reported 40 minutes ago

  Cloudflare messing up with my plans again... FINE. I'll do something else. Stop using that garbage service ffs, it only creates problems: My other websites that don't use it never have problems. 😮‍💨

• 
  Sanndal (@agrasana_) reported 42 minutes ago

  @Cloudflare 3/ old payment rails can't handle that volume. cards have real overhead per swipe — $0.003 through a card network makes no sense. invoicing assumes a human deciding once a month, not a machine deciding every second.

• 
  Pramod Gupta (@pramodhq) reported 42 minutes ago

  Dayravel is getting good traction at this early stage. Now it’s time to start adding more user-focused features. - Like destinations. - Bookmark destinations. - Newsletter. But first, I need authentication, and for that I need a reliable email service for transactions mail and email services. I’ll be choosing one from: - Cloudflare Email - Resend - Brevo - Amazon SES - Postmark

• 
  vhscom (@vhsdev) reported 43 minutes ago

  @nikuscs @Cloudflare once the text watermarking rolls out search engines can just nuke the slop. bots will be clearly separated into those that produce referral traffic and those that do not. those that do not will be offered an option to pay. problem solved. p.s. someone pls give that guy a razor

• 
  Admire The Web (@AdmireTheWeb) reported 43 minutes ago

  @Cloudflare @MattieTK Customer zero? You mean one?

• 
  Joshua Ojoawo (@Joshyahweh) reported 45 minutes ago

  Cloudflare, a company whose entire business is uptime, had a worldwide outage traced to an internal database update. Not an attack, not a disaster. A change that looked routine enough to not need much scrutiny.

• 
  PodWire (@PodWireHQ) reported 45 minutes ago

  Ask an AI agent for a hosting provider and it reaches for Cloudflare $NET or Vercel, which is why hedge funds are now buying data on how agents pick vendors. Julien Bek (@JulienBek), a partner at Sequoia Capital, says agent traffic is already at par with human traffic, three years into AI. He cites Cloudflare for the estimate that agent traffic runs 1,000x human traffic within five years. The fast answer to that is UI goes to zero. Agents swap your product in a minute, brand loyalty dies, and everything turns into a race to the bottom. He thinks the slow answer is the opposite. Agents carry bias from whatever got scraped in pre-training and from the people who annotated post-training, so they already come with defaults. We spent 20 years building a pixel perfect website that converts humans. The next build is a bits perfect platform that converts agents. Key takeaways already in your email via @PodWireHQ Source: 20VC with @HarryStebbings

• 
  Joey Romaine 🇺🇸 |=★=| (@Tank23x0) reported 49 minutes ago

  Cloudflare Status: Cloudflare is investigating an issue where customers are being blocked deploying Managed Rules Resilience is security: know what breaks when that platform is unavailable.

• 
  Nicu Chiciuc ▣ (@nicu_tsx) reported 49 minutes ago

  Already have apps? Import any repo. Connect/create Convex projects and Cloudflare Workers. The "new app" flow is just a simple version of all the flows that we support. Every PR gets preview deploy Every local worktree gets local deploys you can use dozens of agents in parallel

• 
  Alisina (@Alisina_base) reported 49 minutes ago

  @opencode @Cloudflare Cloudflare optimizations pushing inference errors near zero shows real tuning wins

• 
  KirbySmith (@GenKirbySmith) reported 51 minutes ago

  @opencode @Cloudflare I've had network errors all weekend using ox-alpha-free.

• 
  Simran (@simranzchawla) reported 52 minutes ago

  LinkedIn's AI code reviewer gets 63.9% of its comments merged into the final code. Measured properly too — 5,230 sampled comments across 1,727 PRs, 90.1% of them confidently classifiable against the merged diff. Break that number down by category and it stops being a story about AI. 100% of concurrency bugs. 80% of logic errors. 58.1% of bug fixes. 43.5% of refactors. 40.6% of security fixes. That is not a ranking of how hard each problem is. It's a ranking of how checkable the answer is. A race condition either exists or it doesn't, and you can point at the exact line/method that breaks. A security fix is a risk opinion, and opinions get argued with even when they're correct. Same reviewer, same models, same PRs — acceptance collapses exactly where the ground truth disappears. So the agent doesn't have a capability problem. It has a verifiability problem. Now look at what Cloudflare did with that same problem. Since the start of 2026 their AI reviewer has flagged almost 230,000 deviations from engineering standards and withheld approval on about 16,000 of them. Under 7%. The interesting part isn't the reviewer. It's that they wrote the standards down first — a central repo called the Codex, structured RFCs, every requirement marked SHOULD or MUST, each with an owner and a lifecycle state that moves guidance → observation → enforcement. That lifecycle is the whole trick. A new rule doesn't get to block your merge on day one. It gets logged as signal, it earns its way up, and only then does it become a gate. Cloudflare didn't make the model better at judgment calls. They converted judgment calls into citable rules, so the reviewer stops saying "I think this is risky" and starts saying "this violates a MUST that has a name and an owner." By the way, that's the same progression a feature flag goes through — recommendation, canary, enforced. Nobody flips a new rule straight to blocking for the same reason nobody ships a flag straight to 100%. And the split underneath is doing quiet work too: deterministic rules stay with linters and static analysis, AI only gets the ones that genuinely need context. So here's the question I'd now ask before pointing an agent at anything: What artifact does this agent's output get graded against, and does that artifact already exist? If it exists — merged diffs, a passing test suite, a schema, a reconciliation, a rollback — start there. That's where you get a number instead of a demo. If it doesn't exist, your first project isn't the agent. It's the Codex. Write the rules down, give each one an owner, let them earn their way to enforcement. Cloudflare's real work wasn't the reviewer; it was building the corpus that made the reviewer's findings citable in the first place.

• 
  Hannan (@truehannan) reported 52 minutes ago

  @BraydenWilmoth Outerbase is acquired by cloudflare! WHAT? Bro i justed started using it. Btw can u fix the latest build. It failed to deploy on workers and im lazy to figure out for now

• 
  VΞKING (@veeeeking) reported 55 minutes ago

  How to Get Cited in AI Search: A Practical Source Guide Learn how to get cited in AI search by publishing answerable pages, verifiable evidence, clear entity signals, and crawlable source content. AI citations are not won by adding a hidden tag or repeating a keyword. Models and retrieval systems favor pages that clearly answer a question and provide evidence that can be checked. How to get cited in AI search To get cited in AI search, publish the clearest useful source for a specific question. The page must be accessible, identify the entity without ambiguity, answer the query directly, and support important claims with evidence a reader can inspect. No tag or submission form can guarantee selection. Use this sequence for each priority question: Choose one buyer question. Map it to a dedicated page rather than asking the homepage to cover every use case. Answer it near the top. State the practical conclusion before background or product messaging. Add proof. Include specifications, limitations, methods, dates, primary sources, or genuine customer evidence when available. Make the page retrievable. Confirm that the canonical URL returns the intended content and is not blocked by robots, authentication, or a WAF. Build contextual links. Link from related pages with descriptive anchor text so the topic and page relationship are clear. Inspect actual answers. Compare exposed sources across repeated, equivalent prompts before deciding what to improve next. This process improves source eligibility and usefulness. It does not guarantee that every model, answer, or interface will cite the page. Make the entity unambiguous Use a consistent brand name, product name, category, and website identity. Explain what the product does, who it is for, and where it is available. Conflicting descriptions across the homepage, product pages, and profiles make the entity harder to resolve. Publish answerable pages A single homepage cannot answer every buyer question. Create focused pages for important use cases, integrations, industries, comparisons, pricing, security, and methodology. Each page should resolve a real question without forcing a reader to infer the conclusion from marketing slogans. Add verifiable evidence Specific claims are easier to trust than superlatives. Support important statements with: named customer examples and measurable outcomes; clear product specifications and limitations; original research with a visible method and date; expert authorship and revision dates; primary sources for third-party facts. Do not invent statistics or publish unsupported “best” claims. Keep the site accessible Important information should be present in crawlable page content, use clear headings, load reliably, and have sensible internal links. Descriptive titles, canonical URLs, and relevant structured data help systems interpret the page, but markup cannot compensate for weak content. If the site uses a CDN or WAF, audit crawler access separately. Our Cloudflare AI crawler blocking guide shows how to distinguish AI search access from training-oriented crawling. Learn from actual citation gaps In Dottly AI, open prompts where the brand is absent or uncited. Review the domains the model did cite and identify what useful evidence those pages provide. The goal is not to copy a competitor; it is to understand the question your own site fails to answer. Citation availability depends on the selected model and provider. A response without exposed sources is not proof that retrieval did not occur. Measure patterns across supported answers and repeated runs rather than treating one missing citation as a verdict. Measure citation opportunities Use the report documentation to distinguish available, unsupported, and missing source data. Review the GEO fundamentals, compare source gaps with a GEO competitor analysis, and run a free AI visibility check to inspect the citations currently exposed for your brand. For a broader operating plan, use the practical framework for improving brand visibility in AI search to connect citation gaps with entity, evidence, distribution, and measurement work. Teams focused on Perplexity can use the Perplexity SEO tool stack guide to combine citation inspection with technical SEO, content, authority, and outcome measurement. For a ChatGPT-specific investigation, use the brand citation diagnostic workflow to classify owned, earned, competitor, and incomplete source paths without treating citations as rankings. Frequently asked questions about AI search citations Can I submit a page directly for an AI citation? There is no universal submission route that guarantees a citation. Make the page discoverable, answer a specific question, and verify access through the search or AI crawler routes that matter to your policy. Does schema markup make an AI system cite a page? No. Valid structured data can clarify page meaning, but it cannot replace a useful answer, verifiable evidence, internal discovery, or external authority. How long should I wait before evaluating a citation change? There is no fixed period across providers. Record the publication date, keep the prompt and model conditions stable, and look for a repeated pattern rather than treating one answer as proof. Conclusion The practical answer to how to get cited in AI search is to make one page the best verifiable response to one important question. Start with entity clarity, direct answers, evidence, crawlability, and contextual links, then use saved responses to decide the next change.

• 
  Matt Ragudo (@mattragudo) reported 58 minutes ago

  @Bsoutherland23 So right now there really isn’t a CEO agent. Like one that makes decisions on everything. Most agents rely on scope. For example, I have all of my website content work, and automated trading research and content handled by agents. A group of agents. My websites (I have 6 different that I’m focusing on now): Research 3x a week, find stuff interesting based on what I’ve told it plus what’s trending and what’s showing up in socials/news. Reasoning agent then looks at what’s worth publishing based on what’s out there and what my ideal client would want to read that needs to be curated further. Sends that list to my writers. Writer agents draft based on the voice and guidelines that I have given it. Research check agents review the articles based on what we are able to say, verify claims and statements and look up references and links them. Returns this to the writer if there are any issues. Researcher waits for confirmation from writer. Researcher, once done, sends it to a proof reader Proofreader, who further checks one last time for consistency, now also checks for publication rules and makes sure it’s compliant with the verticals. Lastly, a poster with posting credentials will push it to cloudflare to post. All of this is then reviewed monthly for any hold ups in the process by a loop operator whose job is to make sure I (Matt), need not be bothered and that the content is being posted and analytics are doing well. Analytics, which are reviewed by another “Agent system”.

• 
  Yoonsun Lee (@everdenepublic) reported 1 hour ago

  Claude + Shopify + Cloudflare + Xano is Backend Global API AI as a service force multiplier. Claude + Shopify for Theme is a waste of tokens. We don't need to solve the theme setup. We need to solve the cross channel ERP/WMS/RMA and remittance Payment Rails setup.

• 
  kevops (@kevvOH_) reported 1 hour ago

  i am unable to login successfully into cloudflare