Hi,
This specific, and many others, are only announced to peers in the
metro they originate in. To receive this prefix directly you'll
need to peer with us in Los Angeles.
the point is: Level3 is exporting this prefix to the EU since ~1 week
Telia is learning it from Level3 and they also started to re-export it:
Telia Looking Glass
(Telia Looking Glass
r=Vienna)
Command: show route protocol bgp 31.13.71.36 table inet.0
31.13.71.0/24 *[BGP/170] 18w5d 16:40:16, MED 0, localpref 150
AS path: 3356 32934 I, validation-state: unverified
> to 80.239.128.178 via ae9.0
This is causing >120ms latency to Austrian (and some German ...) networks
towards Facebook - current traceroute from source network 188.172.239.0/24:
Packets
Pings
Host Loss% Snt Last Avg
Best Wrst StDev
1. router 0.0% 4 0.5 0.5
0.5 0.6 0.0
2. 192.168.8.3 0.0% 4 0.6 0.7
0.6 0.8 0.1
3. 37.252.236.88 0.0% 4 37.3 34.2
30.6 37.3 2.9
4. er-03.00-09-23.anx04.vie.at.anexia-it.com 0.0% 4 21.1 31.9
21.1 50.9 13.3
5. cr-02.0v-08-72.anx03.vie.at.anexia-it.com 0.0% 4 23.2 25.9
20.4 31.6 5.1
6. win-b4-link.telia.net 0.0% 4 22.1 25.0
22.1 30.1 3.5
7. level-ic-1573273-wien-b4.c.telia.net 0.0% 3 22.4 22.3
21.1 23.3 1.1
8. ae-3-3611.edge2.dallas1.level3.net 0.0% 3 150.5 150.6
150.4 150.8 0.2
9. facebook-in.edge2.dallas1.level3.net 0.0% 3 156.6 152.9
151.0 156.6 3.2
10. po102.psw02.dft4.tfbnw.net 0.0% 3 151.4 151.6
151.4 152.0 0.4
11. 173.252.67.57 0.0% 3 151.6 152.3
151.6 153.4 0.9
12. edge-star-mini-shv-01-dft4.facebook.com 0.0% 3 159.3 158.4
152.5 163.6 5.6
The admins of AS42473 started to drop the more specific from Level3 and now
they get it from Telia (which is the Level3 re-export they learned).
I guess you guys should talk to Level3 and ask them what the hell they are
doing? :).
Thanks & best regards
Jürgen