Issues with homebrew.github.io - timeouts

[Eamonn-OL]

Output of brew config

HOMEBREW_VERSION: 4.3.2-68-ge130e47
ORIGIN: https://github.com/Homebrew/brew
HEAD: e130e47f23b8b806096f9ec4f2c193213b8ec908
Last commit: 14 hours ago
Core tap JSON: 03 Jun 11:25 UTC
Core cask tap JSON: 03 Jun 11:25 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
HOMEBREW_SORBET_RUNTIME: set
Homebrew Ruby: 3.3.2 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.2/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 15.0.0 build 1500
Git: 2.45.1 => /opt/homebrew/bin/git
Curl: 8.6.0 => /usr/bin/curl
macOS: 14.5-arm64
CLT: 15.3.0.0.1.1708646388
Xcode: N/A
Rosetta 2: false

Output of brew doctor

Your system is ready to brew.

Description of issue

Trying to run brew install kubent and the process hanged for over 10 minutes while running the update step.

Adjusting to use --verbose, I saw issues hitting https://formulae.brew.sh/api/formula.jws.json.

Trying to ping formulae.brew.sh I get the following error:

ping formulae.brew.sh
PING homebrew.github.io (185.199.108.153): 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
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

I jumped on VPN and was able to ping successfully:

PING homebrew.github.io (185.199.109.153): 56 data bytes
64 bytes from 185.199.109.153: icmp_seq=0 ttl=57 time=46.800 ms
64 bytes from 185.199.109.153: icmp_seq=1 ttl=57 time=46.188 ms
64 bytes from 185.199.109.153: icmp_seq=2 ttl=57 time=39.252 ms

Despite the IP change, I was able to ping both IP's on VPN, and neither off-vpn.

I'm based in the UK using EE/BT Broadband - posting it here incase it's more widespread than "just me", but the VPN worked around the issue at least.

[dale-satvu]

Also on BT/EE and It's happening to me too.

[Eamonn-OL]

Traceroute looks like it's stopping at BT/EE:

traceroute formulae.brew.sh
traceroute: Warning: formulae.brew.sh has multiple addresses; using 185.199.109.153
traceroute to homebrew.github.io (185.199.109.153), 64 hops max, 40 byte packets
 1  192.168.68.1 (192.168.68.1)  9.941 ms  2.964 ms  4.704 ms
 2  * * *
 3  * * *
 4  31.55.185.184 (31.55.185.184)  16.537 ms  17.053 ms
    31.55.185.188 (31.55.185.188)  24.620 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *

Looking up that IP it's one of BT/EE's cores:

traceroute formulae.brew.sh
traceroute: Warning: formulae.brew.sh has multiple addresses; using 185.199.109.153
traceroute to homebrew.github.io (185.199.109.153), 64 hops max, 40 byte packets
 1  192.168.68.1 (192.168.68.1)  9.941 ms  2.964 ms  4.704 ms
 2  * * *
 3  * * *
 4  31.55.185.184 (31.55.185.184)  16.537 ms  17.053 ms
    31.55.185.188 (31.55.185.188)  24.620 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *

I've reached out to their peering to see if they can investigate - it can be pretty hit and miss on whether they investigate or dismiss as an individual issue. I'll update if I hear anything back!

[forxinrange]

Same for me, UK + BT ISP

FWIW earler today I connected to a vpn (mullvad) and selected a node in the UK, this had the same connection issues. I've just tested that same node and it is now working.

Still the same issues without VPN however.

[Eamonn-OL]

In the past 30 minutes or so this issue has cleared up for me - no ack from BT/EE yet, but I did get talking to someone yesterday who at least said they'd take a look at it, so hopefully that's us sorted!

traceroute formulae.brew.sh
traceroute: Warning: formulae.brew.sh has multiple addresses; using 185.199.109.153
traceroute to homebrew.github.io (185.199.109.153), 64 hops max, 40 byte packets
 1  192.168.68.1 (192.168.68.1)  8.234 ms  2.669 ms  3.136 ms
 2  * * *
 3  * * *
 4  31.55.185.184 (31.55.185.184)  20.039 ms  27.681 ms
    31.55.185.188 (31.55.185.188)  21.088 ms
 5  core1-hu0-12-0-1.colindale.ukcore.bt.net (195.99.127.214)  21.541 ms
    core2-hu0-6-0-6.colindale.ukcore.bt.net (213.121.192.24)  19.645 ms
    core2-hu0-2-0-5.colindale.ukcore.bt.net (195.99.127.116)  19.621 ms
 6  peer7-et-4-1-1.telehouse.ukcore.bt.net (194.72.16.134)  21.731 ms
    peer7-et-3-1-7.telehouse.ukcore.bt.net (109.159.252.172)  20.522 ms
    peer8-et-3-1-7.telehouse.ukcore.bt.net (194.72.16.150)  20.155 ms
 7  transit1-xe-000.telehouse.ukcore.bt.net (194.72.16.177)  19.293 ms  21.553 ms  33.374 ms
 8  166-49-214-166.gia.bt.net (166.49.214.166)  22.026 ms
    166-49-214-192.gia.bt.net (166.49.214.192)  23.676 ms  22.371 ms
 9  149.3.183.150 (149.3.183.150)  30.595 ms  20.659 ms
    ldn-b3-link.ip.twelve99.net (213.248.71.146)  27.303 ms
10  * ae0.milano62.mil.seabone.net (93.186.128.57)  53.898 ms
    ae1.milano62.mil.seabone.net (93.186.128.107)  50.181 ms

Edit: Just got a reply from BT's peering confirming there was an issue blackholing traffic which should now be resolved! :-)

[forxinrange]

All good for me now also! Glad this was resolved quickly.