All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Anyone know what's going on with Versign DNS in Canada?
64.6.64.6 and 64.6.65.6 are both down in Canada completely.
All major peers routes are dead
Residental routing to it are dead
traceroute to 64.6.64.6 (64.6.64.6), 30 hops max, 60 byte packets
1 _gateway (10.0.30.1) 0.526 ms 0.316 ms 0.221 ms
2 * * *
3 10.199.199.1 (10.199.199.1) 0.326 ms 0.304 ms 0.380 ms
4 ae15-3323.cr4-tor1.ip4.gtt.net (69.174.8.105) 0.460 ms 0.496 ms 0.413 ms
5 ae2.cr3-tor1.ip4.gtt.net (141.136.106.30) 1.243 ms 1.096 ms 1.026 ms
6 ip4.gtt.net (198.47.103.10) 0.547 ms ip4.gtt.net (198.47.103.130) 0.810 ms 0.726 ms
7 * * *
8 * * *traceroute 64.6.64.6
traceroute to 64.6.64.6 (64.6.64.6), 64 hops max, 40 byte packets
1 10.0.2.1 (10.0.2.1) 5.937 ms 6.895 ms 2.909 ms
2 10.0.2.1 (10.0.2.1) 9.666 ms 10.285 ms 6.824 ms
3 ae22-20.tor-cor-bdr03.distributel.net (206.80.255.12) 6.370 ms 8.800 ms 7.474 ms
4 204.101.103.225 (204.101.103.225) 8.567 ms 16.731 ms 7.867 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 ix-be-9.ecore1.tnk-toronto.as6453.net (63.243.172.25) 30.200 ms 23.539 ms 50.271 ms
11 66.110.50.3 (66.110.50.3) 28.449 ms 21.077 ms 24.631 ms
12 * * *
13 * * *
14 * * *
15 * * *

Comments
I'm on my VPN to my home in BC on Shaw/Rogers. Getting 300-600ms pings but both reply.
Pings to 4.2.2.2 are saying 320ms, so VeriSign doesn't seem too bad.
Nothing on downdetector.
Traceroute also successful. Hop 14 rec1pubns1.ultradns.net
Not on .com, but .ca there are reports
https://downdetector.ca/status/verisignpublicdns/
Right, but doesn't my confirmation that I can access the server proving its the routing between you and the server and not the VeriSign server?
In other words, it's a backbone problem.
Never said it was verisign sever problem. In my first post I clearly said about the routes.
LOL, no shit. That's the whole point of the thread...
The route is back for GTT, not for residental (Bell)
My bad. I read the thread title and took that to be VeriSign DNS server and not routing to the server itself.