anycast IPv4 inaccessible

I have a really hard time accessing nextdns in the last few days as anycast is effectively dead in the water here and ultra low latency is unstable at best.

The trace usually ends at Era-IX for me, which learns the primary addresses via:

2 BGP path(s) available for 45.90.28.0/24

 via 185.1.240.204
   path 20473 34939 34939
   received 127:48:26 ago (9/27/2024, 12:10:35 PM)
   communities
       0:1239, 0:4657, 0:7713, 0:9299, 0:9505, 0:9680, 0:9924, 0:15802, 1299:5009, 1299:5669, 1299:7009, 2914:436, 2914:4013, 2914:4029, 2914:4413, 2914:4429, 2914:4613, 2914:4629, 20473:20, 20473:4000, 20473:6602, 64699:3356, 64699:15169, 65000:812, 65000:7015, 65000:7922, 65000:11351, 65000:12271, 65000:21928, 65500:4134, 65500:4837, 65500:7552
   large communities
       20473:0:3150528120, 206221:899:374 (Learned from: IMDC, AMS), 206221:901:18 (Horizon Participating: Nikhef, AMS), 206221:901:62 (Horizon Participating: Equinix AM7, AMS), 206221:901:374 (Horizon Participating: IMDC, AMS), 206221:901:13339 (Horizon Participating: 13339)

 via 185.1.240.32
   path 60068 57695 34939
   received 148:59:31 ago (9/26/2024, 2:59:30 PM)
   communities
       0:1239, 0:1276, 0:4657, 0:6939, 0:7642, 0:7713, 0:8717, 0:9009, 0:9299, 0:15802, 0:17974, 0:23947, 931:47001, 1299:5009, 1299:5669, 1299:7009, 2914:436, 2914:4013, 2914:4029, 2914:4413, 2914:4429, 2914:4613, 2914:4629, 3214:1100, 3214:1200, 3214:1400, 3214:1500, 3214:1600, 3214:2000, 3214:2100, 3214:2200, 3214:2300, 3214:2500, 3214:2600, 3214:2700, 3214:2800, 3214:2900, 3491:50100, 3491:50200, 3491:50400, 3491:50500, 6762:1090, 6762:20001, 6762:20002, 6762:20003, 6762:20004, 6762:20005, 6762:20006, 6762:20007, 6762:20008, 6762:20009, 6762:20010, 6762:20011, 6762:20012, 6762:20013, 6762:20014, 6762:20015, 6762:20016, 6762:20017, 6762:20018, 6762:20019, 6762:20020, 6762:20021, 6762:20022, 6762:20023, 6762:20024, 6762:20025, 6762:20026, 6762:20027, 6762:20028, 6762:20029, 6762:20030, 6762:20031, 6762:20032, 6762:20033, 6762:20034, 6762:20035, 6762:20036, 6762:20037, 6762:20038, 6762:20039, 6762:20040, 6762:20041, 6762:20093, 6762:20094, 6762:20095, 6762:20096, 6762:20097, 6762:20098, 6762:20099, 6762:23008, 57695:14000, 60068:203, 60068:5000, 60068:7020, 60068:20000, 60068:40020, 60068:40040, 60068:40050, 60068:40070, 60068:40080, 60068:40090, 60068:40100, 60068:40120, 60068:40160, 60068:40190, 60068:40200, 60068:40210, 60068:40260, 60068:50010, 65000:0, 65000:812, 65000:7015, 65000:7922, 65000:11351, 65000:12271, 65000:21928, 65500:7552
   large communities
       206221:0:6939 (Don't export to AS6939), 206221:0:9009 (Don't export to AS9009), 206221:899:18 (Learned from: Nikhef, AMS), 206221:901:18 (Horizon Participating: Nikhef, AMS), 206221:901:62 (Horizon Participating: Equinix AM7, AMS), 206221:901:374 (Horizon Participating: IMDC, AMS), 206221:901:13339 (Horizon Participating: 13339)

Here's how the diag looks for me:

Testing IPv6 connectivity
  available: false
Fetching https://test.nextdns.io
  status: ok
  client: 2a01:ac:xxx:yyy:zzz
  protocol: DOH
  dest IP:
  server: vultr-ams-1
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
  zepto-dub: 3.202ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
  anexia-dub: 3.205ms
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: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
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: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Pinging PoPs
  anexia-dub: 3.244ms
  zepto-dub: 3.126ms
  anexia-lon: 12.987ms
  vultr-lon: 15.851ms
  zepto-ams: 15.883ms
  zepto-ams: 16.926ms
  anexia-ams: 16.876ms
  zepto-lon: 17.656ms
  zepto-bru: 20.05ms

I'm not sure what the ipv6 availability is about. As far as https://test-ipv6.com/ is concerned, I have a 10/10 score (and I actively use ipv6).

This problem really comes and goes in waves, but when it's down it's down and the nextdns daemon can't resolve anything for the periods of 15-20 minutes, which really sucks if I'm trying to actively do something.

Any idea?