New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Cloudflare is not the internet.
*is down
Could this be the reason why SCALEWAY DOESN'T WORK?
Works for me, tried querying one of my domains directly from their nameserver.
Mine seems to be working.
It works fine for me, no idea if someone has/had issues reaching metadedi.net try metadedi.ru which runs on non cloudflare dns servers.
Only for you..
For me it works too. Maybe Cloud%§&" got their stuff fixed by now.
Mine started working some minutes ago, the control panel was unresponsive and i couldn't reach the vps
Works, Fake news.
You did not just ping a DNS server instead of checking if it really replies to requests?
all day, I am browsing, via Cloudflare DNS
The question was whether you seriously "checked" a name server by pinging.
Judging by the sub 1ms latency I think he's checking anything but CloudFlare DNS.
Hamachi virtual interface?
Not if he's using a VPS in same city as Cloudflare datacenter. My Seattle VPS'S all have sub 1ms pings to the major DNS providers.
Ping is NOT DNS.
@wss is not DNS
GNU is not Windows and WINE is an emulator.
Let's see if i survive this.
Join us now and break the software;
You'll be free, microsoft, you'll be free.
Join us now and break the software;
You'll be free, microsoft, you'll be free.
Hookers can get piles of money,
That is true, Bongo, that is true.
But they cannot eat fungus off their feet;
That's not good, Bongo, that's not good.
...edited
Impacted only some users, event timeline here:
https://www.cloudflarestatus.com/incidents/xwz0zft74d12
That's certainly a home computer. I see Windows 7 Aero UI.
I smell conspiracy. Probably involved google.
They setup a KVM on the DNS servers just to give it a reliable ping time.
I think it was a conspiracy for us all to switch to 1.1.1.1 as a resolver instead of 8.8.8.8, so everything would work again, ASAP. Now people are too lazy to switch back.
All of this could've been avoided, had people been using TempleOS.