Facebook slow or timing out

[jezuk1]

Hello all,

I'm having trouble accessing the Facebook website, is anybody else? It's been like this for a few days now. Sometimes pages load, sometimes they time out. It seems to come and go in phases, the website becomes responsive for a while and then all of a sudden links and pages will no longer load. Tried to access it just now and here's the delightful Chrome response:



Here's a traceroute while I'm unable to access the website:

Code Select Expand

C:\Users\Jez>tracert www.facebook.com

Tracing route to star.c10r.facebook.com [2a03:2880:2040:1f01:face:b00c:0:8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  (my ip)
  2    15 ms    15 ms    15 ms  2a02:390:ffff:ffff:ffff:ffff:ffff:ffed
  3    16 ms    16 ms    16 ms  2a02:390:0:fffb:204:4eff:feb3:741b
  4    15 ms    16 ms    16 ms  2a02:390:0:ff00:21b:21ff:fe70:879e
  5    17 ms    17 ms    20 ms  gigabitethernet25.switch2.lon1.he.net [2001:470:1:222::1]
  6    58 ms    17 ms    15 ms  2001:7f8:4::80a6:1
  7    91 ms    91 ms    90 ms  ae19.bb01.iad2.tfbnw.net [2620:0:1cff:dead:beef::259]
  8    90 ms    91 ms    90 ms  ae7.dr02.ash4.tfbnw.net [2620:0:1cff:dead:beef::335]
  9    92 ms    92 ms    94 ms  po1022.csw01a.ash4.tfbnw.net [2620:0:1cff:dead:beef::148d]
10    89 ms    91 ms    90 ms  edge-star6-ecmp-01-ash4.facebook.com [2a03:2880:2040:1f01:face:b00c:0:8]

Trace complete.

No obvious problems seen in that department.

[Lance]

I wonder if you could force an ipv4 connection to see if you still have the problem?

[jezuk1]

I wonder if you could force an ipv4 connection to see if you still have the problem?

Good idea. I turned IPv6 protocol off in Windows to test it. The website seems much more responsive now, no problems seen over IPv4 so far. I think if this is an IPv6 related problem it's only affecting Facebook. Quite a few other websites including YouTube and even World of Warcraft has been connected via 6 for a while now and no problems experienced there.

IPv4 traceroute:

Code Select Expand

C:\Users\Jez>tracert www.facebook.com

Tracing route to star.c10r.facebook.com [31.13.80.23]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsl-7800n.home.gateway [192.168.1.254]
  2    15 ms    15 ms    15 ms  redbus-gw3.idnet.net [212.69.63.42]
  3    15 ms    16 ms    15 ms  redbus-gw5-gi2-300.idnet.net [212.69.63.229]
  4    17 ms    16 ms    16 ms  telehouse-gw6-gi4-1276.idnet.net [212.69.63.10]
  5    16 ms    22 ms    24 ms  v225.core1.lon1.he.net [216.66.86.45]
  6    23 ms    23 ms    23 ms  10gigabitethernet2-4.core1.par2.he.net [72.52.92.42]
  7    24 ms    23 ms    23 ms  ae0.pr01.cdg1.fb.com [195.42.144.181]
  8    24 ms    24 ms    24 ms  ae1.bb01.cdg1.tfbnw.net [204.15.22.194]
  9    24 ms    23 ms    23 ms  ae1.pr02.cdg1.tfbnw.net [204.15.23.13]
10    23 ms    24 ms    28 ms  po126.msw01.02.cdg1.tfbnw.net [31.13.27.93]
11    24 ms    24 ms    24 ms  star-01-02-cdg1.facebook.com [31.13.80.23]

Trace complete.

At least the IPv4 route doesn't go half way around the world 

[Lance]

I guess even the big websites are still getting used to IPv6!

[jezuk1]

I guess even the big websites are still getting used to IPv6!

Perhaps it will magically resolve itself in time. I'm not too worried about it anyhow