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:

• 
  Paul Michael (@paulmichaeldev) reported 1 minute ago

  @iuditg That's not an SSL expiry, that's an SSL misconfiguration. It's also Atlassian's problem, not Anthropic. I've read your replies and I get your frustration, but how do you deal with a 3rd party dropping the ball with one of your startups? And do you blame all of the individual companies when CloudFlare shits itself causing half of the Internet to go down?

• 
  Chan Walrus (@chanwalrus) reported 2 minutes ago

  @kidariseyogt @NamecheapCEO @Cloudflare I've had some hideous problems with Cloudflare in the past to the point where if I see a captcha, I just close a site. Probably best not to get into it here as my GOD... I have a LOT of work to do today. XD

• 
  🌱Thionne (@Thionne_WTZ) reported 3 minutes ago

  The agent economy is coming and with it, AI agents will increasingly rely on protocols like x402 to make autonomous payments. But who will protect those agents from wallet drainers, malicious contracts, and other Web3 threats? RootCrak is building the security infrastructure for this new economy. Our technology continuously protects users today, and soon, AI agents will have the same layer of protection. Autonomous agents need autonomous security. @base @Cloudflare we are here to help.

• 
  Gregory (@_studable_) reported 6 minutes ago

  just got my cloudflare bill and it's over $17, so i will be hereby shutting down gexx

• 
  hexmint ✌️ (@hexmint) reported 7 minutes ago

  @Cloudflare you really need to QA this Create Worker page. If I enter two letters in any of the text boxes here, the first letter is lost. And if there is a single letter there, I need to press backspace twice to delete it. Feels like a React issue idk

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

  Tomorrow.... i will post up some power videos.... Been working on the websites for 2 days... think i have some issues with cloudflare to sort out. Page times out and takes a while to reload sometimes. gotta look into that....

• 
  Jakob (@jakob_btc) reported 9 minutes ago

  1. google cloud just set 2029 as its target for full post-quantum readiness 2. google has already protected its own internal communications with PQC since 2022 3. microsoft wants its products and services transitioned by 2033 4. apple already runs quantum-safe encryption in imessage for every iphone 5. signal already runs quantum-safe key agreement 6. cloudflare has been running post-quantum key exchange since 2022 7. AWS is now rolling PQC into core infrastructure 8. the white house already ordered federal agencies to migrate to PQC by 2030 9. UK told organizations to plan for complete PQC migration by 2035 10. the NSA set the deadline for full PQC migration as 2035 is there something they know that we don't know?

• 
  Jon raRaRa (@jon_raRaRa) reported 9 minutes ago

  @rrespectorr @Cloudflare @fct_pt Damn not good! Wondering if I should make one for 2027 🤔

• 
  Aaron Boodman (@aboodman) reported 9 minutes ago

  Think of DOs by analogy to a serverless function. A better (and much funnier) name might have been "serverless objects". A "serverless function" is a stateless javascript program you upload to, say, Vercel. The external interface is a function. It is reachable at a URL. You send a request to the URL, Vercel instantaites your program, sends the exported function the request, gets the function result, send the result to you as an HTTP response, then destroys the program. DOs are exact same thing, but stateful. You upload a JavaScript program to CloudFlare. The external interface is a *class*, not a function. DOs are reachable at a URL. You send a request to the URL and CloudFlare invokes your program, instantiates your class, and sends a particular method on the class the request, gets the result, and send it to you as an HTTP response. So far, just a more complicated version of serverless functions. The difference is that CF keeps that class running for awhile. If another request comes into same URL, CF routes it to the same running program and the same exact JavaScript object in memory. So you can keep state in that JS objects across invocations. That's it, that's the whole pitch. These little javascript programs are low-power (last I looked max ram was maybe 1GB?). But they are cheap to run so you can have zillions of them. This makes them a very useful primitive for certain kinds of problems, like say chatrooms, multiplayer games, etc.

• 
  Joel - coffee/acc (@JoelDeTeves) reported 16 minutes ago

  How does @Cloudflare not have an SPF flattening service built in yet? They already have one of the best DMARC solutions. And everyone loves Cloudflare DNS. Wouldn't this be a match made in heaven? PS - Cloudflare, I am available to hire as your idea guy. $300k / year USD.

• 
  Dylan Garcia (@_dylanga) reported 16 minutes ago

  @VicVijayakumar @Cloudflare I'm 100% sure that if my instance were to go down right now I would have no clue how to get it back up and running. I was looking at my deployments notes from back then and it involves deprecated docker-machine, a docker network on the host, etc. Just a pain. Cya!

• 
  Joseph Lorenzo Hall, PhD (@JoeBeOne) reported 20 minutes ago

  The archive is public, so this isn’t a “harvest now, decrypt later” use case (no secrets!). It is a useful real-world compatibility test. I’d love to see Backblaze add PQ key exchange support to B2 so Cloudflare-to-origin connections can use it without falling back to X25519. 6/6

• 
  Chris McGimpsey-Jones 🏴‍☠️👻 (@cipheranarchist) reported 24 minutes ago

  @Jimwatkins @Cloudflare @POTUS The problem at Cloudflare is (and always has been) Matthew Prince.

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

  WOOO!!! i fixed it!!! Website is back up!!!!1 Had a DNS issue switching over to Cloudflare... Can't fix the email until the nameservers propagate though.... lame...

• 
  kidariseyo (@kidariseyogt) reported 28 minutes ago

  @chanwalrus @NamecheapCEO At this point if you are serious about hosting, use a domain provider like @Cloudflare I moved services that where in NC to CF workers as most of others apps hitted NC endpoint to send data. a CF worker matching exact down url saved the day, staying in CF.