Unable to access resolvers since Sunday

Hi there,

It seems something changed in the early hours of Sunday morning (my guess is around 8am PDT). Since this time I have been unable to access the any cast resolvers at:

45.90.28.38

45.90.30.38

Running a trace route I am seeing it fail in Seattle:
 

jakevis@M3Space ~ % traceroute 45.90.28.38
traceroute to 45.90.28.38 (45.90.28.38), 64 hops max, 40 byte packets
1 192.168.68.1 (192.168.68.1) 13.781 ms 15.072 ms 4.705 ms
2 core.ifibertv.com (208.84.220.1) 5.156 ms 5.754 ms 9.819 ms
3 est-rtr-ifbr-core1.est-rtr-ifbr-edge1.ifiber.com (208.84.220.193) 6.267 ms 4.920 ms 5.884 ms
4 cr1-ewncwaem-hu-0-0-1-0.bb.as20055.net (107.191.238.38) 5.827 ms 6.181 ms 6.696 ms
5 lr1-ewncwa06-b-be-12.bb.as20055.net (204.11.67.141) 11.507 ms 21.704 ms 22.392 ms
6 lr1-wntcwaxx-a-be-19.bb.as20055.net (64.52.96.81) 11.376 ms 23.616 ms 11.786 ms
7 lr1-elbgwa01-b-be-14.bb.as20055.net (204.11.66.178) 12.002 ms 21.943 ms 11.008 ms
8 lr1-elbgwa01-a-be-11.bb.as20055.net (204.11.65.226) 10.795 ms 12.277 ms 13.268 ms
9 prm1-sttlwawb-a-be-12.bb.as20055.net (204.11.64.142) 9.880 ms 27.003 ms 22.720 ms
10 * * *
11 six-a.sea2.constant.com (206.81.81.66) 310.955 ms 25.047 ms 18.289 ms
12 * * *
13 * * *
14 * * *
15 * * *

This is also happening for the test endpoints / much of the diag test script endpoints as well.

As a side note- my local ISP (ifiber) was recently procured by ziply - and while I would love to blame it on them, I do have a public ip, and it is fully accessible for everywhere ping.sx can check, so I dont think its an asymmetric routing issue to me. The Traceroutes seem to exit ziply (as20055) and then get 1 more hope and die.

I had kinda went all in with nextDNS and DoH... but unfortunately this has broken everything; including my DNS over Tailscale stuff.  I have a pro account if that matters.

Any way someone can get the upstream providers to look at this?  Happy to DM my public IP.

Diag results bellow-- they failed to upload..
 

jakevis@M3Space ~ % sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'
Welcome to NextDNS network diagnostic tool.
This tool will download a small binary to capture latency and routing information
regarding the connectivity of your network with NextDNS. In order to perform a
traceroute, root permission is required. You may therefore be asked to provide
your password for sudo.
The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Resolvers: 1.1.1.1
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": dial tcp 149.248.36.234:443: i/o timeout
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 149.248.36.234:443: connect: operation timed out
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 170.39.227.247:443: connect: operation timed out
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connect: operation timed out
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.30.0:443: connect: operation timed out
Pinging PoPs
cacloud-yvr: 16.363ms
anexia-yvr: 16.641ms
directspace-pdx: 37.396ms
tier-pdx: 35.655ms
xmission-slc: 53.84ms
zepto-sjc: 53.588ms
bronto-slc: 54.109ms
vultr-sjc: 35.69ms
Traceroute for ultra low latency primary IPv4 (149.248.36.234)
1 192.168.68.1 38ms 18ms 11ms
2 208.84.220.1 27ms 44ms 24ms
3 208.84.220.193 9ms 9ms 7ms
4 107.191.238.38 7ms 6ms 40ms
5 204.11.67.141 16ms 14ms 10ms
6 64.52.96.81 15ms 26ms 27ms
7 204.11.66.178 14ms 13ms 15ms
8 204.11.65.226 27ms 17ms 12ms
9 204.11.64.142 12ms 33ms 29ms
10 * * *
11 206.81.81.66 21ms 12ms 28ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Traceroute for ultra low latency secondary IPv4 (170.39.227.247)
1 192.168.68.1 8ms 12ms 6ms
2 208.84.220.1 10ms 37ms 8ms
3 208.84.220.193 12ms 4ms 9ms
4 107.191.238.38 11ms 10ms 5ms
5 204.11.67.141 51ms 13ms 10ms
6 64.52.96.81 16ms 13ms 49ms
7 204.11.66.178 16ms 12ms 11ms
8 204.11.65.226 11ms 23ms 26ms
9 204.11.64.142 14ms 10ms 22ms
10 * * *
11 206.81.81.161 27ms 15ms 16ms
12 170.39.227.9 16ms 10ms 22ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Traceroute for anycast primary IPv4 (45.90.28.0)
1 192.168.68.1 32ms 7ms 6ms
2 208.84.220.1 13ms 12ms 14ms
3 208.84.220.193 20ms 20ms 6ms
4 107.191.238.38 8ms 5ms 4ms
5 204.11.67.141 16ms 11ms 22ms
6 64.52.96.81 34ms 12ms 61ms
7 204.11.66.178 30ms 11ms 12ms
8 204.11.65.226 24ms 42ms 9ms
9 204.11.64.142 11ms 13ms 10ms
10 * * *
11 206.81.81.66 37ms 10ms 12ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Traceroute for anycast secondary IPv4 (45.90.30.0)
1 192.168.68.1 11ms 4ms 3ms
2 208.84.220.1 60ms 35ms 29ms
3 208.84.220.193 23ms 14ms 4ms
4 107.191.238.38 10ms 18ms 12ms
5 204.11.67.141 40ms 17ms 16ms
6 64.52.96.81 13ms 21ms 37ms
7 204.11.66.178 16ms 13ms 11ms
8 204.11.65.226 12ms 24ms 71ms
9 204.11.64.142 14ms 63ms 16ms
10 * * *
11 206.81.81.161 25ms 23ms 16ms
12 170.39.227.9 16ms 10ms 11ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
Do you want to send this report? [Y/n]: y
Optional email in case we need additional info:
Post unsuccessful: status 400
{"error":"0: instance.Test requires property \"Client\"\n"}%