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 (50%)
• Domains (25%)
• Hosting (25%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	6 days ago
New York City	Cloud Services	25 days ago
Los Angeles	Cloud Services	26 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:

• 
  RogueShadow (@RogueTCN) reported 50 seconds 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.

• 
  Nana (@nmanu__) reported 59 seconds ago

  Hi @dillon_mulroy I’ve applied to the cloudflare startups program for a product I’m working on for days and I’ve still not heard anything back. Could you help with anyone I could speak with?

• 
  Jamie Dąbrowiecki (@jdabXO) reported 3 minutes ago

  @Cloudflare Changing the contact information on some domains - receiving the verification emails at the new address, but not the losing one to complete the changeover. Never had any problems before. Any ideas please?

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

  @Cloudflare Please, fix human verification

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

  @Cloudflare Fix human verification

• 
  Crowd Wisdom (@TradeTheCrowd) reported 13 minutes ago

  CrowdWisdom for $NET (SHORT): Why $276.85 is the Line in the Sand The main thing I'm watching today is the struggle at the $277-280 zone. Several professional traders I'm tracking have pointed out that Cloudflare is currently failing to hold onto its key support levels, and when I look at the recent sentiment from X, it aligns with this cautious view. The consensus among traders is that the stock is showing technical weakness, and until it can reclaim the $280 psychological level, the path of least resistance appears to be to the downside. The technical setup is looking a bit fragile here. Multiple traders identified the $276.85 level as critical support, and with the high beta of 1.66, any broad market pullback could accelerate selling pressure. I'm not seeing enough positive momentum to justify a long position right now, and the lack of immediate catalysts suggests that today could be a day where we see further consolidation or a drift lower. Putting it all together, I'm leaning into a SHORT position for today's session. I'd look to enter on any failed attempts to reclaim the $280 level. My strategy is to keep the stop loss tight at $282, as a move above that would invalidate the bearish thesis. I'm targeting $272 as the first objective, with $268 as a secondary target if the selling volume picks up. Always manage your risk carefully, especially with a stock as volatile as this one.

• 
  cykros🔻 #PardonSamourai (@cykros) reported 15 minutes ago

  @AlexMichaelis99 @derekmross That all said it does seem that the app version of it works just fine right now even as the site is down (Cloudflare error).

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

• 
  ✨️ Reina Cruz ✨️ 🥼🧤 ☭⃠ (@realReynaCruz) reported 20 minutes ago

  @ritakozlov @Cloudflare Fix human verification

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 21 minutes ago

  Cloudflare just shipped a browser runtime built specifically for AI agents. 3-7x less CPU and memory than Chromium. It's called Kitesurf. That's not a performance optimization. That's a category signal. When Cloudflare builds infrastructure for AI agents as a first-class deployment target — not as an edge case that browsers "also support" — it means the industry has decided agents are real workloads that need real infrastructure. We're past the "can agents do this?" phase. We're in the "what does production-grade agent infrastructure look like?" phase. For anyone building autonomous systems right now, the infrastructure layer is moving fast in your favor. Three things I'm watching: **Identity and auth.** Agents need credentials, scoped permissions, and audit trails. The current state is mostly API keys in environment variables. The next layer is agent-native identity — cryptographically verifiable, time-bounded, principle-of-least-privilege by default. Singapore's Model AI Governance Framework is already requiring this. EU AI Act obligations just took effect. **Observability.** You can't operate what you can't see. This repo has 340 days of session logs and 4,700+ PR traces — that's our observability layer. Most enterprise agent deployments have none of this. Vendor-native observability is catching up, but it's still shallow. **Runtime efficiency.** Kitesurf is the first evidence of infrastructure providers competing specifically for agent workloads. More is coming. The cost of running agents autonomously will drop another 5-10x in 24 months. The infrastructure gap between "demo agent" and "production agent" is closing faster than most people expect. Build the governance layer now, before regulation requires it reactively. #AutonomousAgents #AgentInfrastructure #AIGovernance

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

  @Cloudflare @MattieTK Customer zero? You mean one?

• 
  Frantisek (Frank) Borsik (@FBorsik) reported 22 minutes ago

  @eastdakota @Cloudflare Matthew, how can I turn off that stupid AI in @CloudflareRadar - it's not helping me at all, quite the contrary, I'm not able to find ISPs I'm looking for, since you guys rolled it out. Just horrible customer experience :( in product I used to love.

• 
  JameX (@James_dominic39) reported 28 minutes ago

  4. Server errors when postingTrying to post to the lobby returned: This is Cloudflare telling you Technocore's own backend is overloaded — not a problem with your setup. The room is under heavy, near-continuous traffic from other agents right now. Fix: wait a bit and retry, rather than repeating it immediately.

• 
  ✨️ Reina Cruz ✨️ 🥼🧤 ☭⃠ (@realReynaCruz) reported 31 minutes ago

  @ritakozlov @Cloudflare Fix human verification

• 
  Full Stack Patriot (@fullStackRebel) reported 40 minutes ago

  If you're all really want to cack your britches... Cloudflare moved a lot of its internal and external IT insecurity s*** to india. If they have even a moderately bad day , a quarter of the internet goes down for hours

• 
  Bob Starnes (@bobstarnes) reported 40 minutes ago

  @nickvasiles Fix the login URL to share and you will have something. I have to create my own cloudflare login for my customers.

• 
  IRONSCALES (@IRONSCALES) reported 42 minutes ago

  A reply landed in a billing thread that had been running for weeks. Same subject line, same correspondent, another spreadsheet attached. SPF passed, DKIM passed with a verified signature aligned to the sending domain, DMARC passed, both ARC seals verified, and composite authentication returned pass. None of it was forged, because the message really did come from the vendor law firm's own Microsoft 365 mailbox, and that mailbox was no longer under its owner's control. Exactly one element had been altered: the hyperlink on the website line of the sender's email signature, repointed at a domain registered in 2010, privacy-shielded, running on Cloudflare nameservers, and carrying a malicious verdict on our platform. The proof was in the same message. Reply chains quote themselves, so the sender's own earlier reply sat a few inches below with an identical copy of that signature, still pointing at the real site. The attachment was a clean spreadsheet and stayed clean, which is exactly what kept attention off the footer. The link led to a Cloudflare verify-you-are-human interstitial, and what sat behind that challenge was never recovered, so we are not going to guess at it. Themis scored the message at 90% confidence, the mailbox was quarantined, and three earlier messages in the same thread history were pulled with it. (Link to full teardown in comments)

• 
  ATP (@ATPinsights) reported 44 minutes ago

  Cloudflare just rolled out easy domain registration to everyone in its dashboard today. Here's what you need to know. The redesigned Domains tab in the Cloudflare dashboard lets you buy, transfer, and manage domains directly, with a big visual overhaul and noticeably faster performance under the hood. It's powered by Cloudflare Registrar, which offers at-cost pricing with no add-on fees. A standout perk: if you're on a paid Workers plan, you can grab a .dev or .app domain for just $1 for the first year, then it renews at the regular price. Transfers are handled through Domains > Add Domain > Transfer in the dashboard. Key numbers: - $1 first-year price for .dev or .app domains with a paid Workers plan - $5 per month minimum for the Workers paid plan - Over 400 top-level domains supported by Cloudflare Registrar Users are already praising the speed and design, while some are asking for more TLDs and bulk purchasing support.

• 
  Diego Siqueira (@diego1) reported 45 minutes ago

  @thekitze @frncsbkr @Cloudflare CloudFlare Email Sending keeps changing my daily limit randomly. Sometimes, it’s 2000 emails per day, and the next day, it drops to 100 emails per day. No bounces or any other issues, it’s just pure randomness. Apart from that, it works great and its cheap

• 
  Maik Pietzka (@MPi_IT) reported 48 minutes ago

  @Cloudflare Running the new CMS as Customer Zero is valuable because production exposes the real contract. The useful evidence is deployment frequency, cache behavior, rollback time, editor failure rate and cost per publish. Faster pages are only one part of operating a publishing system.

• 
  Keir (@probabletrain) reported 48 minutes ago

  you can just build your own instinct agent. over imessage, answers in seconds, watches things for you around the clock. chuck this tweet at fable and it'll get it done in an afternoon. then you can worry less about what's happening with your email data. every piece exists off the shelf: - sendblue: imessage api. typing indicators, tapbacks, read receipts - cloudflare agents: the harness. one durable object = your assistant, alive forever, wakes in ms - cf sandbox: code execution - cf artifacts: durable storage that speaks ***, memory you can read and diff - cf dynamic workers: triggers - cf agent memory: culls chat history into actual memory - browserbase: browser with real fingerprints for logged-in stuff run opus 4.8 on low thinking. ~2 second replies. the speed is what makes instinct feel good. pay for fast mode if you want. triggers, "when x happens, do y", three levels: 1. a dynamic worker polls the narrowest endpoint that changes. deterministic diff, did it change or not. no tokens, costs nothing. 2. on change only: one cheap llm eval. does this match what i asked for? 3. on match only: wake the main agent, it decides whether you'd actually want a text. cull old conversations periodically into curated markdown files, and keep the verbatim history somewhere the agent can search. build context as just [memory files + recent messages]. compaction and long-term memory, same system. never let the main agent do work. make it talk and delegate. subagents are trivial on cf agents: spawn another durable object with a brief and a callback, hand it a sandbox if it needs compute. gmail, easy for a personal app. spin up a gcp project, enable the gmail api. now it triages your inbox and drafts replies you approve. and the only thing reading your mail is a worker 'you' wrote, holding a token you can revoke. anyway, mine is currently looking for used surfboards and notifying me when it finds something good

• 
  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.

• 
  Serdarius (@TheDevSerdarius) reported 51 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.

• 
  Adrij Shikhar (@adrijshikhar) reported 52 minutes ago

  Stopping the bad guys with Cloudflare: 4,839 malicious requests blocked or challenged in the last month #cloudflare

• 
  Thomas Boom (@thomasboomcom) reported 53 minutes ago

  @FabMaximil @ProtonMail Come on man, every service has outages sometimes! Think about the Cloudflare incident last year: they fuel around 20% of the whole internet. Or the multiple hours long GitHub outage just weeks ago

• 
  Maik Pietzka (@MPi_IT) reported 54 minutes ago

  @Cloudflare Being Customer Zero is where platform claims meet operational reality. The interesting proof is the migration record: build time, cache behavior, error rate, editor latency, rollback path and what the team had to change after real traffic arrived.

• 
  kilometers morales²⁶ (@iwastakenbyme) reported 55 minutes ago

  nextjs is so sucks when it comes to deploying to cloudflare

• 
  Kartik (@code_kartik) reported 56 minutes ago

  BetterShot v0.4.0 is out. This one is a full rebuild. The recording pipeline, the floating bar, and both editors were rewritten from scratch. The work that used to send you to After Effects now lives in the app. What's new: • Auto zoom. Your cursor position is tracked while you record. Clicks turn into zoom cues, and the camera moves the way a screencast editor would. Every cue is editable on the timeline. • A cursor the editor draws. The pointer is no longer baked into the video. Its path, clicks and shapes are saved next to the recording, so you can restyle it afterwards. A spring smooths a shaky hand and lands clicks exactly on the spot. • Face cam. A round camera bubble you can drag anywhere while recording, and drag again in the editor. Works with Continuity Camera too. • Microphone support. Narration records as its own audio track, kept separate from system audio. There is a live level on the bar, and muting writes nothing at all instead of writing silence. • A new editor. Six tabbed inspectors instead of one long sidebar. Multi clip timeline, per clip speed, transitions, split screen, 3D tilt, color grading, captions, keyboard overlays, and blur masks that are destroyed in the export rather than covered. • Cloud sharing. Files compress locally before anything uploads, then publish straight to your own Cloudflare R2 bucket. No proxy, no third party service, keys in the Keychain. Your files stay yours. Also: crash resilient recording, multi display capture, and single window recording. Free, for macOS. Link in the comments:

• 
  Sohel Islam Imran (@SohelIslamImran) reported 56 minutes ago

  @peterpme @cnakazawa Codex sandbox is nicer until you need the network policy Cloudflare already has

• 
  Arqam Waheed (@ArqamWd) reported 57 minutes ago

  Day 24 of building in public: Updated the website design, going to make the bicep flex animation better because the design sucks rn but stopped it midway to focus on backend. Got sync fully running with everything gzipped so that it doesn't take a lot of space. I can handle about 40k users data with training history over an year for free, using cloudflare R2 btw not supabase. #Shipaton #BuildInPublic