https://pantsbuild.org/ logo
Join Slack
Powered by
hey team, just to confirm are Pants site still com...
# general
b
hey team, just to confirm are Pants site still completely off for Brazil? There is no ETA on solving that?
f
The Pants team consists of volunteer open source maintainers and are not a single organization. Speaking for myself, I am not in a position to solve networking problems which are entirely out of my control; other maintainers likely have similar views. Moreover, I just tested accessing pantsbuild.org with my VPN set to Brazil and I was able to access it just fine. As this point, the issue is likely with your own Internet Service Providers in Brazil. Maybe just work through your ISPs' support system to ask them to fix the routing of your traffic?
b
@fast-nail-55400 I will check with my ISP, but I highly doubt that is the issue, since other people I know that also use Pants are facing similar issues with different ISPs
in any case, I also have little networking knowledge to even understand what needs to be done in order to solve it. The only thing I probably can contribute is both in testing and sharing details about the problem For reference, here is the 
traceroute
output:
Copy code
❯ traceroute <http://pantsbuild.org|pantsbuild.org>
traceroute to <http://pantsbuild.org|pantsbuild.org> (104.26.13.102), 30 hops max, 60 byte packets
 1  172.22.32.1 (172.22.32.1)  0.306 ms  0.291 ms  0.287 ms
 2  172.16.0.1 (172.16.0.1)  2.927 ms  2.912 ms  2.908 ms
 3  <http://152-244-26-1.user.vivozap.com.br|152-244-26-1.user.vivozap.com.br> (152.244.26.1)  4.826 ms  4.823 ms  4.819 ms
 4  <http://201-1-224-2.dsl.telesp.net.br|201-1-224-2.dsl.telesp.net.br> (201.1.224.2)  4.863 ms  4.859 ms <http://201-1-224-0.dsl.telesp.net.br|201-1-224-0.dsl.telesp.net.br> (201.1.224.0)  4.856 ms
 5  <http://152-255-212-117.user.vivozap.com.br|152-255-212-117.user.vivozap.com.br> (152.255.212.117)  1426.661 ms  1426.640 ms  1426.637 ms
 6  <http://187-100-168-128.dsl.telesp.net.br|187-100-168-128.dsl.telesp.net.br> (187.100.168.128)  333.570 ms  148.447 ms  148.435 ms
 7  <http://187-100-168-137.dsl.telesp.net.br|187-100-168-137.dsl.telesp.net.br> (187.100.168.137)  148.440 ms * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
f
I will check with my ISP, but I highly doubt that is the issue, since other people I know that also use Pants are facing similar issues with different ISPs
Why do you doubt that network routing problems is the issue? Given the discussion in this thread https://pantsbuild.slack.com/archives/C046T6T9U/p1721063822002629, my educated guess is that this issue is an ongoing consequence of the Cloudflare BGP route leaks discussed in that thread. Your ISP's network engineers will likely need to talk to the operations people at their peers and upstreams to make sure that the routing tables in their core routers actually have the correct routes.
Given the traceroute hangs at telesp.net.br, I suggest asking your ISP to contact Telesp's operations staff.
b
I'll ask them, I mentioned this because many different developers reported the same issues, and when I asked them they all use different ISPs
in any case, I'll contact my ISP
@fast-nail-55400 I mean, no site other than Pants is having any issues, and the people who tested it all use different ISPs. So, it is high unlikely the ISP being the issue 🙂 in any case, I'll contact them
f
> So, it is high unlikely the ISP being the issue My guess is that the issue is in the Internet "backbone" ISP like Telsp (given the traceroute you provided) and not any user's direct ISP. Those direct ISPs will likely route their traffic via Telsp and will have a peering/upstream relationship with them. But between you living in Brazil and me living in the US, which one of us has the better chance of convincing an "indirect" ISP in Brazil to fix its network?
I submit not me.
many different developers reported the same issues, and when I asked them they all use different ISPs
as another data point, I set my VPN to Brazil and still could access pantsbuild.org when I reloaded
> will likely route their traffic via Telsp and will have a peering/upstream relationship with them It would be interesting for all affected users to run traceroute, and then we could see if we any single backbone ISP stands out as the problem.
b
@fast-nail-55400 are you able to set a specific city? If so, can you test São Paulo please? in any case, I've sent a message to my ISP with the traceroute, the link to Cloudflare's blog post, and also mentioning the issue with Telsp
thanks for your help 🙏
f
I checked again and was able to still connect to pantsbuild.org when on VPN (and I confirmed my VPN server was in Sao Paulo). I also ran traceroute and relevant intermediate routers include vl201.sao-eq4-core-1.cdn77.com, vl250.sao-eq4-core-2.cdn77.com, and as13335.saopaulo.sp.ix.br.
w
To @fast-nail-55400 ‘s point, we can’t really know anything other than: Pants is not setup to block a subset of IPs in Brazil. That’s probably as far as any of us can take it. I’ve also set my VPN to Brazil, one time it was blocked, another time it worked. Some users here from Brazil seem to be blocked, while others are not, and a given user who was blocked from certain computers was unblocked on mobile 🤷 That does feel like certain routes or providers, and based on a very small amount of info - it did also very, very, very loosely and anecdotally correlate to where Cloudflare was showing re-routed data centres in Brazil
As far as mitigation, as I wrote in the other thread I think, Pantsbuild.org is only really “required” to download the install script, but basically everything happens from GitHub - so you can use GitHub releases directly. And the docs are also generated from Github docs
h
I will file a customer support ticket with Cloudflare, in case they can address proactively on their end
Done
fingers crossed
🤞 1
Folks in Brazil, is this still happening? cc @breezy-pizza-55668
b
@happy-kitchen-89482 yes, it is still happening
unfortunately I can only access Pants website using a VPN. I already spoke with my ISP and they informed everything is working as expected on their side, and that this is a problem with the site, not their infrastructure
and, honestly, it really seems to be that. No other site is suffering from that, pantsbuild.org is the only site I can't access
h
I’ve opened a ticket with Cloudflare, but not heard anything back yet
it’s been a couple of weeks
I can’t think what else it can be, since the actual hosting is just github pages
w
I just tried a traceroute and saw this: 
traceroute: Warning: <http://pantsbuild.org|pantsbuild.org> has multiple addresses; using 172.67.72.231
That feels weird. Though, if it were a problem, my assumption is that it would affect everyone - but it is strange
😕 1
b
both with and without 
www
has the same effect @happy-kitchen-89482
10 Views
Open in Slack
PreviousNext
Powered by