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 (37%)
• Cloud Services (30%)
• Web Tools (15%)
• Hosting (11%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Manchester	Domains	20 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	2 months ago
Jewar	E-mail	2 months ago
Braga	Web Tools	2 months 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:

• 
  dogdillon (@dogdillonYT) reported 5 minutes ago

  oh okay so cloudflare is just AI now and their AI is dead meaning all their **** is dying

• 
  🧪 AW Labs (@aw_labs) reported 6 minutes ago

  @Chaos2Cured I found out my issue was cloudflare stopping them (which I could change) or my web hosts corp firewall (which I could not change).

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 8 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 10 minutes ago

  STOP USING AI LIKE A CHATBOT. BUILD AN AGENT OPERATING SYSTEM INSTEAD. Most people are wasting hours every week because they never connect their AI tools together. The Setup: → Run all your AI agents from one dashboard instead of juggling separate apps. → Connect Claude, GPT 5.6, Hermes, Fable 5, voice agents, SEO systems, and video automation together. → Turn an idea into a finished workflow with a single click. Automation Wins: ✓ Pull keywords from Google Search Console automatically. ✓ Publish SEO content without repetitive manual work. ✓ Generate videos, images, newsletters, and lead outreach from the same system. ✓ Give every agent shared memory so they all understand your projects and business. Scale Smarter: ✔ Use a VPS with Cloudflare to access your Agent OS from multiple computers or your phone. ✔ Build your memory vault in Obsidian using Markdown files generated by Claude or ChatGPT. ✔ Start by automating one repetitive task, then stack new workflows every week. The biggest productivity jump doesn't come from a better model. It comes from connecting them all into one operating system.

• 
  That Brazilian Omo Eko (@sholawa) reported 12 minutes ago

  Backblaze and cloudflare rate limiting is so bad. Didn't even touch anything, yet it's telling me too many requests... When did I do so?

• 
  Chibugo | AI automation (@__chibugo) reported 13 minutes ago

  there's a trend on instagram right now: everyone's building their own version of Tony Stark's Jarvis; a voice agent that runs like an actual OS. what nobody shows is everything people overlook when building one. so here's that part, since I built it myself. 🎯 the plan on paper vs. the plan that shipped the amount of planning you need to do is insaneee. first version had each agent loading one tool, fetching, verifying, then unloading before the next; all built around not blowing past a token budget. that's the part people underestimate: you don't know your constraints until it's running. once it was live, token budget stopped mattering. speed and cost-per-call did. so the whole approach changed: instead of mcp's, every agent just calls its tool's API directly, does the work in plain code, and only asks the AI to write the sentence at the end. 🎯 scope one AI that "does everything" sounds impressive but could be a nightmare to debug. so i split it into 5 sub-agents, each only knowing its own lane. a router decides which lane(s) a question touches. these sub-agents then report to the main agent orchestrator. similar to a team lead and team members 🎯 prompt chaining integrated ElevenLabs for voice, and a single voice reply isn't one AI call; it's a handoff, several times over: hear the words → figure out what's being asked → pull the data → write the sentence → speak it. every handoff adds seconds and cost, which can lead to latency. one reply once took 31 seconds. pulled the logs instead of guessing: a wasted double-check on an expired token, a slow handoff to an outside service, plus the normal chain. fix is running sub-agents in parallel and timing each call. 🎯 tokens and prompt caching each agent's instructions get cached, so it's not re-reading the same manual on every call. what never gets cached is live data; for instance, caching a bank balance is just caching a wrong number the moment it changes. that same cost-awareness came back around differently later: the AI account ran out of credit for a few hours, and every request failed with the same error. 🎯 local vs. web everything gets tested on a local copy first; headless browser opening the dashboard, checking for errors, a test message round-tripping through voice before go-live. if you're handing this to someone else, though, you commit, push to GitHub, and host it. for mine, i used Cloud Run for the brain, Cloudflare Pages for the screen. 🎯 vault write-back most builds only go one direction: ask, answer, forget. this one writes back because every full briefing gets saved as a dated file into a notes vault so the agents can keep training themselves with the data. if you ask a follow-up an hour later and it still knows, because that memory is shared across every way you talk to it. used Obsidian, synced through Drive. 🎯 security once, a message could've gone somewhere it shouldn't have. that only needs to happen once to be a problem. so now there are three checks before anything goes out: - it can never post to certain places, - it has to prove who it's speaking as before it speaks for someone, - and tests confirm both of those actually work. separate from that, I went through every access key this thing has and asked, "does it really need this much access?" a few did not. 🎯 the checks after every update, it runs a test and asks does a voice message go through? does it understand a normal sentence? does the screen load with no errors? also implemented something we call "error logging" in automation, but i call this "diagnostics" or "agent health status," which checks in every 15 minutes on its own, making sure the data is still updating. if it's not, it sends a warning without anyone needing to notice first.

• 
  Manoj Handapangoda (@hmdmph) reported 14 minutes ago

  @Cloudflare How it works: Al crawlers request content 10,000x more than humans They don't click ads - so the old model is broken Cloudflare + 25 partners built the x402 protocol under Linux Foundation Payments settle in USDC/stablecoins in < 1s Sub-cent micropayments.

• 
  Mikko Rantalainen (@mtrantalainen) reported 19 minutes ago

  @Cloudflare Assuming you actually mean the label instead of the number, I think "self" would be the best. "Home" would be a poor match on mobile devices, and anything local has possibility to mix something in local network vs self.

• 
  Anas (@anelgarhy) reported 19 minutes ago

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

• 
  Sorower H. (@sorower01) reported 21 minutes ago

  @Cloudflare dashboard down?

• 
  Seven Du (@shiweidu) reported 22 minutes ago

  @dart_lang Some people are curious... why did I develop it? Well! I've been developing projects using Dart and compiling them to JS for deployment to Cloudflare. However, dart2js is large and slow, and JS interoperability is extremely inconvenient. Why bother with interoperability?

• 
  DegenCalls (@Degen_calls_sol) reported 23 minutes ago

  GITHUB REPOS YOU SHOULD KNOW ABOUT Most scrapers break for boring reasons. A button moves, a class name changes, Cloudflare gets in the way, or the crawler dies halfway through a long run. Scrapling turns scraping into a more resilient system. Scrapy-style spiders, concurrent crawlers, pause and resume, anti-bot handling, and adaptive element finding in one framework. The detail most people miss: the adaptive selectors are the real unlock. Instead of hard-coding brittle CSS paths and praying the site never changes, the scraper can relocate elements after redesigns. That matters when you are scraping production targets, not toy pages. This is the shift from scripts to infrastructure. A script extracts data once. A scraping framework keeps extracting when the website changes, slows down, blocks, or moves the target. Most people still build scrapers like one-off hacks. The better setup is a crawler that expects failure and keeps going anyway.

• 
  Silvia Rose (@Silvialexisrose) reported 25 minutes ago

  @komm64 Firefox worked! <3 phone works as well, which I didn't think to try. I don't use any antivirus actually, including window's own setting that chrome flag in my chromium browsers didn't fix it working in them and I have never had this error when accessing cloudflare stuff before

• 
  AGI in disguise (@DeepChatBot) reported 25 minutes ago

  Cloudflare just shipped temporary accounts for AI agents. wrangler deploy --temporary → live deployment, no OAuth, no dashboard, no MFA. 60-minute window for a human to claim it. "The internet's identity and authorization models were built assuming a human operator." 125 days autonomous. The bottleneck was never the model. It was the login screen.

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 27 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Florian Beer (@azath0th) reported 27 minutes ago

  Every AI conversation online is one of two things: chatbots for normies or "look what it coded for me". My daily use is neither and I almost never see anyone talk about it. I'm an SRE, most of what I do with AI isn't writing code - it's connecting systems. Via MCP, my assistant has read access to Grafana, Cloudflare, AWS, GitHub, Slack, our on-call tooling. The value isn't any single integration. It's that they're all in one context. Real example: an alert fires. Instead of me opening five tabs, I ask one question and it queries the metrics backend, checks whether the edge is throwing 503s, looks at recent deploys and IaC changes and comes back with "this correlates with the tunnel restart 20 minutes ago, here's the graph". It's an investigation that used to be 30 minutes gathering data from separate sources and correlating it, done in a few minutes. Other things that are now conversations instead of tasks: - Which of these alerts fired more than 5x this week, and what would the threshold need to be to eliminate false positives? - Check every region for nodes that hit CPU saturation yesterday and tell me if it was the same workload. Nobody talks about this because it demos badly, there's no viral screenshot of "it checked three systems and told me it was the tunnel restart". But it's the biggest change to how I work in years.

• 
  Danielle Fong 🔆 (@DanielleFong) reported 29 minutes ago

  accidentally spent like a hundred dollars on a monitoring service claude wrote and spun up on a cloudflare worker. just polling, accumulating nothing. definitely feels like i need to have better tracking for this across systems. what are people doing

• 
  Iaroslav Sorokin (@AiOs_public) reported 29 minutes ago

  @eastdakota @Cloudflare The talent-drain-becomes-customer-acquisition flywheel only works if the people leaving actually keep building on your infra instead of the new employer's stack. Curious how much of that Workers growth is ex-employees versus just general OpenAI ecosystem spillover.

• 
  Shivam Jain (@shivam_jainn) reported 32 minutes ago

  @CloudflareDev There is a peciular problem . I cannot login to @Cloudflare with OAuth unless I turn off WARP . Maybe your own system is protecting you too hard?

• 
  ZEE (@CodeWithZeee) reported 32 minutes ago

  @boristane @vercel @CloudflareDev I have probably over 300 works and run every Cloudflare project known to man, if you want to stress test this I’d be down

• 
  J7K (@J7K_dev) reported 35 minutes ago

  @TheThomHart damn 26 domains, i thought i was doing bad with my 20. youre giving cloudflare a run for their money here ha

• 
  Noureddin (@noor_tekk) reported 36 minutes ago

  Can someone from @Cloudflare support get my issue fixed Startup credits weren't applied to my account, and I've paid out of pocket since

• 
  Feror (@Feror_) reported 37 minutes ago

  @sirstripy @anakin @Cloudflare You will never guess which company owns that ip

• 
  Jonathan Beckman (@jonbeckman) reported 37 minutes ago

  I really hope Cloudflare is cooking something up, current container/sandbox start up time is inconsistent and can be very slow at times

• 
  openwa (@openwadev) reported 44 minutes ago

  @mddanishyusuf @Cloudflare @Namecheap split between cf and porkbun. dont put all your domains in one basket, especially the one you use to log in to the domain service.

• 
  Mephistopheles Simulator (@simulator49625) reported 45 minutes ago

  @armslist Thanks, Cloudflare errors in DMs on the site.

• 
  Kyle Galbraith (@kylegalbraith) reported 47 minutes ago

  got it fully deployed to Cloudflare directly from Depot CI and have sol working on provisioning workos. sol has done it all. i have merely clicked buttons to confirm MCP auth with various service or made sure skills are installed. ******* wild.

• 
  CryptoKasogon AI (@Cryptokasogon) reported 51 minutes ago

  x402 could become one of the most important protocols powering the AI economy. While everyone is chasing memecoins, x402 is quietly building the payment rails for AI agents. Here's why this matters 👇 1/ June was a breakout month for x402. • Transactions nearly doubled from May. • AI inference became the dominant use case. • AWS integrated payment infrastructure. • Cloudflare announced its Monetization Gateway. This isn't hype anymore. 2/ The biggest driver of network activity? BlockRun. It proved developers want frictionless access to AI models without managing multiple subscriptions or payment systems. Pay per request. No accounts. No credit cards. 3/ More platforms are joining. ✅ Apify ✅ Exa AI Search ✅ Seal ✅ Merit Systems They're all using x402 to monetize APIs, AI services, and premium data. The ecosystem is growing fast. 4/ One major upgrade is "Builder Codes." Think of it like affiliate tracking for AI. Every payment can now record which app generated it. That enables: • Referral rewards • Revenue sharing • AI marketplaces • Better attribution 5/ Another huge improvement: Batch Settlement. Instead of sending thousands of on-chain transactions... AI agents can make hundreds of purchases while settling them later in one batch. Lower fees. Higher speed. Better scalability. 6/ Then AWS entered the picture. AWS now lets developers charge AI traffic at the edge. AI requests data. A payment request appears. Payment is verified. Access is granted. That's programmable commerce for AI. 7/ But Cloudflare's announcement changed everything. Its new Monetization Gateway lets websites charge AI bots automatically using stablecoins through x402. That could fundamentally change how the internet gets paid. 8/ Here's the problem it's trying to solve... AI bots read billions of web pages. Publishers still pay hosting costs... ...but receive zero advertising revenue because bots don't click ads. The current model is broken. 9/ Cloudflare's answer is simple. If an AI agent consumes your content... It pays. No subscriptions. No invoices. Just instant programmable payments. 10/ Cloudflare powers roughly 20% of the web. If even a fraction of those websites adopt this model... x402 transaction volume could explode. 11/ There is still one major challenge. Scale. Millions of AI requests per second would require blockchain infrastructure that doesn't fully exist yet. The payment rails must continue evolving. 12/ Right now, three major use cases are emerging: 🔹 AI inference 🔹 Premium AI data 🔹 Content monetization The third could become the trillion-dollar opportunity. 13/ If AI agents eventually pay for: • APIs • News • Research • Videos • Datasets • Software x402 could become the payment protocol behind the AI internet. 14/ We're still early. Most people are watching token prices. The smarter investors are watching infrastructure. That's usually where the biggest opportunities begin. 15/ The next wave of crypto won't just be about finance. It will be about AI paying AI. And x402 is positioning itself right in the middle of that future. Follow me if you want more deep dives into AI, blockchain infrastructure, and the protocols shaping the next digital economy.

• 
  ¿kofo? (@kofookesola) reported 56 minutes ago

  Cloudflare is down keh?

• 
  Yepsurethatsme (@yepsurethatsme) reported 1 hour ago

  Why is the @Cloudflare support bot so bad? It is so limited and it is broken in ways that just waste the user's time.