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.

• Domains (41%)
• Cloud Services (26%)
• Hosting (17%)
• Web Tools (11%)
• E-mail (4%)

Live Outage Map

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

City	Problem Type	Report Time
Noida	Hosting	7 days ago
Jewar	E-mail	7 days ago
Braga	Web Tools	7 days ago
Noida	Cloud Services	8 days ago
Paris	Cloud Services	8 days ago
Prievidza	Domains	9 days 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:

• 
  Ivan_Qtech (@ivanjovic) reported 6 minutes ago

  @cursor_ai But where do i runt this agent i đanaged to install it through the github action but i think that is wrong becuse it runs from the stsrt each time. Can i somehow use it throguh cloudflare containers? @grok please help?

• 
  Anh Tran (@rilwis) reported 6 minutes ago

  @rmelogli @learnwithmattc I usually use browser bookmarks. But it becomes a problem when switching browsers. So I export it to a html file, tell Claude to design it a little bit, and deploy to Cloudflare. Now I set it as my browser homepage :)

• 
  Raphaël T-M (@raphaeltm_) reported 12 minutes ago

  I want these so bad. @Cloudflare wanna bring these to #Paris?

• 
  Leo - 14 y/o founder (@leodev) reported 15 minutes ago

  @theCTO i've got a cloudflare hat with "agents never sleep"

• 
  Turtle. (@TurtleOne_) reported 15 minutes ago

  @LanceHalo @MarathonDevTeam Probably a combination of cloudflare being flooded + some unfortunate save data syncing error. Sometimes it's better not to disclose the issue to prevent bad actors from attempting to stress test the fix

• 
  PiBazar.eu™ & Jwkk.Biz™ (@jwkkbiz) reported 16 minutes ago

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

• 
  Stunlokked (@stunlokked) reported 20 minutes ago

  @xai @Cloudflare ******* great. now when cloudflare shits the bed another service will get taken with it.

• 
  Logan Thorneloe (@loganthorneloe) reported 20 minutes ago

  @aarondfrancis @browserbase @Cloudflare That is the worst government website

• 
  Anurag Bhagsain (@abhagsain) reported 30 minutes ago

  Woke up at 4AM to work Spent next 5hrs chasing a bug that claude said is from the cloudflare agent think sdk 😭 I'm gonna need a nap now @mattzcarey @threepointone pls send help. I have raised an issue # 1649

• 
  📈📉💸 (@Bicepmonkey) reported 30 minutes ago

  Good day, Money Market! GitLab $GTLB released its earnings report for the first quarter of fiscal year 2027. The stock has gotten volatile since the numbers dropped. Full-year revenue guidance remained about the same overall, though they raised the lower end of the outlook by a small amount. The main item that stirred things up was the plan to replace around 14% of the workforce with artificial intelligence. Cloudflare $NET went down a similar path not long ago. The market has pushed back because this could make it harder for the company to scale its operations in the future. Companies trying to grow usually hire more salespeople and developers to grab market share and keep up with customer needs. GitLab $GTLB has put its money into buying back shares instead. That choice often leaves investors worried that growth is drying up. I have not changed my view on GitLab $GTLB and see this as mostly noise around the stock. The company is working to restart stronger revenue growth. It plans to bring on additional salespeople. These new roles probably do not overlap with the positions AI will handle. The approach also calls for more upfront selling to new customers along with more detailed pricing tiers. I will check in on the progress early in 2027. Shares currently trade at a price-to-sales ratio below 5. That level sits below the average across my coverage list and below the trailing four-quarter average that GitLab $GTLB has posted. Both of those averages come in near 8. The valuation does not look expensive when stacked against the 17% revenue growth projected for this year.

• 
  Keith Ramphal (@KeithRamphal) reported 30 minutes ago

  @NoamTenne @Cloudflare Because there's no situation where they talk down to you, you might be wrong in how you think something works, but they're always polite and professional. If you show up with a security issue, you *will* get attention. Probably more than you expect. CF does it right and they do it at scale.

• 
  𝑮𝑹𝑹𝑳 (@GRRLmusic) reported 32 minutes ago

  @DominicEkom_ @David_Rudnick yeah looool people who would buy and wear cloudflare merch (especially **** that looks that bad) of their own volition definitely have questionable (******* horrendous) taste

• 
  Artur Chmaro ⛛ (@ArtiChmaro) reported 33 minutes ago

  Does anyone run Railway on production? It’s perfect for poc, demos but running production app on it is damn expensive (especially memory usage). After many attempts to optimize memory usage with cache, cloudflare etc I just decided to move into self-hosted VPS with Coolify and Hermes for management. VPS is already cheaper and still have capacity to serve more apps. I hope this would be my final setup. Don't want to move it again 🥲

• 
  Dave (@DaveDiederen) reported 35 minutes ago

  @realboyuanzhao Hahahah so recognisable. Had this when CloudFlare went down last year and we were working on a custom cart. All cart apps went down and the brand went off on me saying we broke the store, just to realise that it was a CloudFlare outage. The relief after that bro was insane

• 
  Dennis Beatty (@dnsbty) reported 36 minutes ago

  @eastdakota @NoamTenne @Cloudflare I think Cloudflare is great if you can self serve everything, but once you need support it's kind of terrible. I'm on an enterprise account through Cloudflare for Startups, and my ticket has been open for a month with no response.

• 
  Olaf Geibig eu/acc AI==危机 🇩🇪🇵🇱🇪🇺🌐 (@olafgeibig) reported 38 minutes ago

  @tonbistudio I find dealing with tmux too complicated. I simply configured a VPN with WireGuard on my internet router and I have the same - fully open source. I have several Hermes related services on my homelab exposed via the free cloudflare tunnel: Hermes Dashboard, Hermes web-ui. That alone gives you a lot of security: DDoS protection, WAF with OWASP Top 10, an IP in the cloudflare edge network and NOT your router's IP. With few clicks using cloudflare's Zero Trust services, I added an OpenId provider in front of my exposed services, e.g. Google OAuth.

• 
  Alabamawildman (@Alabamawil97387) reported 40 minutes ago

  @CloudflareDev @xai @Cloudflare Cloud-based sucks.

• 
  qualk 🌲🪓 (@qualk37) reported 40 minutes ago

  @thepix_elated @rpcs3 @TencentGlobal a DDoS doesn't have to be malicious, they just typically are. additionally they're actively and knowingly circumventing mechanisms that forbid them with an overwhelming amount of requests which if they didn't have the Cloudflare anti DDoS their infra would definitely go down

• 
  Babak (@TheUnicornist) reported 42 minutes ago

  @jamesqquick ok. I was waiting for you to say cloudflare any moment but that moment never came

• 
  Mohit (@codewith55) reported 44 minutes ago

  Total monthly cost to run a startup: $20 - Claude = coding ($20/mo)💲 - Supabase = backend (Free)✅ - Vercel = deploying (Free)✅ - Namecheap = domain ($12/yr)💲 - Stripe = payments.(2.9%/transaction)💲 - GitHub = version control (Free)✅ - Resend = emails (Free)✅ - Clerk = auth (Free)✅ - Cloudflare = DNS (Free)✅ - PostHog = analytics (Free)✅ - Sentry = error tracking (Free)✅ - Upstash = Redis (Free)✅ - Pinecone = vector DB (Free)✅ There has never been a cheaper time to build

• 
  𝙵𝚛𝚎𝚎 𝙶𝚘𝚗𝚊𝚍 (@stronkly_typed) reported 44 minutes ago

  @KuptoKosmos @Cloudflare wtf is this, be a serious company for once please

• 
  ✨NovaNate ✨ (@NathangamerX) reported 44 minutes ago

  @NTE_GL dear NTE I Have sent an email to customer support regarding issue i had with moments during live stream experinnce network loss during game and it stays stuck and apparently when i active cloudflare the experience goes well and never have that issue and i kindly asked and worded in the email to check that issue out and hopefully get that resolved (:

• 
  DoNcHuiiiTo X (@DoNcHuiiiToX) reported 45 minutes ago

  The risk of relying on one hosting provider. When they go down, everything goes down with you. The real fix here is having redundancy ideally a backup server on a different provider and some DDoS protection in front like Cloudflare. That way, if one host has issues, the site can switch over to the backup or stay partially online instead of going completely down. @MagneticXRPL

• 
  Grandma Sez So (@GrandmaSezSo) reported 47 minutes ago

  @Cloudflare @MeckaAI Cloudflare sux. Click troubleshoot and even the form to send problem doesn't submit. I hate when websites use Cloudflare.

• 
  Quasar Markets (@QuasarMarkets) reported 52 minutes ago

  THE AVERAGE IPO DARLING FALLS 55% BEFORE THE STORY IS WRITTEN Everybody talks about the #IPO pop. Almost nobody talks about what happens next. I pulled together a basket of some of the most recognizable growth IPOs and recent market darlings. The results are eye-opening. The average stock in this group experienced a maximum drawdown of 55%. The median drawdown was 54%. Some of the biggest names in tech, fintech, cloud, AI, ridesharing, and crypto suffered declines of 70%, 80%, even 90% before finding their footing—or never recovering at all. Yet the winners became legendary. Palantir. ARM. CoreWeave. MongoDB. Datadog. Cloudflare. That’s the lesson. Investing isn’t about avoiding volatility. It’s about identifying which companies can survive it. The market has a way of shaking out weak hands long before it rewards conviction. Day One is about excitement. Year One is about execution. The next decade is about whether the business can compound revenue, cash flow, and competitive advantage. The greatest wealth creators weren’t built on opening day. They were built by investors willing to sit through the uncomfortable middle. At Quasar Markets, we’re less interested in the IPO headline and more interested in the long-term story the data is trying to tell. Follow @QuasarMarkets

• 
  Lumexis (@kandy_dev) reported 55 minutes ago

  I run a real SaaS for almost nothing. SwiftIn lives on free tiers. The only thing I actually pay for is the AI that does the translating. Everything else is wired together so tightly that I barely open a dashboard anymore. Here's why. Every tool I use talks to Claude directly, through something called MCP. It connects the AI to the live service, not a copy-paste of it. So instead of logging into six dashboards, I just ask. Supabase is my database. I ask why a user's data looks wrong, and Claude queries the database and tells me. No SQL editor, no clicking around. Railway runs my backend. "Is the last deploy healthy?" It reads the logs and answers. If something is on fire, I know before a user emails me. Sentry catches the crashes. An error lands, Claude opens the issue, reads the stack trace, and usually hands me the cause and the fix in one go. Vercel hosts the frontend. A deploy fails, it reads the build log and points at the exact line, instead of me squinting at red text. PostHog tells me what people actually do. I ask what changed after yesterday's release, and it pulls the numbers and the drop-offs. Cloudflare sits in front of all of it as the CDN. The boring, reliable layer I almost never think about. Which is the whole point. This isn't a big team. It's one person, a stack of free tiers, and an AI that can reach into every one of them. And the timing is the whole trick. I'm not scaling yet. I'm still finding users. This is the marketing stage, the part where you learn who the product is really for. Paying for serious infrastructure now would be paying for a problem I don't have yet. Free tiers carry you straight through this stage. By the time you outgrow them, the product is already paying for itself. The cost of building just fell through the floor. Most people haven't noticed yet.

• 
  Nilmani Prashant (@NILMANIPRASHANT) reported 58 minutes ago

  Rate limiting isn't about blocking requests. It's about **protecting system invariants under adversarial load** — including your own code doing something stupid at 2am. --- **The precise definition most people skip:** A rate limiter is a policy enforcement mechanism that maps an identity (user, IP, API key, service) × resource (endpoint, DB, queue) × time window to an allowed request budget. Miss any of those three dimensions and your limiter is incomplete. --- **The five algorithms — and what they actually trade:** **Fixed Window** — simplest. Bucket resets on clock boundary. Problem: 2x burst at the seam. If your limit is 100 req/min, a client sends 100 at :59 and 100 at :01. You've served 200 in 2 seconds. This is how Cloudflare's early DDoS protection got punched through. **Sliding Window Log** — stores each request timestamp. Exact, no burst artifact. Cost: O(n) memory per user. At Stripe's API scale (~500M requests/day), storing per-request timestamps across even 1% of users is untenable without aggressive TTL management. **Sliding Window Counter** — approximation using two fixed windows weighted by overlap. Formula: `current_count + previous_count × ((window_size - elapsed) / window_size)`. Stripe uses this. ~0.003% error rate in practice. Memory: O(1) per user. **Token Bucket** — refill at constant rate, allow burst up to capacity. AWS API Gateway uses this. 10,000 req/s steady-state, 5,000 burst above that. Requests consume tokens; tokens refill at rate R. Good for bursty-but-average-bounded traffic. **Leaky Bucket** — requests queue, drain at fixed rate. Smooths output regardless of input shape. Netflix uses this on their Zuul edge layer to protect downstream microservices from thundering herd. Queue depth becomes your config ****. --- **Where this actually lives in distributed systems:** Local in-process: fast (~1μs), but worthless in a multi-node fleet. Node A doesn't know what Node B allowed. Centralized Redis: ~1-3ms round trip. Use Lua scripts for atomicity — `INCR` + `EXPIRE` in a single script. Redis's single-threaded command execution gives you linearizability for free. This is what most Stripe, GitHub, and Twilio rate limiters use at the storage layer. Gossip/eventually consistent: each node tracks local counts, syncs async. Allows ~N× over-serving where N = node count before sync. Acceptable for soft limits (analytics APIs), not for billing or security enforcement. --- **The senior engineer gotcha:** You set a 1000 req/min limit. Load test passes. You ship. Three months later, you get paged. Latency on your downstream DB is 40× normal. Your rate limiter is working perfectly — 1000 req/min per user, 10,000 users, that's 166 req/s aggregate, which was fine in testing with 100 users. **You rate-limited per identity but never modeled aggregate load.** The limiter protected individual users from themselves but said nothing about what your system can actually handle. You needed a global ceiling, not just per-user quotas. Google's SRE book calls this the difference between *demand-side limiting* (per user) and *supply-side limiting* (per resource). You need both. Stripe enforces per-API-key limits AND global concurrency limits per endpoint via a token bucket at the load balancer level. --- **When NOT to rate limit at the application layer:** If your bottleneck is CPU-bound work (ML inference, crypto ops), rate limiting requests doesn't help — you need a work queue with backpressure. If you rate limit, you'll drop valid requests while the remaining 10% still saturate your CPU. This is why Google's Bard/Gemini API uses quota + async job queues for expensive inference calls, not synchronous rate limiting alone. --- **Numbers worth memorizing:** Redis INCR throughput: ~100K ops/sec single node, ~1M/sec with clustering. Lua atomic script overhead: ~15% vs raw INCR. P99 latency on Redis rate-check in same-region AWS: 800μs–2ms. Sliding window counter error

• 
  Luke Parker (@LukeParkerDev) reported 58 minutes ago

  @theo @NoamTenne @Cloudflare I swear everyone at CF is also devrel (and not bad at it)

• 
  Tony Dinh (@tdinh_me) reported 1 hour ago

  This project involves an iOS app, sign-in with apple, in-app purchase, revenue cat, api backend server, firecracker sandbox, AI gateway, database (postgresql), a blob storage, cloudflare R2, DNS for linking domains, a minimal harness to build a website, and a lot of prompts. Normally, this would take a team of 10 at least. Now I do it alone fully remote via telegram from my phone. I only looked at the code once (due to a potential security concern), but other than that I never read a line of code. I do most of my reviews via prototypes, diagrams, text, and, html reports. The future is going to be wild.

• 
  The American Protectors of Journalistic Freedom (@melisandrePro) reported 1 hour ago

  Cloudflare Is a terrible interference that keeps you from searching websites. It does exactly the opposite as intended.