100% packet loss on vultr Sao Paulo, Brazil

NextDNS Sure!

Here is the diag:

https://nextdns.io/diag/b2b65340-3022-11f0-afb1-299b6374c0e5

My ISP (TIM) blocks traceroute on their network, which is why their hops are missing.

I would also like to add that the IP 45.90.30.0 is the only one responsive, and that is why it showed up in the diagnostic tool. This is the only IP in the range 45.90.30.0/24 tested by the tool.

IPs from 45.90.30.1 to 45.90.30.254 are not responding to pings or DNS requests. This behavior can also be seen on Vultr's looking glass (https://sao-br-ping.vultr.com), suggesting there is an issue in their network.

As far as I understand, clients are instructed to use addresses from 45.90.30.1 to 45.90.30.254 on their setup page and not 45.90.30.0.

NextDNS Yes, very unusual.

Have you tried contacting Vultr to see why this is happening? The drops seem to be occurring on their network.

If not, what do you think the next move is?

I would appreciate it if you could keep me posted.

NextDNS Because they are the last network on the path before it reaches IPs 45.90.30.0–255 in São Paulo, and they are also dropping the same packets I observed with my ISP.

Just look at the screenshots from Vultr’s Looking Glass above, or try it yourself: https://sao-br-ping.vultr.com.

A Looking Glass is a network debugging tool hosted by major networks — in this case, hosted by Vultr — to help understand how traffic is flowing. It provides basic tools like ping and traceroute from various locations within Vultr's network.

So, if packets are being dropped within Vultr’s network, any ISP that gets routed through them will exhibit the same behavior. This is exactly what I’m seeing with my home ISP (TIM), my mobile ISP (Vivo — I can run another diagnostic if you'd like, but it shows more of the same), as well as in Looking Glass results from NTT America and Cogent, both of which are also routed through Vultr in São Paulo.