 SeattleMattStreaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA |
[Northeast] Facebook LatencyLatency to Facebook is through the roof again tonight -
How f'ing long is this going to last?
Verizon's routing to the site has been in the crapper for months now - and it gets next to impossible in the evening... |
|
neftv
join:2000-10-01
Broomall, PA |
neftv
Member
2011-May-2 8:00 pm
My guess Verizon is adding those 50 and 100 meg accounts daily that the capacity is overwhelming upstream from Verizon. The providers upstream have to catch up with Verizon? 2,96.227.xx.1,5ms,L100.PHLAPA-VFTTP-123.verizon-gni.net,0 3,130.81.140.252,8ms,G0-6-4-1.PHLAPA-LCR-21.verizon-gni.net,0 4,130.81.22.58,6ms,so-9-0-0-0.PHIL-BB-RTR1.verizon-gni.net,0 5,152.63.3.61,60ms,0.xe-3-0-1.XL3.IAD8.ALTER.NET,0 6,152.63.33.117,54ms,0.ae3.BR1.IAD8.ALTER.NET,0 7,4.68.62.137,54ms,ae7.edge1.washingtondc4.level3.net,0 8,4.69.149.62,23ms,vlan60.csw1.Washington1.Level3.net,0 9,4.69.134.145,27ms,ae-62-62.ebr2.Washington1.Level3.net,0 10,4.69.132.90,17ms,ae-3-3.ebr1.NewYork2.Level3.net,0 11,4.69.135.254,24ms,ae-1-100.ebr2.NewYork2.Level3.net,0 12,4.69.141.21,17ms,ae-6-6.ebr2.NewYork1.Level3.net,0 13,4.69.135.185,88ms,ae-2-2.ebr4.SanJose1.Level3.net,0 14,4.69.153.10,89ms,ae-81-81.csw3.SanJose1.Level3.net,0 15,4.69.152.145,96ms,ae-3-80.edge2.SanJose3.Level3.net,0 16,4.53.210.14,84ms,FACEBOOK-IN.edge2.SanJose3.Level3.net,0 17,204.15.21.166,91ms,ae2.bb02.sjc1.tfbnw.net,0 18,0.0.0.0,20ms,,0 19,0.0.0.0,20ms,,0 20,74.119.79.49,118ms,po1023.csw01a.prn1.tfbnw.net,0 21,69.171.224.39,121ms,www-14-01-prn1.facebook.com,0 I remember when » www.internettrafficreport.com/use to show like 85 but lately its been 79 and declining. North American IT technology is going to come to a grinding halt just like the economy and employment. |
|
 Smith6612
MVM
join:2008-02-01
North Tonawanda, NY ·Charter
Ubee EU2251
Ubiquiti UAP-IW-HD
Ubiquiti UniFi AP-AC-HD
|
to SeattleMatt
It's not Verizon's issue either. My Frontier connection is seeing poor performance to Facebook at night. Maybe not as bad as Verizon on some nights, but still very bad. Frontier uses Level3 as their major peering provider, so perhaps the issue is laying with Level3. I know it isn't congestion on Frontier's network as everything else comes up crazy fast and my speeds are where they should be. My traces complete without any issue until I hit Facebook's own network in California, right after getting off of the Level3 network. I don't think this is so much of a Verizon issue than it is how Level3/Facebook's network are broadcasting available routes. |
|
 norbert26
Premium Member
join:2010-08-10
Warwick, RI |
to SeattleMatt
i doubt this has anything to do with FiOS. I have been having this problem for quite some time even on my iPhone . To further add to this the latency varies between different devices i use including the computer, the blu-ray player app (real bad there) , a logi tech revue, and iPhone. Facebook needs to address this issue. |
|
SeattleMattStreaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA |
Not to mention they constantly flip flop their routing broadcasts.
One second I'm 16ms to Virginia - the next trace i'm 200 out to somewhere in California (whatever PRN is).
Last night was really bad - with 33% Packet Loss. I'm in agreement that this isn't a VZ specific issue - just really frustrating. |
|
 drakeBack to back
MVM
join:2002-06-10
Bridgeport, CT |
to norbert26
said by norbert26:Facebook needs to address this issue.
It's not Facebook's issue; its the routing path. I've been using my FiOS connection with Facebook and yet to see an issue. A trace route proves this as well - last night (after reading this thread) and now. Until those routing stations address the issue, there's really nothing you can do. Though I can suggest changing your IP address which may put you on a different subnet thus a different route to the destination. I've seen this to work for a few other members here; maybe it will work for you guys too. |
|
n3voc
join:2011-06-22
Glenshaw, PA |
to SeattleMatt
Actually it is most definately a Facebook problem. Do a whois on the IP addresses that fail. They are Facebook IP's! |
|
faze
join:2011-01-10
Reisterstown, MD |
to SeattleMatt
Having this issue here in Maryland. Works perfectly fine on my T-Mobile 4G phone. The second I switch to my home wifi, slows down to a crawl. I would call Verizon, but I'm not some dufus end user that knows nothing about IT. I don't feel like going through the power cycle crap and clear cache/cookies crap all day long. |
|
|
drakeBack to back
MVM
join:2002-06-10
Bridgeport, CT |
to SeattleMatt
Latency seems fine for me in New York City. Tracing route to facebook.com [69.63.189.11]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 4 ms L100.NYCMNY-VFTTP-174.verizon-gni.net [71.183.49.1]
3 7 ms 6 ms 7 ms G4-0-3-1074.NYCMNY-LCR-10.verizon-gni.net [130.81.139.78]
4 7 ms 7 ms 6 ms so-5-0-3-0.NY5030-BB-RTR2.verizon-gni.net [130.81.29.238]
5 10 ms 8 ms 8 ms 0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.2.81]
6 8 ms 8 ms 8 ms 204.255.168.194
7 14 ms 17 ms 15 ms FACEBOOK-INC.ethernet12-1.csr1.DCA3.gblx.net [64.215.81.234]
8 19 ms 22 ms 18 ms ae1.bb02.iad1.tfbnw.net [74.119.78.60]
9 13 ms 12 ms 12 ms ae11.dr03.ash2.tfbnw.net [74.119.78.154]
10 17 ms 14 ms 14 ms po1016.csw01b.ash2.tfbnw.net [74.119.76.117]
11 18 ms 22 ms 20 ms www-10-01-ash2.facebook.com [69.63.189.11]
Trace complete.
|
|
| |
to n3voc
said by n3voc:Actually it is most definately a Facebook problem. Do a whois on the IP addresses that fail. They are Facebook IP's!
Experiencing serious issues here in Canada and the latency jumps once it hits Facebook's servers:
8 71 ms 40 ms 40 ms equinix.br01.ord1.tfbnw.net [206.223.119.115]
9 120 ms 128 ms 87 ms ae0.bb02.sea1.tfbnw.net [74.119.79.34]
10 165 ms 99 ms 119 ms ae5.bb02.prn1.tfbnw.net [74.119.79.99]
11 90 ms 112 ms 102 ms ae1.dr01.prn1.tfbnw.net [74.119.79.105]
12 97 ms 96 ms 98 ms po1023.csw01a.prn1.tfbnw.net [74.119.79.49]
13 124 ms 133 ms 115 ms www-16-01-prn1.facebook.com [69.171.224.41]
As soon as I had issues, I searched the forums to see if anyone else did, which lead me to this thread. |
|
neftv
join:2000-10-01
Broomall, PA |
to drake
I am in suburban Philadelphia and looks like routing to facebook is a longer time for the Philadelphia area.
tracert facebook.com
Tracing route to facebook.com [69.63.181.12]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms xxxxx
2 5 ms 4 ms 4 ms L100.PHLAPA-VFTTP-123.verizon-gni.net [96.227.82
.1]
3 6 ms 7 ms 7 ms G0-6-4-1.PHLAPA-LCR-21.verizon-gni.net [130.81.1
40.252]
4 * * * Request timed out.
5 13 ms 12 ms 12 ms so-8-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net
[130.81.17.3]
6 12 ms 12 ms 12 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21]
7 99 ms 194 ms 14 ms te4-4-10G.ar6.DCA3.gblx.net [208.178.58.121]
8 14 ms 14 ms 14 ms xe6-2-0-10G.scr2.WDC2.gblx.net [67.16.136.197]
9 81 ms 82 ms 82 ms ae5.scr4.SNV2.gblx.net [67.16.140.170]
10 84 ms 84 ms 94 ms e5-3-40G.ar5.SJC2.gblx.net [67.17.72.14]
11 78 ms 83 ms 79 ms 64.208.158.30
12 84 ms 84 ms 84 ms ae1.bb02.sjc1.tfbnw.net [204.15.21.164]
13 79 ms 87 ms 81 ms ae7.br01.snc1.tfbnw.net [204.15.20.57]
14 85 ms 84 ms 84 ms po1023.csw01b.snc2.tfbnw.net [74.119.79.241]
15 81 ms 82 ms 87 ms www-11-01-snc2.facebook.com [69.63.181.12]
Trace complete. |
|
| |
urbanriot
Premium Member
2011-Jun-23 12:32 am
Issue finally rectified itself for me. Hopefully it was related to your issues and it's also fine for you...! |
|
| |
to SeattleMatt
I have the same issues. Facebook loads like it's on a dial up connection. I'm in upstate N.Y. and it's been like this for a while now.
Tracing route to www.facebook.com [69.171.228.14]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms XXXXXXX
2 5 ms 4 ms 4 ms 10.32.63.96
3 6 ms 7 ms 7 ms G3-0-7-390.NYCMNY-LCR-13.verizon-gni.net [130.81
.96.170]
4 9 ms 9 ms 9 ms so-7-2-0-0.NY325-BB-RTR1.verizon-gni.net [130.81
.28.52]
5 10 ms 9 ms 9 ms 0.ae1.BR2.NYC4.ALTER.NET [152.63.18.37]
6 8 ms 9 ms 9 ms 204.255.168.190
7 5 ms 7 ms 6 ms ae4-40G.scr4.NYC1.gblx.net [67.16.134.161]
8 87 ms 86 ms 87 ms xe5-0-0-10G.scr4.SNV2.gblx.net [67.17.95.138]
9 91 ms 87 ms 87 ms e5-3-40G.ar5.SJC2.gblx.net [67.17.72.14]
10 113 ms 84 ms 84 ms 64.208.158.30
11 84 ms 87 ms 84 ms ae0.bb01.sjc1.tfbnw.net [74.119.76.21]
12 85 ms 114 ms 87 ms ae2.bb01.pao1.tfbnw.net [74.119.76.136]
13 118 ms 122 ms 121 ms ae9.bb01.prn1.tfbnw.net [204.15.20.51]
14 110 ms 104 ms 104 ms ae0.dr03.prn1.tfbnw.net [204.15.23.85]
15 108 ms 114 ms 114 ms po1023.csw05a.prn1.tfbnw.net [74.119.76.249]
16 116 ms 114 ms 106 ms www-13-05-prn1.facebook.com [69.171.228.14]
Trace complete. |
|
| |
to SeattleMatt
Facebook needs to upgrade their servers to hold the capacity like googles ..since so many people use facebook and it slows down.. and it gets ddosed all the time by hackers.. |
|
 WK2
Premium Member
join:2006-12-28
united state |
WK2
Premium Member
2011-Jun-23 3:00 pm
it takes me 1.5 minutes to load Facebook |
|
kes601
join:2007-04-14
Virginia Beach, VA |
to SeattleMatt
Facebook SLOW here as well, was fine at work (err, umm, research), but at home....SLOW. |
|
| |
Facebook's been slow all day, everyday here for weeks. Getting to be a serious PITA. |
|
kes601
join:2007-04-14
Virginia Beach, VA |
kes601
Member
2011-Jun-23 4:56 pm
Interestingly, m.facebook.com is quite fast. |
|
| |
to SeattleMatt
Slow here in North Texas. |
|
| |
Not for me....don't know why.... |
|
 John97Over The Hills And Far Away
Premium Member
join:2000-11-14
Spring Hill, FL |
to SeattleMatt
Horrendously slow here. This is by far the worst it has ever been. |
|
| |
to justin9876
said by justin9876:Not for me....don't know why.... What is your "tracert www.facebook.com" Mine is below Tracing route to www.facebook.com [69.171.224.40] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms router.home.com [192.168.1.1] 2 4 ms 4 ms 4 ms L100.DLLSTX-VFTTP-49.verizon-gni.net [173.64.199.1] 3 3 ms 4 ms 4 ms G0-1-849.DLLSTX-LCR-08.verizon-gni.net [130.81.107.110] 4 3 ms 4 ms 4 ms so-6-2-0-0.DFW01-BB-RTR2.verizon-gni.net [130.81.28.210] 5 8 ms 7 ms 7 ms 0.ae2.BR1.DFW13.ALTER.NET [152.63.2.149] 6 6 ms 7 ms 7 ms te1-4-10G.ar5.DAL2.gblx.net [64.208.27.2] 7 6 ms 6 ms 7 ms ae0-20G.scr1.DAL1.gblx.net [67.16.139.9] 8 51 ms 51 ms 52 ms xe8-1-0-10G.scr3.SNV2.gblx.net [67.16.163.106] 9 54 ms 52 ms 54 ms e8-1-20G.ar5.SJC2.gblx.net [67.16.145.118] 10 50 ms 52 ms 52 ms 64.208.158.30 11 55 ms 54 ms 54 ms ae0.bb01.sjc1.tfbnw.net [74.119.76.21] 12 80 ms 57 ms 57 ms ae2.bb01.pao1.tfbnw.net [74.119.76.136] 13 * 94 ms 94 ms ae9.bb01.prn1.tfbnw.net [204.15.20.51] 14 90 ms * 91 ms ae0.dr01.prn1.tfbnw.net [74.119.79.101] 15 93 ms * 97 ms po1023.csw01b.prn1.tfbnw.net [74.119.79.53] 16 92 ms 92 ms 92 ms www-15-01-prn1.facebook.com [69.171.224.40] Trace complete. |
|
SeattleMattStreaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA |
to John97
John,
Agreed - it's slowing down now before 6pm Eastern.
Facebook really needs to beef up their infrastructure. |
|
solarein
join:2010-12-03
San Francisco, CA |
to SeattleMatt
Been having a problem in Westchester, NY too for about 3 days now. I've noticed that traceroute has been reporting a different route ever since it became slow, may have something to do with it. I don't remember what exactly the route to facebook.com was like earlier but it was a short one, 10 hops or fewer, and every hop reported its IP. How it looks like this.
traceroute to facebook.com (69.63.181.12), 30 hops max, 60 byte packets
1 - (192.168.1.1) 0.315 ms 0.271 ms 0.414 ms
2 L100.NYCMNY-VFTTP-128.verizon-gni.net (71.183.96.1) 4.034 ms 3.996 ms 3.954 ms
3 G3-0-1-1128.NYCMNY-LCR-11.verizon-gni.net (130.81.107.180) 3.913 ms 3.995 ms 3.957 ms
4 so-2-1-0-0.NY325-BB-RTR1.verizon-gni.net (130.81.29.12) 6.070 ms 6.030 ms 6.214 ms
5 0.ae1.BR2.NYC4.ALTER.NET (152.63.18.37) 5.903 ms 5.878 ms 6.073 ms
6 204.255.168.190 (204.255.168.190) 6.044 ms 7.186 ms 7.140 ms
7 ae4-40G.scr4.NYC1.gblx.net (67.16.134.161) 7.082 ms 6.044 ms 6.002 ms
8 xe5-0-0-10G.scr4.SNV2.gblx.net (67.17.95.138) 110.916 ms 110.882 ms 110.805 ms
9 e5-3-40G.ar5.SJC2.gblx.net (67.17.72.14) 98.427 ms 86.912 ms 86.834 ms
10 64.208.158.30 (64.208.158.30) 84.132 ms 84.048 ms 82.661 ms
11 ae1.bb02.sjc1.tfbnw.net (204.15.21.164) 87.341 ms 87.281 ms ae0.bb01.sjc1.tfbnw.net (74.119.76.21) 83.878 ms
12 ae4.br02.snc1.tfbnw.net (74.119.76.26) 83.796 ms ae3.dr04.snc1.tfbnw.net (74.119.78.190) 97.017 ms ae7.br01.snc1.tfbnw.net (204.15.20.57) 83.667 ms
13 po1022.csw01b.snc2.tfbnw.net (74.119.79.243) 97.174 ms 96.888 ms po1020.csw01a.snc2.tfbnw.net (74.119.79.239) 97.047 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
|
|
neftv
join:2000-10-01
Broomall, PA |
to SeattleMatt
I wonder how a tracert with someone one on Comcast looks like. |
|
John97Over The Hills And Far Away
Premium Member
join:2000-11-14
Spring Hill, FL |
to SeattleMatt
Only one timeout this time, usually there are several as of late... |
|
SeattleMattStreaming Tech Director
Premium Member
join:2001-12-28
Seattle, WA |
It's all within the Facebook network - Comcast's traceroute's shouldn't look any different. |
|
faze
join:2011-01-10
Reisterstown, MD |
faze
Member
2011-Jun-24 8:26 am
So why do mobile networks not have this issue if it's all Facebook's fault? |
|
1 edit |
said by faze:So why do mobile networks not have this issue if it's all Facebook's fault?
It's not the mobile networks that save it from having a problem. You can visit the mobile site (m.facebook.com) over your FiOS connection and it will be just as fast. The mobile site is on different servers, is pared down, and likely has fewer users hitting it at any given time. |
|
| |
to SeattleMatt
Facebook has been unusable at night from the desktop for the past week or 2.
If it's not a Verizon issue, but rather a facebook issue affecting all users, why isn't this national news? |
|
·
