by rwky on 2/12/23, 1:16 AM with 13 comments
by adrienjarthon on 2/12/23, 10:12 PM
Sorry about this, I still don't have any answer or explanation from Vultr or CloudFlare at this point. Most likely cause IMO is that CloudFlare (accidentally?) blocked one or many big ranges of IPs belonging to Vultr (and maybe some other providers as people seems to say Vultr was not the only impacted). I noticed during the incident this morning for example that I could ping CloudFlare IPv6 (ICMP) but not connect through TCP (port 443). So this sounds more like a firewall than a routing issue from what I could see.
I'll update once I have anything else in https://status.updown.io/issue/1e196616-1368-43a0-8c04-82cff.... For the moment I'm keeping the mitigation in place just in case.
If you have more details about this from CloudFlare or elsewhere I'll be happy to hear it :)
by palmeida on 2/12/23, 11:12 AM
by johnny81 on 2/12/23, 9:23 PM
by ammmir on 2/12/23, 1:32 AM
by bbu on 2/12/23, 6:47 AM
by luisrudge on 2/12/23, 7:11 AM