IPv4 Routing/Peering Issues with Vodafone

Since yesterday evening my containers fail to build because they are unable to reach the npm registry, which is served by Cloudflare. There are multiple A records for the corresponding domain:

dig registry.npmjs.org

; <<>> DiG 9.16.1-Ubuntu <<>> registry.npmjs.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26996
;; flags: qr rd ra; QUERY: 1, ANSWER: 12, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;registry.npmjs.org.            IN      A

;; ANSWER SECTION:
registry.npmjs.org.     138     IN      A       104.16.25.35
registry.npmjs.org.     138     IN      A       104.16.17.35
registry.npmjs.org.     138     IN      A       104.16.23.35
registry.npmjs.org.     138     IN      A       104.16.26.35
registry.npmjs.org.     138     IN      A       104.16.19.35
registry.npmjs.org.     138     IN      A       104.16.24.35
registry.npmjs.org.     138     IN      A       104.16.21.35
registry.npmjs.org.     138     IN      A       104.16.18.35
registry.npmjs.org.     138     IN      A       104.16.20.35
registry.npmjs.org.     138     IN      A       104.16.16.35
registry.npmjs.org.     138     IN      A       104.16.22.35
registry.npmjs.org.     138     IN      A       104.16.27.35

I can reach:
104.16.24.35
104.16.20.35
104.16.27.35

I can’t reach:
104.16.25.35
104.16.17.35
104.16.23.35
104.16.26.35
104.16.19.35
104.16.21.35
104.16.18.35
104.16.16.35
104.16.22.35

This is a tracert to a working address:

tracert 104.16.27.35

Routenverfolgung zu 104.16.27.35 über maximal 30 Hops

  1    <1 ms     1 ms     1 ms  fritz.box [192.168.178.1]
  2    12 ms     6 ms     8 ms  ip53a9b72d.static.kabel-deutschland.de [83.169.183.45]
  3     7 ms     9 ms     7 ms  ip5886eacb.static.kabel-deutschland.de [88.134.234.203]
  4     9 ms     8 ms    11 ms  145.254.3.66
  5    18 ms    16 ms    17 ms  145.254.2.179
  6     *       17 ms    18 ms  145.254.2.179
  7     *        *        *     Zeitüberschreitung der Anforderung.
  8    24 ms    17 ms    17 ms  104.16.27.35

Whereas a tracert to an unreachable address stops at the last vodafone hop:

tracert 104.16.25.35

Routenverfolgung zu 104.16.25.35 über maximal 30 Hops

  1    <1 ms     1 ms     1 ms  fritz.box [192.168.178.1]
  2     8 ms    10 ms    10 ms  ip53a9b72d.static.kabel-deutschland.de [83.169.183.45]
  3     8 ms     8 ms     8 ms  ip5886eacb.static.kabel-deutschland.de [88.134.234.203]
  4     7 ms     9 ms    10 ms  145.254.3.66
  5    20 ms    17 ms    20 ms  145.254.2.179
  6     *       23 ms     *     145.254.2.179
  7     *        *        *     Zeitüberschreitung der Anforderung.
  8     *        *        *     Zeitüberschreitung der Anforderung.
  9     *        *        *     Zeitüberschreitung der Anforderung.
[...]

Is there something amiss with your peering with Vodafone?

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.