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:

• 
  Sam (@Swgtct) reported 5 minutes ago

  @ODEONHelp some bizzare reason I have been cloudflare blocked on app and website any ideas or can I just never go to odeon again ?

• 
  Publisher in a Box (@publisherinabox) reported 9 minutes ago

  Click-through on the number one organic result drops about 58% where an AI Overview appears. @ahrefs measured it across 300,000 keywords. That number sits inside a data-heavy breakdown of where AI search stands right now. Five points matter most for operators: 1. Citations alone are not the whole picture. Wil Reynolds tracked a 1,900% month-over-month jump in ChatGPT citations to a single page on his site. Business impact: close to zero. Counting how many times an AI engine mentions you is half a metric. It does not tell you whether you were recommended or just named, whether the description was accurate, or whether it happened on the engine your buyers actually use. 2. Google's own reporting confirms the gap. The new AI performance report in Search Console shows impressions only. No clicks, no queries, no CTR. Marketers asked for attribution data and got a vanity counter. You cannot make a business decision on impressions alone. 3. The click loss is quantified, not anecdotal. The 58% is measured click-through on position one across 300,000 keywords. Publishers who depend entirely on organic search clicks are watching a measurable decline, not an imagined one. 4. Most agentic infrastructure is not being read. Ahrefs studied 137,000 sites and found 97% of llms.txt files never get read by a crawler. Meanwhile Cloudflare reported in June 2026 that bot and agent traffic crossed 50% of all internet traffic for the first time. Technical retrievability is the whole game here. Schema, llms.txt, crawler access. It is the gap that closes fastest and the one almost nobody has verified actually works. 5. GEO demand is climbing from a standing start. "Generative engine optimization" now pulls 7,900 US searches a month, up 997%. The entire AI attribution keyword cluster is up 430% year over year. Operators are searching for this because they feel the traffic shift and want a playbook. Here is the part most people skip. GEO gets you cited inside the AI answer, SEO gets you ranked in a list of links. Four engines answer differently, ChatGPT, Claude, Perplexity and Gemini, and most publishers appear on one and are invisible on the other three. Sentiment counts as much as volume, because being named is not the same as being recommended. We built our GEO scoring before most teams knew the term, and we ran it on our own properties before we ran it for anyone else. The AI referral traffic followed. That is the only reason we are confident enough to publish the methodology. For publishers building a real business, GEO is another revenue line sitting alongside Facebook, the website with Google Discover, and the newsletter. Facebook is the base the rest of it is built on. It pays publishers directly and sends readers to the site, and that is what funds every other channel. A diversified publishing business treats each discovery surface as a channel worth measuring on its own. The operators who figure out AI referral traffic now are claiming ground the rest of the field will have to buy back later. The ground in your niche is still open. How we measure it and how you claim it, in the first reply 👇

• 
  TechRemarker (@TechRemarker) reported 12 minutes ago

  @CloudflareHelp Does any one know how to contact @Cloudflare support? As detailed in this thread. CF had a bug where they charged me twice for the domain registration. Site contact options just show help docs. No response from CF Help here. Anyone know how I can reach them?

• 
  Chinmay Purav (@chinmay_purav) reported 16 minutes ago

  Hey @Cloudflare , Please bring in support for .IN TLD domains!

• 
  Rishi Raj Jain (@rishi_raj_jain_) reported 19 minutes ago

  @SantoshYadavDev @astrodotbuild @Cloudflare CF Pages are basically replaced with Worker. Lmk if you need any help!

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 21 minutes ago

  On June 3 2026 Cloudflare CEO Matthew Prince announced that bot and agentic AI traffic had officially surpassed human generated web traffic for the first time in the internet's history. The split landed at 57.5% bot traffic versus 42.5% human traffic. Prince had originally predicted this crossover would happen by end of 2027. It arrived eighteen months early. His response was direct: "Welp, that happened faster than I predicted." The driver is not the old wave of scraper bots and search crawlers. The main culprit is agentic AI. Autonomous programs browsing the web on behalf of AI assistants. A single agent can visit thousands of pages to complete a task a person would finish in a handful of clicks. Agentic AI traffic grew 8,000% across 2025 alone. Now let’***** on the Dead Internet Theory context. The theory, which originated in fringe internet forums around 2021, proposed that most internet activity was already artificial. Fake engagement, bot generated content, astroturfed discussions, AI personas. The humans were the minority and did not know it. The conspiratorial version of that theory claimed it was coordinated and intentional. That part remains unverified and unlikely. But the core observation that the majority of internet traffic is non-human is now confirmed data from the largest internet infrastructure company on the planet. The internet was architected around human usability and attention. The entire world of digital advertising, publisher monetisation, and e-commerce sits on the assumption that users are human. That assumption is now statistically false. Every engagement metric, every analytics dashboard, every ad impression count is increasingly measuring machine activity and reporting it as human behaviour. The business models built on human attention are being quietly hollowed out by traffic that generates requests but never buys anything, never reads anything, and never remembers what it visited. The theory was wrong about the why. It was right about the what.

• 
  spongebobham2billion (@spongebobhamtwo) reported 21 minutes ago

  Put that neocities **** down and buy a cloudflare domain like a real man

• 
  brendan (@brendonovich) reported 22 minutes ago

  @thdxr i've never used cloudflare until alchemy existed, i'm scared of wrangler configs

• 
  Prajwal Tomar (@PrajwalTomar_) reported 23 minutes ago

  Vibe coders are getting sued. People are shipping apps with real users and skipping the boring stuff that kills them. A 20+ year dev shared the pre-launch checklist every AI builder needs. I added what I learned after shipping 60+ apps at the agency. Don't skip this: 1. Protect yourself, not just your app. The moment you collect user data you're in legal territory (GDPR, CCPA). Have a privacy policy. Know where user data lives. 2. Row Level Security. Without RLS, anyone can open DevTools and read your entire database. Supabase → Auth → Policies. Zero policies means your app is naked. 5 min to fix. 3. Test the failure path, not just the happy path. Wrong password 5x. Reset for an email that doesn't exist. Verification link clicked twice. Signup with an existing email. Catches 80% of auth bugs. 4. Security baseline in 2 min. Prompt your AI: "Review my app as a security specialist and make sure I have strong security headers and a solid baseline security posture." 5. OWASP. Prompt: "Review my app against OWASP standards and highlight vulnerabilities." This is where SQL injection, XSS and auth bugs actually get caught. 6. Client-side validation is UX, not security. Attackers disable JS and hit your API directly. Validate again on the server. Every time. 7. AI code leaks data in 3 spots: .env values in the frontend, API responses returning too much, secrets in logs. Prompt: "Check my app for credential or sensitive data leaks in frontend or API routes." 8. API keys in the frontend means game over. If it's in the browser, assume it's already taken. Move it server-side or proxy it. 9. Rate limits before someone burns your API bill. Cap every endpoint hitting a paid API. I've watched a Supabase bill jump from $20 to $200 in a day. 10. CAPTCHA on public forms (Cloudflare Turnstile is free) plus CORS locked to your domain. 10 min, kills bot floods. 11. Error messages that don't leak. "User not found", not "SELECT * FROM users failed". Log full errors server-side, show users generic messages. Build fast. Just don't ship naked. (full breakdown in my article below)

• 
  Lucas Rodriguez (@LucasSaasbr) reported 23 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  the Sleeping Wizard (@magicnaptime) reported 27 minutes ago

  Damn guys maybe try dialing it up to 2:2:2:2 for Pete's sake @CloudflareDev @Cloudflare

• 
  Austin S. Lin (@siraustin) reported 30 minutes ago

  @prd_008 dear lord no… Sites is a fine name for what it is (it’s cloudflare pages and workers abstracted). one big issue is that you get different levels of github access from within chatgpt app depending on whether you have chat (no access to private repos), work (access to existing repos), or remote selected (full github access to create and manipulate repos).

• 
  Tejas (@stejas809) reported 32 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  fofotara (@fofotara) reported 32 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Rohan (@iamTRA) reported 34 minutes ago

  I killed my Wix/Webflow subscriptions this week. ~$40/mo from old acquisitions. Bloated af. Replaced with $0/mo Cloudflare pages - built end-to-end by agent. Faster pages rank higher on Google Maps. Cloudflare docs are complex, never bothered to read. No need to in 2026.