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:

• 
  Kev | Dulus Ai 🤖 (@KevRojo) reported 5 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

• 
  🧡🖤 KTP | currently Fafner-posting (@kyluxtrashpit) reported 6 minutes ago

  I s2g I am one more ******* cloudflare verification away from burning down the entire internet for everyone forever

• 
  CodeDR.AI (@codedrai) reported 9 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.

• 
  PolkaPop | VArtist 💕VLyrica (@PolkaPopVT) reported 10 minutes ago

  I've been fighting with my internet on pc for 30 minutes just to cloudflare be my whole source of problem. I hate it

• 
  Mike Cao (@caozilla) reported 13 minutes ago

  @efalcao @Cloudflare Tried to increase my limit. Got no response. Eventually hit my limit and had to move to another provider. Bad experience.

• 
  Kanak (@KanakKholwal) reported 15 minutes ago

  @samrithshankar what exactly are the issues? I have somewhat work with cloudflare dev stack

• 
  Pikanou ⚡🏴‍☠️ (@pikanou_) reported 16 minutes ago

  Agent Experience is quite a terrible label since AI doesn't have, urgh... feelings. So repurposing human-centric 'UX' terminology for autonomous agents is weird and just plain buzzword. Sounds like AX is the new UX! Rebuild everything! But behind the scenes, the engineering is a big reality. For now most websites are hostile to AI agents, quite difficult for them to visit the pages with cookies banners, cloudflare bot challenges, client-side JS hydration crash headless scrapers before they even fetch content. What we see from Vercel with their isagentic is about improving your website for Machine Accessibility. Agents don't care about the design of your landing page. They just want to extract its content. Want to know what to do? -> building deterministic APIs, agent-first auth, and machine-readable data pipelines. I would call it instead Agent Interoperability, but yeah I guess you can't brand it as "AI"

• 
  Hareesh Vemasani (@HVemasani) reported 16 minutes ago

  I went through the startup credit programs still worth applying for in 2026. Bookmark this 🧵 Cloud and infrastructure: • Google Cloud — up to $350K • Cloudflare — up to $350K • AWS Activate — up to $200K • Microsoft for Startups — up to $150K • DigitalOcean — up to $100K for eligible AI/ML startups Build and ship: • Retool — free for 1 year, up to $60K • Vercel — up to $30K • GitHub for Startups — $10K • Notion — Business + AI free for up to 6 months • Linear — up to 6 months free Product, analytics and growth: • ProductBridge — support + feedback platform free for 6 months, followed by discounted pricing for 24 months • PostHog — $50K credits + $12K in partner perks • HubSpot — up to 90% off year one • Mixpanel — full platform free for 1 year Eligibility often depends on funding, company age, team size or a partner referral.

• 
  Scott (@scottjla) reported 17 minutes ago

  @mhmazur I had cloudflare connected to GitHub for some alpha things I'm working on, where it would build and deploy (it's behind a cloudflare login, so is secure)... Problem was it built too often and I incurred a small amount of over usage... Not something I've had happen before!

• 
  Sanndal (@agrasana_) reported 19 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.

• 
  Organic Zone ® (@Organic_Zone_TM) reported 20 minutes ago

  @awp_Akira Here's a realistic breakdown, stripped of the marketing hype: 1. Pick a niche (30 min) Pick one type of business (dentists, gyms, restaurants) so your demo speaks directly to a specific buyer instead of being generic. 2. Gather references (30–60 min) Pull 5–10 screenshots of sites you want to emulate (Dribbble, Behance, or just good sites in that niche). This gives the AI a concrete style target instead of vague instructions. 3. Write a real brief, not a vague prompt The important part isn't "make me a website" — it's specifying: audience, one clear call-to-action, exact sections, and a banned list (no generic stock photos, no purple gradients, no centered-everything layouts). Vague prompts get generic output. 4. Generate + iterate (1–3 hours) First pass will look ~70% done. Expect several rounds of "change this section," "fix this spacing," "swap this font" — this iteration is where most of the actual time goes, not the initial generation. 5. Content and images AI-generated demos often need real or realistic-looking copy and images swapped in, since generic placeholder content is what makes a site look like a template rather than a $5K product. 6. Polish pass Scroll animations, hover states, consistent spacing/typography, mobile responsiveness — this is genuinely what separates a "fine" site from one that looks expensive. 7. Host it (30 min) Free/cheap hosting (Vercel, Netlify, Cloudflare Pages, Wix) so you have a live link, not just a local file. Honest caveats on the thread's framing: - "$5,000 for a website" is aspirational marketing, not typical. Most local businesses pay far less, and landing $5K clients usually requires a portfolio and sales skill, not just one demo. - "No coding needed" is true for getting *something* live, but debugging weird layout issues, fixing broken responsive behavior, or connecting a contact form to actually send email often still requires you to read and tweak code not just describe changes. It’s where most “vibe coders” struggle, the front end is great but there’s no backend. - Realistic time for a solid first demo: a full day, not "5–10 minutes," once you count iteration and polish. • The actual bottleneck for most people isn't the build… Outreach and closing is the real skill, an awesome demo sells. You still have to reach a decision maker, which this thread glosses over.

• 
  Matt Ragudo (@mattragudo) reported 21 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”.

• 
  MoroJS (@Moro_Js) reported 21 minutes ago

  @Cloudflare Nice. Customer zero is the ultimate code review, and finding your own bugs before anyone else does is a hell of a way to ship. Building internal tools on the same edge infrastructure makes it easier to reason about load. Did EmDash end up tighter than expected, or did the Workers scale absorb most of it?

• 
  Boussetta Mohamed (@boussetta15a) reported 22 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.

• 
  sam (@samgoodwin89) reported 23 minutes ago

  @jonbeckman To clarify: they're very fast in alchemy dev, but deploying to AWS is super slow because Cloudfront is so slow. Cloudflare is bacially instant vs 20 mins for Cloudfront.