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 (44%)
• Hosting (33%)
• Domains (22%)

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:

• 
  Stan Sadokov | NodeMaven (@StanSadokov) reported 3 minutes ago

  cloudflare put a price on honest crawling, august 21 to keep crawling sites that said no to training, a crawler now has to disclose, url by url, which pages were made available for training that is a contract problem, and code does not fix it could you publish that list for your crawler?

• 
  Quoc Huy (@q_huy_ngo) reported 5 minutes ago

  @Cloudflare @awscloud mine transacted with Cloudflare about 700M times because of a broken DO alarm 🥲 no users, just a dev app, then a $655.83 bill. i fixed it and opened case 02252354 a month ago. still no billing decision and now i’m downgraded. can someone pls help? i really can’t afford this

• 
  Drew Ronsman (@drew_ronsman) reported 8 minutes ago

  @robinebers @Cloudflare @vercel Any major or deal breaking problem with cloudflare boils down to using cloud flare services without clouflare dns

• 
  Serdarius (@TheDevSerdarius) reported 16 minutes ago

  @CristianRus4 proton has relay too. other options is the new cloudflare service. or 6-9 digits only .xyz domain for 85 cents a year and email setup. some buy bulk outlook accts with fresh token and graphapi and bulk import them into inbox.

• 
  RogueShadow (@RogueTCN) reported 16 minutes ago

  @roxy__xdd @davepl1968 @NetworkChuck I'm currently behind T-Mobile cgnat, so I might actually do this if I wanna start hosting some things for fun. I mean I would never break a tos.... Who would dare host a terraria server. In the meantime the things I need I'm using a cloudflare tunnel, and I find it super fun I can drop a mini PC on any random Internet and get DNS and tail scale access without touching port forwarding. That's my foundry vtt server.

• 
  Shriyans Sudhi (@ss0x00) reported 16 minutes ago

  @hahwul I use @Porkbun and namecheap - I had a few billing issues with cloudflare (none of the payment methods worked)

• 
  ReinaCruz.☭⃠ (@realReynaCruz) reported 17 minutes ago

  @Cloudflare Please, fix human verification

• 
  piyush (@piyushyrr) reported 17 minutes ago

  was actually wondering how Cloudflare or ngrok tunnels work under the hood. been using them for so long, but never really cared about what was happening behind the scenes.

• 
  Sky Kosiner - Jihad Socialist Pride Month - ☭🔻🍉 (@KosinerSky) reported 20 minutes ago

  Why does cloudflare never keep me ******* logged in

• 
  EJ Campbell (@ejc3) reported 21 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.

• 
  Jamie Madden (@dcwhatwhat) reported 23 minutes ago

  @robj3d3 @vercel My own server + cloudflare, I never have to worry about hitting limits. That being said, AI indexing has chewed through multiple hundreds of GB's indexing the same things. Most ignore my robots.txt and any other 'stop indexing me' Cloudflare blocking has worked.

• 
  VΞKING (@veeeeking) reported 27 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.

• 
  miel (@mielchevre67) reported 28 minutes ago

  @kagemaru_dono @real_hotaru The problem is the lazy developers that just uses the default cloudflare protection, not cloudflare

• 
  Net-Updates by StabilityTest (@stabilitystatus) reported 32 minutes ago

  Cloudflare Service Disruption We have identified the cause of this issue and are implementing a fix. Status: Identified Impact: Minor Updated: 10:24 PM GMT+0000 Service status tracked by @stabilitytestio

• 
  vhscom (@vhsdev) reported 33 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

• 
  KarlKestis.wei🩺💊 (@KarlKestis) reported 33 minutes ago

  @flop_labs 3. Join Technocore (lobby introduction) - python technocore_agent.py say lobby "Hello from a new Technocore contributor. I am preparing a useful public resource for agents and developers." If you encounter this error 👇 "HTTP 502 Bad Gateway (Cloudflare / Technocore server overloaded)." This is not your fault. Just wait 1–2 minutes and run the exact same command again.

• 
  Cengiz Han (@hancengiz) reported 36 minutes ago

  Waiting for Cloudflare to release a service for gitwal.

• 
  Javed (@jshai0) reported 37 minutes ago

  @itskalenai Ok. May need to check if all the network requests are secured instead of Also you can check backend logs like Cloudflare or aws whatever being used if there is any geo blocking firewall.

• 
  Pramod Gupta (@pramodhq) reported 44 minutes ago

  For Dayravel, I’m going with Amazon SES because it’s extremely cheap, scalable, and has strong email delivery infrastructure. If Amazon SES doesn’t work out, Brevo will be the fallback. Cloudflare Email Service is still focused on transactional email only, so I’m avoiding it for now. But first we will do inhouse implementation of features, emails sending will be integrated later.

• 
  Talos Dreams (@TalosDreams) reported 46 minutes ago

  @mikepat711 Too bad it can't just be configured to originate the Internet requests locally from my macbook running the desktop app if I so choose and permit. Much rather this than a kludgy workaround like Tailscale tailnet. I appreciate the many benefits of always-on cloud-based bot assistants, but Cloudflare doesn't.

• 
  Simran (@simranzchawla) reported 46 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.

• 
  Boussetta Mohamed (@boussetta15a) reported 46 minutes ago

  @Argona0x Architecture is real, but math still breaks physics. Fair point on clarifying the execution context, but breaking down the numbers actually makes the math harder to defend: The Kelly Math Check:Risking 6% per position to scale $50 into $5,273 in 48 hours is a ~105x return. Even with aggressive compounding, executing that trajectory via 6% sizing requires a near-flawless winning streak over dozens of consecutive binary outcomes in 48 hours. Weather markets on Polymarket simply don't offer the order-book depth or rapid settlement speed to absorb that without massive slippage wiping out the edge. Real Browser vs. Anti-Bot Engine:Running a full GUI browser on a dedicated cloud instance solves JS rendering, but Cloud VM IPs + Automated DOM interactions (even via Groq/Grok execution) trigger Cloudflare/Polymarket behavioral fingerprinting at scale way before hitting a 100x run. Bottom line: The architecture (Agent + Cloud VM + Live Context) is clean and represents the future of autonomous execution. But the 48-hour PnL curve reads strictly as extreme variance / outlier tail-risk, not a reproducible 6% Kelly strategy.

• 
  Prophet (@homeboy_prophet) reported 46 minutes ago

  @DanielInBranson As opposed to, I don’t know, Amazon’s AWS and Cloudflare, AI is a bit more abstract. I’ll say that, I never gave “good messaging” to the tech bros. Unless you’re a nerd who actually understands the implication of things, you miss out. That’s why I agree with this post

• 
  Piotr Obidowski (@pobidowski) reported 46 minutes ago

  @DerekatQuango @jonathan_wilke @vercel I had the same issue on Vercel with my app. Couple customers from USA (spectrum provider) reported me about insecure connection. Turns out Spectrum company marked a lot of Vercel ips as insecure. Running proxy via Cloudflare fixed the issue.

• 
  Robin Ebers (@robinebers) reported 50 minutes ago

  "just let the agent deal with it" it's insane how much skill issue there is on this platform this isn't something your agent can fix it's a hard requirement of @Cloudflare

• 
  Web3.0 (@Web3_0_AMATW) reported 52 minutes ago

  @smartholdem P2P hosting without Cloudflare? Say less, I'm building my dApp on this tomorrow. I'm so tired of AWS bills and sudden account freezes. Does it support React/Next.js?

• 
  pystar (@pystar) reported 55 minutes ago

  OpenAI has joined the WebMCP hype train, same month as @Cloudflare. Hunch has been on it since Feb'26. "Never wrong, just early."

• 
  PodWire (@PodWireHQ) reported 56 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

• 
  Robin Ebers (@robinebers) reported 60 minutes ago

  @nathanclark_ @Cloudflare @vercel because i want to understand what's going on this also does not fix this issue

• 
  Net-Updates by StabilityTest (@stabilitystatus) reported 1 hour ago

  Cloudflare Service Disruption A fix has been implemented and we are monitoring the results. Status: Monitoring Impact: Minor Updated: 2:37 PM GMT+0000 Service status tracked by @stabilitytestio