cancel
Showing results for 
Search instead for 
Did you mean: 

Facebook and Instagram CDN Reachability Issues

FIXED
Community Gaffer
Community Gaffer
Posts: 5,461
Thanks: 817
Fixes: 9
Registered: ‎04-04-2007

Re: Facebook and Instagram CDN Reachability Issues

@davidmhewitt BTW, where did you get the domains to trace to? Are getting them from the source of the page?

(This is important as the domain you are tracing to appear to be from Facebook's Brazilian CDNs...)

Kelly Dorset
Broadband Service Manager
Hooked
Posts: 9
Registered: ‎20-01-2020

Re: Facebook and Instagram CDN Reachability Issues

@Kelly Interesting, I hadn't spotted that.

 

I got the domains to trace by using the network inspector in Firefox while it was failing to load and seeing which requests were timing out.

 

I'm no longer seeing that domain in the network requests and I'm seeing lhr domains instead now, which I assume is London Heathrow.

Newbie
Posts: 1
Registered: ‎25-01-2020

Re: Facebook and Instagram CDN Reachability Issues

Hi there.

 

I was running in to similar problems on Wednesday: vast swathes of the internet were unrouteable. For example I could ping google DNS at 8.8.8.8 but couldn't ping google.com or my usual go-to test address at 131.111.8.59 (both destination unreachable).

 

I spoke to a support agent who, similarly, set me to a temporary static IP which seemed to resolve the problem. She asked I post an example traceroute to provide another data point. This thread seemed the most appropriate.

 

The IP I used here was just whatever google.com resolved to at that time since it still happened to be in by backscroll. Hopefully this is useful.

 

 

bishop:~ dh219$ traceroute 178.32.176.32
traceroute to 178.32.176.32 (178.32.176.32), 64 hops max, 52 byte packets
 1  dsldevice (192.168.2.1)  2.822 ms  2.626 ms  2.066 ms
 2  84.93.253.216 (84.93.253.216)  7.762 ms  7.976 ms  8.397 ms
 3  84.93.253.219 (84.93.253.219)  12.587 ms  9.197 ms
    84.93.253.223 (84.93.253.223)  8.628 ms
 4  195.99.125.144 (195.99.125.144)  10.688 ms  8.660 ms  9.317 ms
 5  peer8-et-3-1-6.telehouse.ukcore.bt.net (109.159.252.174)  8.410 ms
    peer8-et-4-0-4.telehouse.ukcore.bt.net (194.72.16.160)  8.333 ms
    peer8-et-0-0-1.telehouse.ukcore.bt.net (62.172.103.170)  10.685 ms
 6  ldn-1-a9.uk.eu (54.36.50.112)  10.210 ms
    ldn-5-a9.uk.eu (54.36.50.114)  10.314 ms
    ldn-1-a9.uk.eu (54.36.50.112)  8.660 ms
 7  be103.gra-g2-nc5.fr.eu (213.251.128.64)  12.791 ms  13.637 ms
    be103.gra-g1-nc5.fr.eu (91.121.215.178)  12.599 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * *^C

 

Community Gaffer
Community Gaffer
Posts: 5,461
Thanks: 817
Fixes: 9
Registered: ‎04-04-2007

Re: Facebook and Instagram CDN Reachability Issues

Fix

 davidmhewitt We suspect it's a problem with a small range of IPs.  Facebook think they are associated with an ISP in Chile!  We've quantined the range now, so I'll remove the static IP.  Let us know if the issue comes back! 

Kelly Dorset
Broadband Service Manager
Community Gaffer
Community Gaffer
Posts: 5,461
Thanks: 817
Fixes: 9
Registered: ‎04-04-2007

Re: Facebook and Instagram CDN Reachability Issues

@dhuk01 What were you trying to get to for the IP 178.32.176.32?  I don't think that's a Google IP?

I'm pretty sure this isn't related to this thread though.  You weren't on the same IP range Smiley

Kelly Dorset
Broadband Service Manager
Hooked
Posts: 9
Registered: ‎20-01-2020

Re: Facebook and Instagram CDN Reachability Issues

Very interesting! Thank you again for all your help with this and for keeping me up to date.