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 (27%)
• Hosting (18%)
• Web Tools (9%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	13 hours ago
London	Domains	3 days ago
Noida	Hosting	16 days ago
Jewar	E-mail	16 days ago
Braga	Web Tools	16 days ago
Noida	Cloud Services	17 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:

• 
  Tradeus Alpi (@TradeusAlpi) reported 6 minutes ago

  @HabeebSz @nthglsn @Cloudflare Imagine paying 22k and then the support blocks your account

• 
  Maximum YT (@Maximum__YT) reported 7 minutes ago

  @status_is_down This seems like a Canada wide issue, cloudflare and telus is down.

• 
  STEVExKONG (@STEVExKONG) reported 9 minutes ago

  @SSOUIC @ChatGPTapp It’s probably not a changing design… but a network issue, I got the Liquid Glass UI when I’m on cellular, but if I use WiFi it’s back to the one in your first picture…(can’t change model either) codex said it’s probably due to my wifi returned a challenge from CloudFlare

• 
  Enzo (@Captain_Enz0) reported 10 minutes ago

  @Touchtheginger @OldSchoolRS Authenticator linked to both the account and attached email, with the email being used for nothing but the account is as good as any other security. Tons of cloudflare problems when I was overseas, even with a VPN. Linking all characters to one account leads to more vulnerability if you do have a hack of any kind. If they false ban you, which they have done plenty of times (faux), they can nuke your whole account and all characters associated. Love OSRS and the team, think jagex is making a lot of good moves in general, but **** the jagex launcher

• 
  Goodness And Mercy (@FineAndRich) reported 11 minutes ago

  🚨 Cloudflare is currently investigating issues affecting the Dashboard and related APIs. ❌ Dashboard requests may fail ❌ API calls may return errors ✅ CDN cached content remains operational ✅ Edge security services are unaffected If your automation or deployments are acting up, Cloudflare may be the reason. #Cloudflare

• 
  Jake (@JakeKing) reported 15 minutes ago

  @Cloudflare lead the charge dogfooding their own tools: locked down ALL external AI tool access internally at end of 2025, before their controls were even fully built.

• 
  Ivon Huang (@Ivon852) reported 17 minutes ago

  GoDaddy positions itself as an all-in-one website-building platform for small and medium-sized businesses. Besides domains, they also sell website builders, WordPress hosting, email, SSL, WHOIS protection, and marketing tools. GoDaddy is often cheap for the first year, then the renewal price goes up. But I don’t need any of those add-on services. So this year, I finally made up my mind and transferred my domain to Cloudflare Registrar. The price was basically cut in half. Cloudflare Registrar sells domains almost at cost. The transfer process was surprisingly straightforward. I thought GoDaddy’s terrible interface would try every possible trick to stop me from transferring out. But in the end, I just filled out a form, got the authorization code, and that was it. A domain transfer usually does not require an extra transfer fee. Your website will not go offline during the transfer process, but it usually takes at least three days to complete. After the domain transfer, the new registrar will charge you for one year of renewal upfront.

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

• 
  Drew Studlino (@DrewAstudlino) reported 18 minutes ago

  @Cloudflare FIX Your broken Verify im human Bullshit verification or youll be on the Docket too!! Im Done with all of You #TOSPIRATES!

• 
  Чернобог 🜏 (@iamchernobog) reported 19 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

• 
  Chuks 🔶️ (@chuksXB) reported 20 minutes ago

  @nthglsn @Cloudflare Wtf is wrong with them

• 
  Puneet Patwari (@system_monarch) reported 20 minutes ago

  Where CDNs are heading (and why it changes how you architect things): Traditional CDN → cache files at the edge Modern CDN → run actual code at the edge Cloudflare Workers, Lambda@Edge, Fastly Compute, Vercel Edge Functions. These let you run logic at the CDN layer: - Auth validation — token expired? Return 401 at the edge. Backend never knows someone tried. - A/B testing — route 5% of traffic to a variant by modifying the response at the edge. Zero backend changes. - Geo-personalisation — different pricing, language, content based on location. All at the edge. - Response transforms — Client A wants 5 fields, Client B wants 12. Transform the same cached response differently per client. This blurs the line between "CDN" and "distributed app server." Your origin handles writes and heavy computation. The edge handles everything else. How I think about CDN when designing a system: 1. What's the read-to-write ratio? If it's anywhere near 100:1 (most systems), the CDN is your most important layer. Full stop. 2. Classify content by change frequency: - Never changes → long TTL - Changes hourly → short TTL + stale-while-revalidate - Changes per-request → don't cache (or cache per-cohort) 3. Measure cache hit ratio every week. Below 85%? You're leaving free performance on the table. 4. Move read-heavy, latency-sensitive logic to the edge. Auth checks. Geo-routing. Response transforms. A CDN is not something you bolt on when the site gets slow. It's an architecture decision you make on day one.

• 
  Raccoon 🦝 (@raccoon_builds) reported 24 minutes ago

  @goldenelephant1 @Cloudflare @grok I'm not on the paid one either mate. i was just trying to help you i'll got the same thing as you and my agent Ia told me its wasn't attack only bot. i'm running a taxi company website so yeah. need to be protected.

• 
  TBPN (@tbpn) reported 30 minutes ago

  The smartest thing @eastdakota did before Cloudflare's IPO was offer shares to people who could help the company in the future. "The most clever thing that we did [for the IPO], and this was advice that I got from Qualtrics Co-Founder Ryan Smith, was he said, 'What are you doing about friends and family?' because you can take 5% of the IPO and allocate it to friends and family. I said we weren't going to do it." "He said, 'No, you're thinking about it wrong. Think about the people, who if they owed you a favor, could make a meaningful difference in the future of Cloudflare, and then offer them the ability to invest in the IPO.'" "I said, 'Some people are going to have conflicts.' He said, 'It doesn't matter. Even just the fact you offered it, even if they can't do it, they'll always remember that super fondly.'"

• 
  Miguel Cardoso (@ODordio) reported 32 minutes ago

  After a both brief and long 5 months I was part of the recent culling at Cloudflare. But clankers can't stop clanking thus proud to say that I am joining Snyk to work on Snyk's pentesting clanker and help push it to GA. No vulnerability is gonna be safe from me and my robots.

• 
  Alfian Busyro (@arufian_b) reported 37 minutes ago

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

• 
  Mr. Review Ai (@MrReviewai) reported 37 minutes ago

  3/ The Fix Strategy for WordPress: No hiding the ugly numbers. I’m stripping down unused CSS/JS using Asset CleanUp, setting up advanced caching, and testing Cloudflare routing to optimize global delivery.

• 
  David Siewert (@david1gp) reported 38 minutes ago

  Cloudflare Pages not working? Or I the only one who is affected? ```json {"text":"POST /pages/assets/upload -> 502 Bad Gateway"},{"text":"Cloudflare Ray ID: a0a71049ef6c7049-FRU"}],"kind":"error","name":"APIError"} ``` @CloudflareDev

• 
  Hey Jay (@JJeffrey100) reported 40 minutes ago

  @flameproxies_ no, you need to just use something better than adguard home or whitelist every request from cloudflare. that's the bulk of the issue for *most* households.

• 
  Meccanica (@wattreach) reported 41 minutes ago

  Claude 5 has API access to some significant infrastructure on a project I'm working on including AWS, Cloudflare, and a few others. I'm getting emails saying **** is getting setup I did not even ask for.... and it's all stuff I would have asked for next... Damn. its nuts.

• 
  Stanley (@stanleyforx) reported 43 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.

• 
  TBPN (@tbpn) reported 45 minutes ago

  FULL INTERVIEW: Cloudflare CEO @eastdakota joins TBPN to discuss why agent traffic has surpassed human web traffic, the company's acquisition of VoidZero, and why concerns about data center water usage are overblown. 2:13 - Why today's infrastructure can't support billions of AI agents 7:38 - Bot traffic vs. human traffic 11:51 - Long-running AI agents are the future, not chatbots 15:15 - The 3 reasons companies are moving AI inference to the edge 17:29 - On concerns about data centers using too much water 19:41 - Matthew Prince on lawsuits from Spain and Italy over piracy 22:10 - Why being a public company is healthier than taking VC money 28:57 - Matthew Prince on hiring 1,111 interns 2:13 - Why today's infrastructure can't support billions of AI agents 7:38 - Bot traffic vs. human traffic 11:51 - Long-running AI agents are the future, not chatbots 15:15 - The 3 reasons companies are moving AI inference to the edge 17:29 - On concerns about data centers using too much water 19:41 - Matthew Prince on lawsuits from Spain and Italy over piracy 22:10 - Why being a public company is healthier than taking VC money 28:57 - Matthew Prince on hiring 1,111 interns

• 
  Oleg | webstudio.is (@oleg008) reported 45 minutes ago

  This time @Cloudflare ****** up so badly. Every website broken that uses image resizer. Only matter of time until caches run out and all images are broken.

• 
  Elijah Onato (@ElijahOnato) reported 46 minutes ago

  @NordEye I remember seeing this photo when cloudflare servers went down

• 
  MQ (@Mar364503) reported 51 minutes ago

  Cloudflare said that the world needs 1 billion server CPUs for AI agents, and that’s 20x current global server CPU production. Again, 20 times of current capacities of $TSM and $INTC combined for server CPUs. If their estimates hold well, the fabs at TSMC and Intel should be the most valuable assets in the world. Given how much time it takes to build the shells, install the toolings and run the production at good yields, I don’t see how the CPU shortage would cool down within the next decade. $NVDA $AMD $ARM

• 
  Stealth Exploit (@stealthexploit) reported 55 minutes ago

  Sorry guys I was not available yesterday so here is a summary Google Cloud Run (Hosting) Cloud Run only charges you for the exact milliseconds your app is processing a request. If nobody is visiting the site, the servers instantly scale to zero and you pay absolutely nothing. With Cloud Run you get 2 Million free requests, 360,000 GB-seconds of memory, and 180,000 vCPU-seconds completely free every single month. Cost: $0.00 until you start getting thousands of daily active users Artifact Registry (Storage) This is usually where companies bleed money because old, massive Docker images pile up over months. The Free Tier gives you 0.5 GB of free storage per month but i created the policy.json to aggressively delete images older than 7 days and only keep the last 3 versions this would make my storage incredibly small. Our Nginx/Alpine containers are extremely lightweight (~25MB each). Cost: $0.00 to $0.10 per month. Google Cloud Build (CI/CD) Every time you push code, Google spins up a machine to build your Docker image. The Free Tier also gives you get 120 free build-minutes every single day but since i was using Vite, builds take about 1 to 2 minutes. This means me and my team can push code 60+ times a day for free with an estimated cost of $0.00 or you can just use github CI/CD Network Bandwidth (Egress) Sending data to users costs moneyso google gives you 200GB per month for free, For better optimization use Cloudflare in front of your domains, Cloudflare acts as a massive shield and It aggressively caches your static CSS, JS, and Images on their own edge servers around the world for free. This means only a tiny fraction of your traffic ever actually hits Google Cloud. Estimated Cost: $0.00 cc : @maazscript @LanHubs

• 
  Chamoda Pandithage (@0xchmod) reported 57 minutes ago

  @cagrisarigoz @Cloudflare Yep, down for me

• 
  Josh W (@ItsWelford) reported 57 minutes ago

  Anyone at Cloudflare able to help with an OAuth client? It's still waiting for verification & it makes me think something is wrong, because my other OAuth client verified almost instantly.

• 
  British Tuga (@BritishTuga) reported 59 minutes ago

  @dearg_x @Cloudflare Literally happened to me today. Thought I'd try out Cloudflare domains and Cloudflare pages. Whole thing goes down

• 
  Jake Casto (@0x15f) reported 1 hour ago

  @TRPage_dev @Yank @Cloudflare Use their Slack or Discord for issues u less you pay for premium success. Far faster turn around, open ticket and post issue in relevant channel