Verizon FIOS routing trouble to Facebook

Fri Aug 14 13:58:42 UTC 2015

On Fri, Aug 14, 2015 at 12:30 AM, Matthew Black <Matthew.Black at csulb.edu> wrote:
> 31.13.70.1

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