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.

• Cloud Services (43%)
• Domains (21%)
• Hosting (21%)
• E-mail (7%)
• Web Tools (7%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	2 days ago
New York City	Cloud Services	20 days ago
Los Angeles	Cloud Services	22 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	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:

• 
  TheDataBunny (Darth Bunny) (@thedatabunny) reported 5 minutes ago

  What would you do if cloudflare and AWS was down for a week?

• 
  @tobeycodes (@tobeycodes) reported 5 minutes ago

  anyone having issues with gitCheckout in cloudflare sandboxes today? seems to always timeout and can never close. it was working fine before today

• 
  Lootera Sandy (@chanduwin567) reported 6 minutes ago

  @MaekusMikolous I setup but still not working, cloudflare blocking everytime when I am running in terminal/

• 
  TomOnTech (@TomOnTech) reported 6 minutes ago

  AI AGENTIC PAYMENTS: The Middle Layer May Capture the Most Value AI agents are beginning to purchase data, software, computing power and services without a person initiating each transaction. Over time, agents could conduct more transactions than people, with many payments worth only a few cents or fractions of a cent. This does not necessarily mean payment processors will collect large fees. Coinbase reported more than 165 million x402 transactions but only about $50 million in cumulative volume—roughly $0.30 per transaction. The x402 protocol is also open and charges no protocol fee. If basic settlement becomes inexpensive and standardized, more value may accrue to the middle layer between the agent and the payment rail. That includes: • Identifying the agent • Confirming its permissions • Setting spending limits • Metering resource consumption • Requesting and verifying payment • Routing the transaction • Managing fraud and compliance • Granting access to the requested resource Public companies positioned around this middle layer: Cloudflare $NET Cloudflare may have the most strategically important position because it sits directly between agents and online resources. Its Monetization Gateway is designed to let an API, dataset, webpage or AI tool require payment before providing access. Cloudflare can potentially handle the payment request, usage metering, verification and access decision at the edge. Cloudflare Wallets could also give agents programmable spending limits, approved merchants and maximum transaction sizes. This places Cloudflare on both sides of the transaction: helping online resources collect payments and helping agents make them. The products are still early, however, and meaningful revenue has not yet been demonstrated. Coinbase $COIN Coinbase has the most developed overall agent-payment stack. It created x402, operates Base, provides agent wallets, facilitates payments and participates in USDC economics. Because x402 is open and vendor-neutral, Coinbase’s long-term opportunity is not charging a large protocol fee. It is monetizing wallets, balances, compliance, business services and activity occurring through its infrastructure. Mastercard $MA Mastercard’s potential role extends beyond processing the payment. Agent Pay for Machines is designed to manage identity, permissions and trust across cards, bank accounts and stablecoins, including high-frequency payments worth fractions of a cent. Even if settlement moves to inexpensive stablecoin networks, Mastercard could remain involved as the credentialing and risk-management layer. Visa $V Visa is developing agent scoring, tokenized credentials, fraud models, stablecoin settlement and an agent directory. Its infrastructure may be especially relevant when an agent makes a larger purchase for a person and the merchant needs to confirm that the agent is legitimate, authorized and operating within the user’s instructions. PayPal $PYPL PayPal combines merchant distribution, consumer wallets, PYUSD, fraud management and dispute resolution. Its strongest opportunity may be serving as the connection between consumer agents and merchants rather than processing sub-cent machine-to-machine payments. Circle $CRCL USDC currently dominates x402 settlement, making Circle an important part of the underlying payment rail. However, Circle primarily earns reserve income on USDC balances rather than revenue from each transaction. High transaction volume matters only if it also creates larger funded balances or demand for Circle’s paid wallet, compliance and developer services. Marqeta $MQ Marqeta can issue virtual cards with detailed spending limits and programmatic controls. This makes it a useful middle layer while agents still need to purchase from merchants that accept cards but not stablecoins. Its role may become less important if direct wallet-to-wallet payments become widely accepted. My current ranking: $NET — payment and access decisions at the internet edge $COIN — wallets, facilitation, Base and USDC economics $MA — agent identity, permissions and trust $V — credentials, fraud protection and merchant acceptance $PYPL — connection between consumer agents and merchants $CRCL — underlying stablecoin settlement $MQ — programmable card bridge

• 
  Richie Young (@Poor__Old) reported 9 minutes ago

  An underrated part of doing your own thing is all the tangential skills you learn. Just had a client from last year hit me up because their website was not showing online. Getting a "1001 error". Something about Cloudflare. Site built through carrd. Hosted on namecheap. Both renewed in the past year. Carrd reset to "offline draft". Namecheap added another DNS record. And it toggled ' on for the existing records. Carrd has its own ceriticate of security, so the toggles and extra DNS record were creating a problem. Honestly, I can't speak it the lingo exactly. But I knew the language enough to trouble shoot, find another back door tab in Carrd, and troubleshoot the problem. Site back up this morning. With a little help from the AI lords and the ability to speak(screenshot) the problem, it's all better now. Good start to the day. Especially after the little one was up from 11-2 last night!

• 
  Royce (@royce_james) reported 12 minutes ago

  @grok @bot is having issues connecting to some webpages. For instance: Grok Bot can browse Disneyland and see plans, but the Reserve page 404s before the guest picker. Root cause: the sandbox runs on a Cloudflare datacenter IP. Sites treat those like bots, so booking SPAs fail while the rest of the site loads. Phone on home Wi-Fi books the same dates with no issue. Classic residential-IP requirement. Any chance we can get Grok a residential proxy / home IP for these flows?

• 
  Artem Builds👷🏻‍♂️ (@artembuilds) reported 12 minutes ago

  @DaniellHemmati Yes, wrangler. Have been facing a lot of issues with the API token side of Cloudflare Pages lately. For now I have manually deployed it on my machine, using wrangler.

• 
  Abdur (@SyedAbdurR2hman) reported 14 minutes ago

  @opencode @Cloudflare Oh, finally the errors are now ended, they were so irritating.

• 
  Blank (@blankparticle) reported 15 minutes ago

  @benjaminshafii @alchemy_run right now it has best support for Cloudflare and AWS, Planetscale/Neon/etc are also supported, Fly Hetzner etc are being worked on, Stripe and other things are on its way

• 
  🅳ιzzιєє🕶👌🏾 (@JJDizz1L) reported 15 minutes ago

  @opencode @Cloudflare Oh, great. Sure, fix it after I finish my long 14 hour session and pushed to main.

• 
  Creed Hardcastle (@CreedHardcastle) reported 16 minutes ago

  @opencode @Cloudflare cloudflare has to jump in mid incident damn

• 
  Cyrus Radfar (@cyrusradfar) reported 17 minutes ago

  @ravikiran_dev7 the lack of any protections for customers from a company at the scale of Cloudflare is their mistake. Rate limits, rational max/scaling rules that would need to be manually overridden by the customer with understanding of the scale they expect. I'm thankful they recognized this is their mistake and they made things right.

• 
  JohnTheRevelator ✝️🥩 (@MaranathaJohn30) reported 18 minutes ago

  Is there a worse service than @Cloudflare? It's pretty much total garbage, every ******* time.

• 
  Lucia (@Lucia_6X) reported 25 minutes ago

  This week, Cloudflare rolled out a protocol called x402. It lets AI agents pay other AI agents for services, autonomously. No card. No login. No human clicking "confirm." 20+ companies are already plugged in. Combine that with agents that can now browse, book, and negotiate on their own... and you start to see where this is going. We're not far from an internet where the majority of transactions have zero humans in the loop. Wild timeline to be alive in. Are you excited or terrified?

• 
  Manish Malhotra (@algotradingdesk) reported 26 minutes ago

  Cloudflare is proving that cybersecurity is becoming an infrastructure business rather than simply a software category. The company recently crossed $2 billion in annual revenue, while its network spans more than 330 cities globally. But the more important number is the amount of internet traffic passing through infrastructure like this. As AI agents multiply, automated traffic and cyberattacks increase alongside legitimate users. That creates a structural shift. Every new AI agent becomes another potential customer. Every new attack becomes another reason to pay for protection. Cloudflare isn't merely selling security. It is positioning itself between the internet and the companies trying to operate on it. In the AI era, the companies controlling digital traffic may become as strategically important as the companies generating it.

• 
  ተገላቢጦሽ (@flippedgeo) reported 27 minutes ago

  @elithrar @Cloudflare Isn’t codemode a better solution for the quoted problem statement?

• 
  Artyom Shimanski (@a_shimanski) reported 30 minutes ago

  @kimindiehacker thanks 🙏 honestly: one post about Cloudflare went semi-viral, posts about email problems did well, and the "who are you, what are you building" ones bring the most replies. connection posts work too

• 
  Ahmet (@ahmetdotrun) reported 31 minutes ago

  two things i've been experimenting with over the last couple of days: 1) kitesurf by @Cloudflare free while in beta. i'm looking at it for (scaled) agentic offensive security work: let an agent explore an app, understand it, map the attack surface. browsers are expensive to run, hard to scale. it seems a lighter option on CF's edge, so potentially a cost effective one for me. tho, bot challenges are still a problem. 2) grok build by @SpaceXAI first time giving grok 4.6 a proper shot. faster than other frontiers and more capable than i expected. burns through the limits quicker than i'd like though.

• 
  Hassan (@thisdothassan) reported 31 minutes ago

  @rxnnie_tech @ossynoya This tissue is a different one from the Airtel issue. Cloudflare behaves this way sometimes until you use a vpn

• 
  Hareesh Vemasani (@HVemasani) reported 31 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) ProductBridge = customer support + feedback (Free) 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) Total monthly cost to run a startup: ~$20

• 
  Welldone (@welldone_tech) reported 35 minutes ago

  Cloudflare shipped WriteGuard for MCP servers: agents can read data, write operations need an explicit gate. Unrestricted tool access is the actual production risk with agents - not that the model is wrong, but that a prompt injection or a hallucination reaches a database that never should have been writable in the first place. Read/write separation for agents isn't a Cloudflare feature. It's the same principle behind every gate we put in our own process - a senior approves the spec before code exists, a different model reviews it, an engineer deploys manually. The tool doesn't get more trust than the person watching it.

• 
  Dain Bramage Entertainment ❄️ (@EOTWoffgrid) reported 35 minutes ago

  @GoDaddyHelp i know this much.... @Cloudflare has suggested whitelisting their IP ranges.... i have told this to two different support staff and they instead Cleared a cache.. and said wait a few hours..... SAME PROBLEM!! Just as site traffic is starting to pick up.... this becomes and issue.... i need it resolved ASAP one way or another. Solutions.... Let's hear them....

• 
  AI News (@ainewsusa) reported 36 minutes ago

  🚨 Breaking in AI: 💻 Cloudflare Cuts Astro Github Issues by 85% with AI Agents Here's what's happening and why it matters 🧵👇 #AICoding #GitHub

• 
  Rishabh (@crashedrishabh) reported 41 minutes ago

  Day 21 Shipped the full download backend. Users never see a GitHub link. Everything on free tiers. Serving a 108 MB installer without egress costs or serverless timeouts. That's the problem. Stack: • Next.js 14 + Bun + TypeScript • Neon Postgres + Prisma 7 • Cloudflare R2 (free egress) + Workers (edge delivery) • GitHub Releases API as source of truth Flow: sync script polls releases → upserts metadata into Postgres → installer streams from R2 via Worker → download starts directly. No 302 to GitHub. Why not proxy through Next.js? 108 MB through a serverless function = timeout risk + bandwidth bill. R2 egress is $0. Workers free up to 100k req/day. Also: AtCoder ABC 472. Solved A–E. E was a banger. @atcoder #buildinpublic @Cloudflare @nextjs

• 
  PromptKing | The Governance OS for AI Agents (@PromptKing32) reported 45 minutes ago

  @Cloudflare Optional scopes fix the consent problem. The remaining problem is independent proof that the agent actually stayed inside those scopes once it started running across systems.

• 
  Elite Web Professionals (@webproelite) reported 55 minutes ago

  AI search tools are sending customers to the wrong local businesses right now. I investigated "near me" searches across ChatGPT, Perplexity, and Google AI. Published the findings on Send2Press. Hallucinated addresses. Mixed-up business names. Real buyers routed to competitors who didn't earn the click. Cloudflare just gave site owners new controls to block AI crawlers. That conversation matters. But the bigger fire is that the AI doing the crawling can't even get your business name and location right. If your data is wrong inside the model, blocking the bot doesn't help you.

• 
  The Agentic Operator (@AgenticOperator) reported 56 minutes ago

  After auditing dozens of brands and tracking thousands of AI citations this year, these are the 10 things that actually move the needle. Not theory. Patterns from real data. Bookmark this. Come back to it. Check your brand against each one. 1. Answer the question in sentence one. AI extracts from the top and heavily weights the first 200 words. If your answer is sitting in paragraph 3 behind a brand story and a mission statement, AI moves on to the next source. The page that answers first wins. Not the page that answers best. 2. Your own website is the source AI trusts least. Third-party content gets cited 3x more than brand-owned pages. The same information on someone else's domain can carry much more weight. Guest posts. Contributed articles. Earned media. Review sites. That's where AI often looks first. Your site is confirmation. Not always the source. 3. Mentions beat backlinks. 3x stronger. Correlation between brand mentions and AI visibility: 0.664. Backlinks: 0.218. Three times the signal. 20 years of link-building strategy just got outweighed by something much simpler: Being talked about across independent sources. Being referenced matters more than being linked to. 4. Reviews on 1 platform don't count. Reviews on 5 platforms do. 4,000 reviews on your own site can look like one unverified source to AI. 340 reviews across Amazon, Trustpilot, Reddit, G2, and Google looks more like consensus from multiple independent sources. AI cares about the spread. Not just the volume. 5. Update your top pages every 2–3 weeks minimum. Pages updated within 30 days earn 3.2x more citations. AI has a freshness bias that most brands don't budget for. You don't need to rewrite the whole page. One new data point. One fresher stat. Something that signals the page is still alive. Publish and walk away, and that citation can lose value surprisingly quickly. 6. Comparison content gets cited 7x more than product pages. 59.5% of AI citations come from listicle and comparison content. Product pages account for 8.5%. The content most brands never bother writing is often the content AI cites most. Publish your own comparisons. Name competitors. Be honest about where you win and where you don't. Because if you don't write the comparison, someone else will. 7. Make sure AI crawlers can actually reach your site. 73% of businesses on Cloudflare are blocking AI crawlers by default. Check your bot protection. Check your robots.txt. Check your redirect chains. If you have more than 2–3 hops in a redirect, many AI crawlers may quit. One hop. Clean path. Open door. 8. Your price must be in raw HTML. Not JavaScript. If your price loads through a JavaScript toggle, dynamic app, or client-side rendering, AI crawlers may not see it. Right-click your product page. View source. Ctrl+F your price. If it's not there in plain text, AI may not be able to match you to price-based queries. You can be disqualified before the comparison even starts. 9. Build your entity across Wikipedia, Crunchbase, LinkedIn, and your own schema. AI needs enough signals to understand who you are and distinguish you from similarly named entities. Organization schema. sameAs links. Consistent profiles. Consistent name. Consistent description. Consistent category. Entity confusion can kill visibility before any content strategy gets a chance. 10. Track all 4 engines. Not just ChatGPT. ChatGPT dropped from 89% to 63% of AI referral share. Claude went from 1.4% to 18.5%. Gemini quadrupled. Perplexity doubled. Claude converts at 16.8%. The platform most brands have barely checked is becoming a major source of high-intent traffic. One-engine strategy is a 63% strategy. Track all four. Optimize across all four. Measure probability, not position. None of these are hacks. None are shortcuts. They're structural advantages that compound over time. The brands that nail 7 out of 10 will have a very different AI shelf than everyone else. Most brands right now aren't even close. That gap is the opportunity.

• 
  Sam Kovacs (@SamKovX) reported 56 minutes ago

  @elBacarisse Thanks this was helpful. We migrated nameservers to Cloudflare and some internet providers were still heading to Bluehost. This should self-resolve 24 hours from now due to the 48hr TTL, but I implemented a quick fix. Can you try a hard refresh and let me know if that resovles it? Thanks. Sam

• 
  Technopolis.tv (@technopolis_tv) reported 58 minutes ago

  @geerlingguy ...and then never opens (possible died behind cloudflare captcha)

• 
  Haris Sulaiman (@harisbuild) reported 1 hour ago

  @thomas_ankcorn @dillon_mulroy I don’t need to read most of the code for the majority of the products I ship. But as a customer of Cloudflare, I fully expect you to.