5 ms·

So it seems... Even https://cloudflare.com/ https://cloudflare.com/ itself is down

• ratsimihah 7y ago
  So cloudflare.com runs on Cloudflare?
  • dexen 7y ago
    Turtles all the way down. But in all frankness, if Cloudflare's own site did not run off of Cloudflare's infrastructure, why would anybody trust them with their websites?
    • beckingz 7y ago
      Ironic isn't it.
  • OskarS 7y ago
    Certainly what I would use if I was building cloudflare.com...
  • kreetx 7y ago
    For the site itself that's totally fine, and the status page is separate as it should be, too.
    • ratsimihah 7y ago
      Fair. Some service recently had their status page hosted on the same server that went down, that was funny.
      • apple4ever 7y ago
        Discord's status page is also down haha
        • auscompgeek 7y ago
          I'm quite surprised Discord's status page is behind Cloudflare. I thought they were using statuspage.io.
          • theoctopus 7y ago
            They are, but that subdomain is proxied through Cloudflare. If they'd set it to just DNS then it would have still worked.
      • kreetx 7y ago
        I guess it's like diversifying one's assets - you put your status page elsewhere than on your own infrastructure.
      • wilsonfromdevon 7y ago
        Down detectors down lol.
    • ht85 7y ago
      This is fine-ish... In case of network issues affecting their proxy, being able to change your configuration to allow direct traffic would be really nice.
      • deleted 7y ago
        [deleted]
• uncoder0 7y ago
  Yep, I'm seeing 502's all over the web as of a few minutes ago.
• steelaz 7y ago
  Great, now we can't even disable HTTP proxy to allow traffic directly to AWS :/
  • PudgePacket 7y ago
    Point your DNS back to your actual host? Might be the only short term solution, though DNS propagation times kinda rule that out :/
    • cj 7y ago
      That's a no-go if you transferred your domains to Cloudflare Registrar.
      • PudgePacket 7y ago
        Something something all your eggs in one basket :)
        • Gigablah 7y ago
          Seems like even other registrars might rely on Cloudflare (e.g. Namecheap) so now people have to continuously ensure there’s no cross-pollination between their infra providers...
    • steelaz 7y ago
      I think the only option here would be to change our name servers at registrar level to point to AWS and recreate all DNS records there, but then you have to deal with name server propagation.
• btown 7y ago
  More importantly, their admin dashboard is down. It's impossible to bypass their "orange cloud" proxies and send traffic directly to our hosting. That they can't flip a switch and have their nameservers send dash.cloudflare.com to a separate piece of redundant infrastructure is mind-boggling.
  • ilogik 7y ago
    change the nameserver at the registrar to someone else
    • skrowl 7y ago
      By the time that change propagates, cloudflare will be backup
      • skywhopper 7y ago
        Yes, but then next time you will be able to control your DNS.
        • scaryclam 7y ago
          Though, only if you're using a short TTL. I'm not arguing against your position in general though.
  • cj 7y ago
    Agreed. First thing I tried to do was login Cloudflare to disable proxying. But can't.
  • duijf 7y ago
    We were able to flip this switch on our services through their API, as we have our Cloudflare config in Terraform. The API wasn't working perfectly, but with some retries we were able to change the config for our domains.
• haneefmubarak 7y ago
  EDIT: the static pages load but trying to log in just times out. I think the static cache is back up but the rest of it is still down. Seems to be back up and running for me.
• jgrahamc 7y ago
  We use our own service.