https://pantsbuild.org/ logo
Join Slack
Powered by
is the <https://www.pantsbuild.org/> website down?
# general
b
is the https://www.pantsbuild.org/ website down?
(it is for me)
h
I can see it
where in the world are you?
b
Brazil
h
Oh no, not this again…
We have had ongoing issues with Brazilian ISPs that are completely outside our control
If you search slack for “Brazil” you’ll get a sample
I don’t think there were any fixes though
b
Copy code
Last login: Thu Jun 26 19:28:10 on ttys006
➜  ~ ping <http://google.com|google.com>
PING <http://google.com|google.com> (142.251.135.46): 56 data bytes
64 bytes from 142.251.135.46: icmp_seq=0 ttl=118 time=5.722 ms
64 bytes from 142.251.135.46: icmp_seq=1 ttl=118 time=10.689 ms
64 bytes from 142.251.135.46: icmp_seq=2 ttl=118 time=8.159 ms
64 bytes from 142.251.135.46: icmp_seq=3 ttl=118 time=5.595 ms
^C
--- <http://google.com|google.com> ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.595/7.541/10.689/2.085 ms
➜  ~ 
➜  ~ 
➜  ~ 
➜  ~ ping <http://pantsbuild.org|pantsbuild.org>
PING <http://pantsbuild.org|pantsbuild.org> (104.26.13.102): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
^C
--- <http://pantsbuild.org|pantsbuild.org> ping statistics ---
7 packets transmitted, 0 packets received, 100.0% packet loss
➜  ~
wow, so weird
h
It’s a specific thing with cloudflare
b
just read the previous thread... wow, that's unfortunate
for future reference
Copy code
➜  ~ traceroute <http://pantsbuild.org|pantsbuild.org>
traceroute: Warning: <http://pantsbuild.org|pantsbuild.org> has multiple addresses; using 104.26.13.102
traceroute to <http://pantsbuild.org|pantsbuild.org> (104.26.13.102), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  5.282 ms  3.604 ms  2.549 ms
 2  * * *
 3  <http://201-1-229-28.dsl.telesp.net.br|201-1-229-28.dsl.telesp.net.br> (201.1.229.28)  8.287 ms
    <http://201-1-229-30.dsl.telesp.net.br|201-1-229-30.dsl.telesp.net.br> (201.1.229.30)  5.439 ms
    <http://201-1-229-28.dsl.telesp.net.br|201-1-229-28.dsl.telesp.net.br> (201.1.229.28)  9.106 ms
 4  <http://152-255-161-159.user.vivozap.com.br|152-255-161-159.user.vivozap.com.br> (152.255.161.159)  13.104 ms
    <http://152-255-161-185.user.vivozap.com.br|152-255-161-185.user.vivozap.com.br> (152.255.161.185)  11.174 ms  12.943 ms
 5  <http://152-255-212-244.user.vivozap.com.br|152-255-212-244.user.vivozap.com.br> (152.255.212.244)  12.234 ms  12.442 ms
    <http://187-100-57-12.dsl.telesp.net.br|187-100-57-12.dsl.telesp.net.br> <tel:(187.100.57.12|(187.100.57.12>)  10.962 ms
 6  <http://152-255-176-64.user.vivozap.com.br|152-255-176-64.user.vivozap.com.br> (152.255.176.64)  13.339 ms
    <http://152-255-176-62.user.vivozap.com.br|152-255-176-62.user.vivozap.com.br> (152.255.176.62)  10.974 ms
    <http://152-255-176-58.user.vivozap.com.br|152-255-176-58.user.vivozap.com.br> (152.255.176.58)  11.438 ms
 7  <http://187-100-42-60.dsl.telesp.net.br|187-100-42-60.dsl.telesp.net.br> <tel:(187.100.42.60|(187.100.42.60>)  10.301 ms  10.713 ms  10.155 ms
 8  <http://187-100-42-63.dsl.telesp.net.br|187-100-42-63.dsl.telesp.net.br> <tel:(187.100.42.63|(187.100.42.63>)  12.882 ms
    <http://187-100-42-61.dsl.telesp.net.br|187-100-42-61.dsl.telesp.net.br> <tel:(187.100.42.61|(187.100.42.61>)  10.793 ms
    <http://187-100-42-63.dsl.telesp.net.br|187-100-42-63.dsl.telesp.net.br> <tel:(187.100.42.63|(187.100.42.63>)  11.483 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
h
In the past it has gone away on its own, so fingers crossed…
🤞 1
w
I'd recommend cloning and building locally...
b
and it's back, yey
❤️ 1
3 Views
Open in Slack
PreviousNext
Powered by