| 22 Jul 2025 |
hexa (signing key rotation when) | the traceroute not completing could be a red flag | 13:01:14 |
@drupol:matrix.org | Ok... | 13:01:14 |
@drupol:matrix.org | yeah that's so weird :( | 13:01:35 |
@drupol:matrix.org | I have that thing running for now 30 minutes: | 13:02:01 |
@drupol:matrix.org |  Download image.png | 13:02:03 |
@drupol:matrix.org | Kinda frustrating. | 13:02:10 |
@drupol:matrix.org | They do everything to keep their workers at home :D | 13:02:18 |
hexa (signing key rotation when) | also a very funny route | 13:03:05 |
hexa (signing key rotation when) | given that you are presumably sitting in brussels, but handing of the traffic to british telecom | 13:03:16 |
hexa (signing key rotation when) | for a detour via londoin | 13:03:20 |
hexa (signing key rotation when) | * for a detour via london | 13:03:22 |
hexa (signing key rotation when) | only to go back to amsterdam | 13:03:34 |
@drupol:matrix.org | yes indeed, sitting in brussels at the moment | 13:03:39 |
hexa (signing key rotation when) | * given that you are presumably sitting in brussels, but handing off the traffic to british telecom | 13:03:53 |
@drupol:matrix.org | Is there anything else I could do to try to spot where the issue comes from? | 13:04:00 |
hexa (signing key rotation when) | this really looks like the reverse path from fastly to your AS is broken | 13:04:16 |
hexa (signing key rotation when) | the solution is … peer with fastly somewhere and cut out the middleman | 13:04:42 |
@drupol:matrix.org | What worries me is this: the behaviour is strange: downloading just 30 MB takes around 15 minutes. It seems to follow a repeating pattern: the connection works normally for 1–2 seconds, then pauses for about 30 seconds, and this cycle continues indefinitely until the end. | 13:04:52 |
hexa (signing key rotation when) | yeah, a route can flap | 13:05:15 |
@drupol:matrix.org |
peer with fastly somewhere and cut out the middleman
how can I do that?
| 13:05:43 |
hexa (signing key rotation when) | https://bgp.tools/prefix/147.67.128.0/17#connectivity | 13:05:48 |
hexa (signing key rotation when) | single homed behind vodafone 🫠 | 13:05:56 |
hexa (signing key rotation when) | if you're not at any exchange you likely cannot | 13:06:48 |
@drupol:matrix.org | I guess the network here is quite protected indeed. | 13:07:15 |
@drupol:matrix.org | anyway, thanks for the help and the link I'll keep it :) | 13:09:12 |
| @federicodschonborn:matrix.org changed their display name from The Worm 🏳️🌈 (he/they) to Wormy McWormface 🏳️🌈 (he/they). | 18:27:19 |
| solideva joined the room. | 20:41:27 |
| 23 Jul 2025 |
vcunat | In the past couple hours we get lots of
mimas hydra-queue-runner[1040202]: AWS error '' (curlCode: 28, Timeout was reached; request id: ), will retry in NN ms
I see nothing at https://health.aws.amazon.com/health/status
| 10:28:29 |
vcunat | Hmm, we only fit less than two days of log for that unit, so who knows how rare this is over long term, but the build throughput does seem unusually low in the past couple hours (which is why I was looking at logs). | 10:31:15 |
vcunat | * In the past couple hours we get thousands of
mimas hydra-queue-runner[1040202]: AWS error '' (curlCode: 28, Timeout was reached; request id: ), will retry in NN ms
I see nothing at https://health.aws.amazon.com/health/status
| 10:32:16 |