Unstable DNS in Brazil (again)

https://cdn.jesteriruka.dev/vehicles/panto.png ^ R2 Bucket, timeout every single time. When the same URL is requested through OVH (United States), the requested file is downloaded just fine. For some reason, other projects (with Pro plan) don't seem to be affected. My ISP is Vivo (Telefonica Brasil), a lot of my customers are talking about this, there is also a considerable amount of reports on https://downdetector.com.br/fora-do-ar/cloudflare/
No description
No description
7 Replies
JesterIruka
JesterIrukaOP3d ago
For context: storage.hydrus.gg is also a R2 bucket, but it works. Seems to be solved now, at least for my ISP.
JesterIruka
JesterIrukaOP3d ago
No description
JesterIruka
JesterIrukaOP3d ago
Yes, I also forgot to say this, but jesteriruka.dev has ipv6 disabled. But wasn't only my computer, I provide some sort of SaaS for gta scripting, and a lot of customers had the same connectivity issue with my domain. Maybe that is the reason why other zones didn't had the same issue
Chaika
Chaika3d ago
a good reason to enable IPv6 perhaps, could have been an ISP-wide issue. If it happens again, traceroutes (tracert on windows) are helpful
JesterIruka
JesterIrukaOP3d ago
I did one but didn't sent it.
Tracing route to cdn.jesteriruka.dev [104.21.48.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms GPT-2741GNAC-N2.GPT-2741GNAC-N2 [192.168.15.1]
2 3 ms 1 ms 6 ms 187-11-87-14.dsl.telesp.net.br [187.11.87.14]
3 3 ms 3 ms 3 ms 201-1-224-64.dsl.telesp.net.br [201.1.224.64]
4 4 ms 4 ms 3 ms 187-100-166-54.dsl.telesp.net.br [187.100.166.54]
5 * * 3 ms 152-255-190-68.user.vivozap.com.br [152.255.190.68]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * 11 ms 104.21.48.1
Tracing route to cdn.jesteriruka.dev [104.21.48.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms GPT-2741GNAC-N2.GPT-2741GNAC-N2 [192.168.15.1]
2 3 ms 1 ms 6 ms 187-11-87-14.dsl.telesp.net.br [187.11.87.14]
3 3 ms 3 ms 3 ms 201-1-224-64.dsl.telesp.net.br [201.1.224.64]
4 4 ms 4 ms 3 ms 187-100-166-54.dsl.telesp.net.br [187.100.166.54]
5 * * 3 ms 152-255-190-68.user.vivozap.com.br [152.255.190.68]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * 11 ms 104.21.48.1
Unfortunately I'm not sure if I can enable ipv6 without major issues, there is a lot of tokens that are assigned to ipv4, which will break the authentication, maybe is best to just leave this specific area to another A record without cloudflare proxy.
Chaika
Chaika3d ago
hmm, that looks like it was from when it was working since you reached the ip in the end
JesterIruka
JesterIrukaOP3d ago
I did before the successful ping, but probably took long enough to just work.

Did you find this page helpful?