[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Facebook doesn't have a route to my ISP's (Cogeco) IPv6 space?
On Thu, 20 Dec 2018 at 22:12, Brian J. Murrell <brian at interlinx.bc.ca> wrote:
>
> On Thu, 2018-12-20 at 17:28 -0600, Constantine A. Murenin wrote:
> > Hi Brian,
>
> Hi,
>
> > But what's exactly at 2a03:2880:f012:3:face:b00c:0:1?
>
> It's one of the endpoints involved in Facebook's Messenger service.
> IIRC it's "graph.facebook.com", although I note that that address is
> currently answering as:
>
> graph.facebook.com. 2068 IN CNAME api.facebook.com.
> api.facebook.com. 2068 IN CNAME star.c10r.facebook.com.
> star.c10r.facebook.com. 25 IN AAAA 2a03:2880:f00e:a:face:b00c:0:2
>
> To be fair though, that one could just be what a load-balancing name
> service is responding at the moment. Notice that the two addresses are
> only off by one.
>
> But even more interesting is that it's now working:
>
> My traceroute [v0.92]
> pc.interlinx.bc.ca (2001:1970:5261:d600:c5d9:3319:afbc:3bb6) 2018-12-20T23:07:14-0500
> Keys: Help Display mode Restart statistics Order of fields quit
> Packets Pings
> Host Loss% Snt Last Avg Best Wrst StDev
> 1. 2001:1970:5261:d600::1 0.0% 94 0.6 0.7 0.4 3.8 0.3
> 2. 2001:1970:4000:82::1 0.0% 94 9.0 20.2 7.3 889.2 91.0
> 3. 2001:1970:0:1a7::1 39.4% 94 19.8 19.5 17.9 26.3 1.8
> 4. 2001:1970:0:61::1 45.2% 93 18.1 16.5 14.3 22.5 1.9
> 5. ae7.pr03.yyz1.tfbnw.net 0.0% 93 19.6 19.4 14.9 76.8 9.4
> 6. po103.psw04.yyz1.tfbnw.net 0.0% 93 14.5 15.8 13.9 24.0 1.5
> 7. po4.msw1ab.01.yyz1.tfbnw.net 0.0% 93 15.3 15.7 14.2 24.0 1.3
> 8. 2a03:2880:f00e:a:face:b00c:0:1 0.0% 93 19.2 15.5 13.7 22.5 1.7
>
> And even just a few minutes ago it was not as I was testing it for
> another (off-list) query:
>
> My traceroute [v0.92]
> pc.interlinx.bc.ca (2001:1970:5261:d600:c5d9:3319:afbc:3bb6) 2018-12-20T22:47:51-0500
> Keys: Help Display mode Restart statistics Order of fields quit
> Packets Pings
> Host Loss% Snt Last Avg Best Wrst StDev
> 1. 2001:1970:5261:d600::1 0.0% 112 0.6 0.7 0.5 5.1 0.4
> 2. 2001:1970:4000:82::1 0.0% 112 9.2 15.8 7.3 374.4 36.2
> 3. 2001:1970:0:1a7::1 17.0% 112 18.3 19.1 17.6 21.9 0.8
> 4. 2001:1970:0:61::1 33.0% 112 15.9 16.0 14.8 27.9 1.8
> 5. 2001:1978:1300::1 0.0% 112 15.5 17.0 14.1 49.8 4.4
> 6. 2001:1978:203::45 0.0% 112 29.5 29.8 28.2 46.8 2.1
> 7. ???
>
> Perhaps the bit of cage rattling that I have done here has knocked
> something loose. :-)
>
> Cheers,
> b.
I think TFBNW folks definitely read these lists, even if they never
respond officially.
Their whole network was apparently down via IPv6 for like at least a
few days several years ago; they've then fixed it back in the day by
simply removing the AAAA records. :-)
https://puck.nether.net/pipermail/outages/2013-May/005570.html
https://puck.nether.net/pipermail/outages/2013-May/005579.html
It's kind of amazing that tech reporters never really pick up these
stories, TBH. I guess these outages don't really sell, especially if
noone but a few selected users can even detect it in the first place,
even if they do last for days or even weeks/years for certain users in
certain configurations.
Cheers,
Constantine.