Anyone around from Verizon? Cannot reach Facebook through Verizon FIOS in Long Beach, CA. No trouble on the AT&T 4G LTE network.
Thursday, August 14, 2015 @ 0410 UTC
matthew black
california state university, long beach
$ p www.facebook.com
PING star.c10r.facebook.com (31.13.69.197) 56(84) bytes of data.
64 bytes from edge-star-shv-01-iad3.facebook.com (31.13.69.197):
icmp_seq=1 ttl=89 time=12.1 ms
64 bytes from edge-star-shv-01-iad3.facebook.com (31.13.69.197):
icmp_seq=2 ttl=89 time=5.64 ms
(looks like I'm talking to an east-coast fb instance)
...
5 0.ae6.xl2.iad8.alter.net (140.222.228.57) 24.242 ms 24.707 ms *
6 0.xe-11-0-1.gw9.iad8.alter.net (152.63.33.169) 22.515 ms
0.xe-11-1-0.gw9.iad8.alter.net (152.63.35.117) 15.337 ms
0.xe-10-3-0.gw9.iad8.alter.net (152.63.41.246) 10.154 ms
7 fb-gw.customer.alter.net (204.148.11.102) 24.263 ms 11.457 ms 9.897 ms
8 psw01a.iad3.tfbnw.net (204.15.23.162) 10.428 ms
psw01b.iad3.tfbnw.net (204.15.23.154) 7.720 ms psw01c.iad3.tfbnw.net
(204.15.23.144) 9.050 ms
...
Pinging star.c10r.facebook.com [31.13.70.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
As I said, it fails from FIOS in Long Beach CA.
On the phone with FIOS support now. The tech wants me to reset my router to factory defaults even after explaining I can reach everything else. I suggested they had an upstream routing or peering problem.
Don't know if this is related but we got this maintenance notice from facebook. Router is within the same region.
----------------------
Hi Peers,
Facebook will be performing maintenance at Coresite LA1 One Wilshire in Los Angeles California. This will affect all peering sessions on our routers and you will see the peering go down intermittently.
ASN: 32934
Start: August 13 2015, 10:00 AM PST
End: August 13 2015, 6:00 PM PST
Peering details: as32934.peeringdb.com
Robert Horrigan
Edge & Network Services Team
----------------------
Carlos Alcantar
Race Communications / Race Team Member
1325 Howard Ave. #604, Burlingame, CA. 94010
Phone: +1 415 376 3314 / carlos@race.com / http://www.race.com
presumably this is fixed now, as:
3 t1-0-0-9.washdc-lcr-22.verizon-gni.net (130.81.32.238) 9.706 ms
10.155 ms t1-2-0-0.washdc-lcr-21.verizon-gni.net (100.41.220.10)
8.803 ms
4 * * *
5 0.ae2.xl3.lax1.alter.net (140.222.227.73) 64.368 ms 63.868 ms 64.362 ms
6 0.ae5.gw7.lax1.alter.net (152.63.112.222) 63.019 ms
0.ae6.gw7.lax1.alter.net (152.63.112.226) 67.564 ms
0.ae5.gw7.lax1.alter.net (152.63.112.222) 67.939 ms
7 facebook-gw.customer.alter.net (152.179.103.150) 68.375 ms
177.174 ms 63.066 ms
8 po101.psw01b.lax3.tfbnw.net (31.13.29.103) 62.537 ms
po101.psw01d.lax3.tfbnw.net (31.13.29.107) 62.533 ms 62.531 ms
9 msw1aa.01.lax3.tfbnw.net (173.252.64.50) 63.043 ms
msw1ab.01.lax3.tfbnw.net (204.15.22.123) 63.023 ms
msw1ah.01.lax3.tfbnw.net (204.15.22.114) 63.205 ms
10 edge-star-shv-01-lax1.facebook.com (31.13.70.1) 62.434 ms 61.857
ms 62.454 ms
and:
$ p 31.13.70.1
PING 31.13.70.1 (31.13.70.1) 56(84) bytes of data.
64 bytes from 31.13.70.1: icmp_seq=1 ttl=89 time=111 ms
-chris