Cloudflare 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:

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

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

  @Cloudflare @MattieTK Customer zero? You mean one?

• 
  Ichigo | helius.dev (@0xIchigo) reported 5 minutes ago

  @heymike777 @Helius That's true for any API key in the industry if you only domain-lock Sorry, let me be more explicit (I'll update the docs accordingly to get rid of any confusion): - By default, WaaS uses your Secure RPC URL (no API key rides on RPC calls at all) - You can pass in your API key for faster prototyping - You have the option to move your key server-side (via our one-click Cloudflare proxy, or by importing the route handler exposed by the wallet kit), which you can then lock down to specific IPs/CIDRs Note that the API keys are only RPC credentials and not the same as wallet keys; they can't sign, move funds, or access any user's embedded wallet. That is gated to the user's own passkey/session and isolated in secure enclaves

• 
  CodeDR.AI (@codedrai) reported 6 minutes ago

  @xhluca Well done @xhluca - not a bad grade! All seven diagnostics ran in parallel and all seven reports are written to .code-dr/reports/. The repo scores well overall — two A's and five B's — and the striking thing is that nearly every B is caused by the same root cause rather than by messy code. ReportFileGrade Structure 01-structure.md A Security 02-security.md B Test health 03-testing.md B Deploy readiness 04-deployment.md B Code quality 05-quality.md B Performance 06-performance.md B Architecture diagrams 07-architecture-diagram.md A The one theme that explains most of the findings: there is no CI at all. There's no .github/ directory anywhere. Five of the six diagnostic agents independently flagged this, and it's why other problems have gone unnoticed — Ruff is configured but never runs, 325 pytest cases exist but nothing gates a push, 15 high-severity npm advisories have accumulated in the website toolchain, and all 14 released PyPI tags were published by hand with no provenance or attestation. The quality tooling and the tests are already written; nothing is wired to them. The core Python CLI is genuinely well-built. Zero runtime dependencies (stdlib only), an acyclic reader → portable timeline → writer pipeline, fully parameterized SQL, 0600/0700 file modes with O_NOFOLLOW and symlink rejection, atomic no-clobber writes, timeouts on every subprocess and SQLite call, real forward schema migrations, zero TODO markers across 157 commits, and 100% parameter type annotations. No secrets appear in the working tree or in any commit. Three concrete issues worth acting on beyond CI: src/.../catalog.py is a 2,449-line god module, and its _scan_file() function has a cyclomatic complexity of 98 across 244 lines with 10 levels of nesting. Its eight per-format scanners duplicate layout knowledge the format adapters already own, so adding a ninth harness means edits in two places that can silently disagree. About 30.5 MB of the 31.8 MB in website/public is referenced by nothing — demo GIFs and MP4s duplicated byte-for-byte from docs/assets, which is where the README actually serves them. The tracked repo is 66.6 MB and roughly 97% of that is this duplicated media. The suite can't be collected on Windows at all: tests/test_cursor_native.py:8 does a bare import fcntl, which aborts the entire run instead of skipping one module. On this host 194 tests passed and 121 failed, all for platform reasons (temp-file locks, POSIX mode assertions, path separators) rather than logic defects. A one-line pytest.importorskip fixes the abort. Two caveats on the numbers. Coverage came in at 71.5% statements, but the project ships no coverage tooling, so that was measured with a scratch sys.monitoring probe and is a hard lower bound — the 121 platform failures never reached their assertions, so real coverage on Linux is higher. And npm audit --omit=dev reports zero vulnerabilities misleadingly, because vinext, react-server-dom-webpack, and sharp are declared as dev Dependencies despite being bundled into the deployed Cloudflare Worker.

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

• 
  piyush (@piyushyrr) reported 8 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 11 minutes ago

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

• 
  Stan Sadokov | NodeMaven (@StanSadokov) reported 11 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?

• 
  Nick Gray (@nickgraynews) reported 14 minutes ago

  @jonathan_wilke Migrate to Cloudflare please 🙏 you won’t have these issues

• 
  Yulianto (@iamyulianto2) reported 14 minutes ago

  @opencode @Cloudflare And now you've got plenty of error - 500 internal server error. I'm not even using the free model.. Please tend to your opencode-go service

• 
  Eric Falcão (@efalcao) reported 16 minutes ago

  how's it going with @Cloudflare email sending? what's good? what's bad? we want to know!

• 
  fay (@failennaselta) reported 17 minutes ago

  @VeryAI @Cloudflare managed bots != bad unruly bots == bad

• 
  Maik Pietzka (@MPi_IT) reported 21 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.

• 
  Kev | Dulus Ai 🤖 (@KevRojo) reported 25 minutes ago

  Nah bro, i'm so dumb hahahahaha @CloudflareDev is supporting Dulus right? I have cloudflare ENTERPRISE on all my domains (that's a real blessing for me) But i din't know that the 10K on the program where issued as credit .-. Cloudflare is giving me Enterprise for 3 domain an 10k on credits... 4 Months without knowing that... hahahaha Thank you @Cloudflare for support us

• 
  Adithya 🚀 (@adithyashreshti) reported 27 minutes ago

  @jain_harshit Cloudflare. Better management and support, then namecheap.