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:

• 
  Jeff Liford (@JeffLiford) reported 8 minutes ago

  @Cloudflare @CloudflareSys @CloudflareDev Cloudflare is operational again at this time, however I am encountering an issue with one domain name being redirected to an improperly spelled domain. Currently investigating root cause.

• 
  Ivo (@IvoAI3) reported 10 minutes ago

  The part of this stack that should get more attention: He's not paying $6/account/month minimum on social posting through @zernio_api just to get this running. First 2 accounts are free. PHP, SQLite, and Cloudflare R2 instead of the usual Next.js + Kubernetes stack most people think they need. This is what "no VC" actually looks like in code, not just in a tweet. Most SaaS ideas die in the infrastructure decision before they ever reach a customer.

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 11 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 ⭐

• 
  surya murugan (@SuryaMurugan_) reported 12 minutes ago

  @elithrar @dok2001 @Cloudflare Please add support for r2 data localization in India. Cannot use r2 for any DPDP act complaint services. 🙃

• 
  Chaos (@Chaos_lfg) reported 12 minutes ago

  Regarding $DESC, the product may launch today. I did some research, and here’s everything you need to know: Supported by: AR, Molecule , BankrBot, Akash Network 1Claw AI has already been successfully integrated into DescAI. Team Lead Coby recently participated in the Base hackathon. I believe Base will support a project that has been incubated within its ecosystem. The core idea behind DescAI: DeScAI is a project at the intersection of DeSci (decentralized science) and AI. Its core, Agent-Core, is essentially an "automated scientific review factory": an autonomous AI agent that finds scientific content across crypto-science ecosystems on its own, runs it through a pipeline of language models, and produces a structured quality assessment. Crawling. The agent gathers source data from three places: ResearchHub (scientific papers and funding proposals), Molecule IPNFTs (tokenized intellectual property from research DAOs), and Pump Science (chemical compound tokens for longevity research). github Reviewing. Each content type has its own LLM pipeline. For example, the articles pipeline is a 13-step process: extracting scientific claims from a PDF, routing them, and grading the empirical evidence, including originality checks against the OpenAlex database. github Output. Every run produces a standard bundle: review.json with integer scores from 0 to 100, overview.json — a plain-language summary, and evidence_audit.md — a provenance audit trail showing the sources behind each conclusion. github Publishing. Finished reviews can be published to Arweave (a permanent data storage blockchain) and backed up to private Cloudflare R2 storage. Writing to Arweave makes a review permanent, immutable, and publicly verifiable. github In short: it's an AI reviewer that automatically checks the quality of science in crypto-science projects and records its verdicts on the blockchain. Where it will be applied The project addresses the main pain point of the DeSci ecosystem: there are plenty of tokenized "science" assets, but almost no independent expert evaluation. Concrete use cases: Due diligence for DeSci token investors. On Pump Science, people trade chemical compound tokens (like RIF and URO) tied to real longevity experiments. The agent provides an independent AI assessment of a compound's scientific merit before someone buys the token. Gate LearnThe Defiant Evaluating funding proposals. ResearchHub collects crowdfunded research proposals — the agent reviews them and helps the community decide what to fund. Screening research DAOs. The DAO pipeline takes an IPNFT "dataroom" from Molecule and produces a six-category review — in other words, it evaluates tokenized scientific projects and their intellectual property. github Replacing/supplementing traditional peer review. Conventional peer review is slow and closed; here, a review is generated automatically, comes with an evidence trail, and is stored publicly and permanently.

• 
  Trent (@TrentBuysValue) reported 19 minutes ago

  @LazyPepper @AmoremPatriae @PaulineHansonOz More likely a DDOS attach to prevent people from donating. Looks like Cloudflare has just been added to help mitigate it.

• 
  MaiKaun (@MaiKaun415422) reported 24 minutes ago

  @vanyaSile The thesis is sound: AI agents are scraping the web at scale, publishers are watching referral traffic collapse, and there’s no clean way to charge a bot for access. Cloudflare already launched pay-per-crawl, the x402 payment standard exists, and people are betting on agent-to-machine micropayments. The hard parts, honestly: You’re picking a fight with adoption on both sides at once. Publishers need to install you AND agents need to pay through you. That two-sided cold start is brutal, and the side with leverage (the big AI labs) has every incentive to route around you or strike direct licensing deals, which is what’s already happening (Reddit-Google, OpenAI-publishers). Whoever owns the chokepoint wins, and right now that’s CDNs and identity layers. Cloudflare sits in front of ~20% of the web and can bundle this for free. A standalone infra startup has to explain why a publisher adds another vendor instead of flipping a switch on infrastructure they already run. The defensibility is thin unless you own either the bot-identity/verification problem (hard, valuable) or become the default settlement rail (network effects, winner-take-most). “We let sites charge agents” as a feature gets absorbed. Where I’d actually look: the verification and pricing layer, not the toll booth. Knowing which agent is asking, on whose behalf, and what the data is worth dynamically is the genuinely unsolved part. The payment plumbing is becoming a commodity standard fast. For Transparency: Ofcourse I validated the idea with AI and added some of own flavor!

• 
  Чернобог 🜏 (@iamchernobog) reported 24 minutes ago

  @vitalune7 @lloyd094 @Teknium You can use it via cloudflare tunnel, the problem is you need to put the whole dashboard open in a subdomain for the whole net, and the dashboard currently does not have an authentication screen, cloudflare has one, but if you use it, the gateway doesn't work

• 
  chan (@chantastic) reported 25 minutes ago

  @datalyncs yeah it’s bad out there. i honestly can’t be bothered to **** with it anymore. my apps are 95% Cloudflare and i could probably get away with raw JS for most UI

• 
  Stanley (@stanleyforx) reported 25 minutes ago

  Day 8 of doing 30 brutally honest account audits. @petecodes - 9,528 followers profile snapshot: - 38,924 total posts over 10.5 years (account since Dec 2014) - following 1,479 (6.4:1 ratio, decent but not dominant) - 125,854 likes given (extremely active engager) - verified blue check - pinned tweet: "best marketing I've spent so far" testimonial about High Signal newsletter ads. 5 likes, 2,579 views. weak pin - based in Edinburgh, UK - runs 3 things: ghostwriting service, High Signal newsletter, No CS Degree (dev inspiration) what's actually working: 1. strong opinions on tools people care about are his 67x multiplier. "If you don't like Webflow's price bump do this..." got 70,827 views, 235 likes, 11 RTs, 32 replies. his average post gets 1,070 views. this ONE post accounts for ~70% of all impressions in the entire dataset. when he picks a side on something trending and offers a specific alternative (Claude Code + Astro + Cloudflare), the algorithm goes all in. he's done this exactly once 2. questions that ask for personal experience. "How much are people paying for accountants in UK?" got 9 replies, 1,495 views. "How do you recover from bad sleep?" got 7 replies, 677 views. "Why do devs hate calls?" got 8 replies, 697 views. these consistently outperform his promos. people respond when asked about themselves 3. revenue transparency posts. "$5,950 in May 2026" got 13 likes, 1,183 views. monthly income reports consistently perform above his average. the indie hacker community rewards openness with real numbers 4. event and community content. the Nantes/Uneed Residency posts consistently hit 500-1,600+ views. real-life meetups create social proof and engagement from tagged people. "Great to see everyone at Uneed Residency" got 13 likes the problems: 1. newsletter promos are drowning the feed. ~30% of all posts are some variation of "subscribe to High Signal" or "buy a newsletter ad slot." most of these get 0-1 likes and under 150 views. the audience has completely tuned them out. the "High Signal" newsletter has become low-signal content on his feed 2. threads are structurally broken. the "If I was ghostwriting for @charlierward" thread: opener got 2 likes/163 views, parts 2-6 got 0 likes each and as low as 11 views. thread middles have no hooks, no tension, no reason to keep scrolling. he should either compress these into single posts or learn per-tweet hook structure 3. no consistent content pillar beyond self-promotion. remove the newsletter promos and ghostwriting pitches and there's no clear "why should I follow this person" content strategy. the Webflow post proves he CAN create massive value. but it's one post in 95 4. engagement rate is critically low. 0.60% average across the dataset. excluding the Webflow outlier, drops to ~0.35%. median post gets 270 views on 9.5K followers (2.8% reach). this suggests algorithmic suppression, likely from the high volume of low-engagement promo posts training the algorithm to not distribute his content 5. too many zero-value tweets. bare URL drops with no text, single-sentence non-sequiturs, reply-style tweets that read like they belong in someone else's thread. these dilute feed quality and signal to the algorithm that his content isn't worth distributing 6. the pinned tweet is a newsletter ad testimonial. first thing a new visitor sees is proof that buying ads in his newsletter works. that tells a potential FOLLOWER nothing about why they should follow. the Webflow post (235 likes, 70K views) should be pinned. it actually demonstrates his value 7. the bio is selling three things at once. ghostwriting service, newsletter, dev inspiration site. a new visitor has no idea what he's actually about. the identity is split three ways and none of them get enough oxygen wins he's leaving on the table: 1. the Webflow post format is his proven winner and he's never repeated it. "trending tool does something unpopular → here's the specific alternative stack I'd use instead." he could do this monthly. every time a SaaS raises prices, changes terms, or makes a controversial move, he has license to post "here's what I'd do instead" with a specific technical breakdown. he's done it once. it should be recurring 2. he's a ghostwriter who never shows his ghostwriting process. zero posts about how he analyzes a client's voice, how he structures a content calendar, what frameworks he uses. "here's how I'd rewrite this founder's last 5 tweets" would be the ultimate proof of his service. the ghostwriting pitch would sell itself through demonstration instead of self-promo 3. no CS Degree is a massive brand he doesn't leverage on X. he built an entire platform around developers without computer science degrees. that's a huge audience. but his X content barely mentions it. "this developer taught herself Python in 6 months and now makes $120K" stories from his own platform would be some of the most shareable content on dev Twitter 4. the revenue reports should be a monthly series with structure. "$5,950 in May" works. but "May 2026: $5,950. Here's what worked: [X]. What flopped: [Y]. What I'm trying in June: [Z]" would 3x the engagement because it gives people something to learn from, not just a number to see 5. he's an extremely active engager (125K likes given) but it's not translating. he's clearly reading and liking tons of content. but liking isn't engaging. thoughtful replies to larger accounts would convert that attention into followers. 10 replies per day to 50K+ accounts in the indie hacker space would move the needle more than 3 newsletter promos 6. the Edinburgh indie hacker angle is unused. building a solo business from Scotland, outside the SF/London bubble. that's a relatable narrative for thousands of remote builders. "building a $6K/month business from a cafe in Edinburgh" is a story. "subscribe to my newsletter" is not opportunities he hasn't seen: 1. "ghostwriter rewrites your tweet" series. take a follower's tweet (with permission), show the original, show his rewrite, explain the changes. this is his entire service demonstrated publicly. it sells the ghostwriting without ever asking for a sale. it's also insanely engaging because people love seeing their content featured and improved 2. "what I'd do differently if I started No CS Degree today" retrospective. he's been running it for years. the lessons from building a dev community without being a traditional CS grad himself would resonate with every self-taught developer on the platform. that's millions of people 3. leaning into the "I read 200 newsletters so you don't have to" curator angle. High Signal's value prop is curation. but his X promos just say "subscribe." instead, post the actual signal. "3 things I read this week that are worth your time" with genuine recommendations. give the value first, then the CTA earns its click 4. the "ghostwriting for [famous person]" format needs fixing, not killing. the concept is gold. "if I was ghostwriting for Elon, here's his content strategy in 5 tweets" is compelling. but the execution failed because the threads had no per-tweet hooks. compress each into a single post with the 3 biggest changes he'd make. one post, not a 6-part thread that dies at part 2 5. pricing and business model transparency. "what it actually costs to run a newsletter, a ghostwriting service, and a community site simultaneously." the indie hacker audience would devour this. real costs, real margins, what's worth it and what isn't. he's running 3 businesses. the meta-content about juggling them is more interesting than any of them individually 6. "here's what I learned ghostwriting for 10 different founders" synthesis post. no names needed. just patterns. "8 out of 10 founders make the same mistake in their first tweet of the day." that's a hook that drives both engagement and inbound leads for his service what he should double down on: 1. the contrarian tool take. proven at 67x his baseline. one per month when a SaaS does something unpopular. specific alternative stacks, not just complaints 2. show the ghostwriting work. public rewrites, before/afters, strategy breakdowns. sell the service by demonstrating it, never by promoting it 3. revenue transparency with lessons. monthly reports with what worked and what didn't. the number alone is a tweet. the number plus the lesson is content 4. kill the bare URL promos. every naked link with 0 likes is actively suppressing his reach. either add genuine value above the link or don't post it 5. compress threads into single posts. his thread middles die at 11-82 views. at 9.5K followers, one punchy post with the core insight will outperform a 6-part thread every single time bottom line: pete has 9.5K followers, three revenue streams, the proof that he can create a 70K-view post, and an extremely active engagement habit (125K likes). but 30% of his output is newsletter promos that get 0 likes, his threads structurally collapse after tweet 1, and his ghostwriting expertise is completely invisible on his feed. the fix is simple: stop promoting and start demonstrating. show the ghostwriting process, give the newsletter value before asking for the subscribe, and repeat the Webflow format that already proved it works at 67x his baseline. what do you say @petecodes, did i get it right? hit me up if you want to brainstorm more ideas together.

• 
  Jason from BallotScore.com (@goldenelephant1) reported 25 minutes ago

  @Cloudflare What i see is hackers using Cloudflare to circumvent their services by using them as a reverse proxy. I have seen multiple attacks trying to grab my .env, checking for wp-install etc files all from Cloudflare IP's. Reported it to You. You said **** off!

• 
  George Apostolakis (@Apostolakis_Geo) reported 26 minutes ago

  @YashHustle_22 I used netlify for small projects in the past until I realised that it sucks so I switched to cloudflare

• 
  The AI Entrepreneur (@ai_in_it) reported 27 minutes ago

  the big AI labs trained on most of the public web. now a ton of those same sites are locked down tight. cloudflare, login walls, bot checks you basically have to pay to clear.

• 
  Josh (@josh_nimako) reported 28 minutes ago

  What Outranking a $1B Company Taught Me Before My 1.7M User SEO Project Died One of my first serious SEO projects is dead now. Before it died, it reached over 1.7 million active users, gave me my first million clicks, and for about a month, and even outranked a company doing around $1B in revenue. But the failures were louder than the losses. The real lesson came after the rankings started working, because traffic showed me every weak part of the site, the server, the content, the tracking, and my thinking at the time. I knew enough to build the site, publish content, target searches, add schema, work on image SEO, and chase fresh demand, but I did not yet understand what happens when the traffic actually lands. Getting traffic is one problem. Surviving traffic is another. The site started as a normal beginner project. Some of it worked faster than I expected. I learned that image SEO can be a serious traffic source when the niche has visual demand, schema can help Google understand the page faster, and freshness can matter more than authority when a search window opens for a short period of time. I also learned how powerful Reddit can be. We used Reddit as part of the distribution layer, not because it was magic, but because Google already trusted the platform and certain threads could rank fast when the query had the right shape. That was my first real lesson in parasite SEO. Sometimes the fastest way to appear in search is not to wait for your own domain to build trust, but to place the right content on a platform Google already trusts, then use that page to capture demand while your own asset grows. That does not replace building your own site. It teaches you how distribution actually works. For about a month, that kind of thinking helped me outrank a company with far more money, authority, and resources than me. I was not better than them. I was just closer to the search. I understood the timing, the page format, the image demand, the freshness window, and the exact thing the user wanted in that moment. That changed how I saw SEO. Big companies can win on authority, but small operators can still win narrow battles when they move faster, match intent better, and understand the search better than the bigger player does. Then the site started breaking. During traffic spikes, pages would freeze, the server would throw 502 and 504 errors, and the site could be unavailable for long periods while I tried to work out what was happening. At the time, the server was exposed directly to the internet, so every request hit the origin server. Real users hit it. Scraper bots hit it. Aggressive crawlers hit it. Bad traffic hit it. Everything hit the same machine. The PHP-FPM pool started choking, Apache logs showed worker thread errors, and the server ran out of breathing room because it was trying to handle too many requests at once. That was the first time I understood that infrastructure is part of SEO. If Google sends traffic and the site falls over, that is not only a server problem. It becomes a crawl problem, a trust problem, a user problem, a revenue problem, and eventually a search problem. The worst issue was inside the theme. The site used Themify Ultra, and one function was checking images through full public URLs instead of local file paths. That sounds small until traffic hits. One page view could cause the server to make extra HTTP requests back to itself to inspect images, so instead of one visitor creating one normal request, the server created more work for itself while also dealing with real users and bots. It was a self-DDoS loop. The site was not only being hit from outside. It was also wasting resources calling itself. We fixed it by bypassing the image-checking behaviour and adding a local hosts shortcut so the server could resolve itself internally instead of going out through the public internet. That one bug changed how I think about performance. Performance is not just a page speed score. Performance is what happens when the whole system is under pressure. Then we put Cloudflare properly in front of the server. Before that, the origin IP was exposed, which meant bots and scrapers could hit the machine directly. Now Cloudflare became the front line. It hid the real server IP, cached static assets like images, CSS, and JavaScript, and challenged or blocked bad bot traffic before it reached the server. That took pressure off the origin. The server no longer had to serve every image to every visitor, and it no longer had to take every bot request directly. Now, if I build a site that depends on organic traffic, I do not treat Cloudflare, caching, bot filtering, and origin protection as extras. They are part of the build from day one. I also learned that bots are not a small issue. Some were scraping content. Some were hammering pages. Some were burning CPU without acting like users. They did not convert, subscribe, read properly, or add anything useful. They just created load. That forced me to learn server logs, Nginx logs, Apache errors, PHP worker limits, caching, bot protection, and traffic spike behaviour, because Analytics could tell me people were visiting, but the server logs showed what was actually hitting the machine. That changed how I use SEO tools too. Ahrefs and Semrush are useful, but they are not the market. In this niche, demand could spike fast when new content appeared, and a page could get thousands of clicks in the first hour before the window closed. A third-party tool might not show that properly because the demand moved too quickly. Search Console showed what Google actually sent. Analytics showed what users did. Server logs showed what hit the server. No single tool had the full truth. I also made quality mistakes. One of the biggest was allowing an unmoderated comment section. At the time, I thought comments were harmless because they added more text and activity to the page. That was naive. Spam, thin replies, irrelevant text, and messy user-generated content made pages worse. The site had traffic, but parts of it started to look lower quality than they should have. That taught me that more content is not always better. More indexable text is not always better. If the page is the asset, you cannot let random people lower its quality. Now I think about SEO very differently. Before this project, I thought SEO was mostly about ranking pages. Now I think it is about building systems that can turn search demand into something useful without breaking. That means the page has to match intent, the content has to be controlled, the server has to survive traffic, the logs have to be watched, the origin has to be protected, and the traffic has to lead somewhere beyond a graph inside Analytics. The site is dead now. Some reasons were strategic. Some were technical. Some were niche specific. All were my fault in the end. But I do not see it as wasted work. It taught me how real traffic behaves. It taught me that a page can rank and still be fragile. It taught me that a site can have users and still be a weak asset. It taught me that small operators can beat giants in narrow search windows and that Reddit and parasite SEO can move fast when the query fits. It taught me that Cloudflare can be the difference between traffic and downtime and that server logs tell a different story from dashboards. It taught me that the next problem starts after the ranking works. That is the part I carry into every project now. I do not just ask: Can this rank? I ask: Can it survive the traffic? Can it stay clean? Can it handle bots? Can it load under pressure? Can it earn trust? Can it turn attention into users, leads, revenue, data, authority, or another asset? My first serious SEO project is dead. But it gave me the lessons I needed. And those lessons are now part of how I build.

• 
  Abolaji Rasaq Oluwapese (@bolazeal) reported 29 minutes ago

  @echo_vick Install Cloudflare Warp to fix this issue