Re: Verizon FIOS routing trouble to Facebook

[Carlos Alcantar <carlos () race com>]

Don't know if this is related but we got this maintenance notice from facebook.  Router is within the same region.

----------------------​

Subject: Facebook Network Maintenance Notification AS32934
 

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


________________________________________
From: NANOG <nanog-bounces () nanog org> on behalf of Matthew Black <Matthew.Black () csulb edu>
Sent: Thursday, August 13, 2015 9:30 PM
To: Christopher Morrow
Cc: nanog () nanog org
Subject: RE: Verizon FIOS routing trouble to Facebook

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.



-----Original Message-----
From: christopher.morrow () gmail com [mailto:christopher.morrow () gmail com] On Behalf Of Christopher Morrow
Sent: Thursday, August 13, 2015 9:18 PM
To: Matthew Black
Cc: nanog () nanog org
Subject: Re: Verizon FIOS routing trouble to Facebook

On Fri, Aug 14, 2015 at 12:12 AM, Matthew Black <Matthew.Black () csulb edu> wrote:
> Anyone around from Verizon? Cannot reach Facebook through Verizon FIOS in Long Beach, CA. No trouble on the AT&T 4G 
> LTE network.

$ 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
...