dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1924
namida12
join:2004-10-30
Las Vegas, NV

namida12

Member

Cox or Facebook?

I realize this is the holidays and the internet volume is greater than early December. But Facebook has become a joke, impossible to reach, load, or mid page freezing.

Question: is it the cox system that is awash with more users than it can handle, or is it a Facebook problem not being able to handle the holiday traffic?

Or is it my modem, and service that can not load Facebook?

I have rebooted modem, router, and changed out the cables. I have also reinstalled the operating system but I am still having the same problems, with all browsers.

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7

Member

No problems here as of now. But a couple weeks ago I noticed Facebook was having some problems. Pages would load fine, but not icons or user photos. It seemed to be national, since I am in RI and it also effected my aunt on a different ISP in Maine.

Maybe start with a tracert to facebook to see if the problems shows up. Also, do you have any parental controls or DDNS enabled on the router?

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA

odog to namida12

Premium Member

to namida12
do you have another device in your house you can try facebook on?
ajwees41
Premium Member
join:2002-05-10
Omaha, NE

ajwees41 to namida12

Premium Member

to namida12
it's facebook some people including me and a few friends had issues and other sites work. It seems to happen at least once a month or if the server that handles the account info is down you can't login while other users on a different server can. just have to wait it out.
namida12
join:2004-10-30
Las Vegas, NV

1 edit

namida12

Member

Q: "do you have any parental controls or DDNS enabled on the router?"
A: No

Phone brings up Facebook immediately. So mobile is good, but Computers are being throttled, or they have underestimated their user volume.

Can run a Tracer see below, but can't open the Facebook website in any browser the last 20 minutes. Tracer stopped and hesitated for a second or two on screen at hop 10.

Maybe the Facebook stock should take a hit if they charged their advertisers more for December and they can not handle this holiday volume?


$ traceroute facebook.com
traceroute to facebook.com (173.252.120.6), 30 hops max, 60 byte packets
1 (Router) 1.050 ms 1.421 ms 1.615 ms
2 10.72.0.1 (10.72.0.1) 8.855 ms 12.845 ms 13.039 ms
3 24-234-16-232.ptp.lvcm.net (24.234.16.232) 13.238 ms 13.431 ms 13.423 ms
4 24-234-6-28.ptp.lvcm.net (24.234.6.28) 13.997 ms 14.193 ms 14.185 ms
5 sanjbprj02-ae0.0.rd.sj.cox.net (68.1.5.186) 34.241 ms 34.246 ms 34.375 ms
6 ae27.pr03.sjc1.tfbnw.net (103.4.98.54) 34.368 ms ae22.pr04.sjc1.tfbnw.net (103.4.96.106) 22.657 ms 22.818 ms
7 ae1.bb03.sjc1.tfbnw.net (31.13.26.160) 22.803 ms ae2.bb03.sjc1.tfbnw.net (31.13.26.164) 28.930 ms 28.885 ms
8 ae30.bb02.sjc1.tfbnw.net (74.119.78.46) 26.600 ms ae16.bb01.sjc1.tfbnw.net (31.13.28.238) 34.305 ms ae30.bb02.sjc1.tfbnw.net (74.119.78.46) 26.372 ms
9 be16.bb01.frc3.tfbnw.net (31.13.24.28) 97.501 ms 97.696 ms be16.bb02.frc3.tfbnw.net (31.13.24.42) 96.288 ms
10 ae60.dr01.frc3.tfbnw.net (204.15.23.247) 93.414 ms ae61.dr03.frc3.tfbnw.net (173.252.64.65) 93.837 ms 95.727 ms
11 * * *
12 * * *
13 edge-star-shv-12-frc3.facebook.com (173.252.120.6) 87.268 ms 92.141 ms 92.135 ms

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA
Nokia BGW320-505

odog

Premium Member

Switch the phone to use WiFi only.(airplane mode, then enable WiFi) and try facebook that way.

I haven't had any issues here in Atlanta but the traceroute does look a little strange. You're going LV to San Jose leaving cox, and getting on the facebook network for a ~70ms ride to frc3?(kansas?) I'm not exactly sure where frc3 is, but 70ms is at least halfway across the country. I would expect you to be hitting a west coast data center.

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

1 edit

NormanS to namida12

MVM

to namida12
I have to concur with odog See Profile; something weird with your route. Starting in San José, I see:
C:\utils\dig>tracert -4 www.facebook.com
 
Tracing route to star.c10r.facebook.com [185.60.216.7]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  koyomi.aosake.net [192.168.102.1]
  2    24 ms    21 ms    22 ms  173-228-7-1.dsl.static.fusionbroadband.com [173.228.7.1]
  3    21 ms    21 ms    20 ms  gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
  4    40 ms    32 ms    32 ms  ae2.cr2.lsatca11.sonic.net [50.0.79.178]
  5    21 ms    21 ms    31 ms  50.ae4.gw.pao1.sonic.net [142.254.58.158]
  6    21 ms    21 ms    20 ms  ae2.0.gw.equinix-sj.sonic.net [50.0.2.14]
  7    21 ms    21 ms    21 ms  sv1.pr02.tfbnw.net [206.223.116.153]
  8    22 ms    21 ms    22 ms  po102.psw01a.sjc2.tfbnw.net [74.119.77.249]
  9     *        *        *     Request timed out.
 10    21 ms    21 ms    22 ms  185.60.216.7
 
Trace complete.
 

I forced the IPv4 trace because my system will go to FB via IPv6 if I don't:
C:\utils\dig>tracert www.facebook.com
 
Tracing route to star.c10r.facebook.com [2a03:2880:f022:6:face:b00c:0:2]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  1000-0000-0000-0000-09d7-04ed-a420-2062.6rd.ip6.sonic.net [2602:24a:de40:7d90::1]
  2    21 ms    22 ms    22 ms  cust-gw.ipv6.sonic.net [2602:24b:8179:10::1]
  3    86 ms    22 ms    22 ms  201.ge-6-1-1.gw.equinix-sj.sonic.net [2001:5a8:5:e::1]
  4    28 ms    22 ms    22 ms  sv1.br01.sjc1.tfbnw.net [2001:504:0:1:0:3:2934:1]
  5    22 ms    22 ms    22 ms  po101.psw01c.sjc2.tfbnw.net [2620:0:1cff:dead:bef0::bd]
  6    22 ms    23 ms    22 ms  po3.msw1af.01.sjc2.tfbnw.net [2a03:2880:f022:ffff::73]
  7    23 ms    22 ms    23 ms  edge-star6-shv-01-sjc2.facebook.com [2a03:2880:f022:6:face:b00c:0:2]
 
Trace complete.
 

To add: I have my ISP DNS servers configured; in addition Google's IPv6 DNS servers:

75.101.19.196- Sonic.net
75.101.19.228- Sonic.net
2001:4860:4860::8888- Google
2001:4860:4860::8844- Google
 

Mia
@72.193.53.x

Mia to odog

Anon

to odog
Vegas also
traceroute to facebook.com (173.252.120.6), 30 hops max, 60 byte packets
1 (Modem) 0.920 ms 1.069 ms 1.237 ms
2 10.72.0.1 (10.72.0.1) 7.974 ms 12.384 ms 12.397 ms
3 24-234-16-232.ptp.lvcm.net (24.234.16.232) 12.724 ms 12.770 ms 12.804 ms
4 24-234-6-28.ptp.lvcm.net (24.234.6.28) 13.607 ms 13.628 ms 13.652 ms
5 sanjbprj02-ae0.0.rd.sj.cox.net (68.1.5.186) 33.242 ms 33.580 ms 33.233 ms
6 ae22.pr04.sjc1.tfbnw.net (103.4.96.106) 26.332 ms ae27.pr03.sjc1.tfbnw.net (103.4.98.54) 29.139 ms 28.944 ms
7 ae1.bb03.sjc1.tfbnw.net (31.13.26.160) 22.007 ms 22.453 ms ae3.bb04.sjc1.tfbnw.net (31.13.26.166) 21.508 ms
8 ae29.bb02.sjc1.tfbnw.net (74.119.76.218) 26.003 ms ae15.pr01.ord1.tfbnw.net (74.119.77.74) 25.828 ms 25.857 ms
9 be16.bb01.frc3.tfbnw.net (31.13.24.28) 95.540 ms be16.bb02.frc3.tfbnw.net (31.13.24.42) 96.295 ms be16.bb01.frc3.tfbnw.net (31.13.24.28) 95.432 ms
10 ae60.dr02.frc3.tfbnw.net (74.119.79.9) 93.012 ms ae60.dr03.frc3.tfbnw.net (74.119.79.11) 88.232 ms ae61.dr03.frc3.tfbnw.net (173.252.64.65) 94.609 ms
11 * * *
12 * * *
13 edge-star-shv-12-frc3.facebook.com (173.252.120.6) 89.440 ms 92.138 ms 92.201 ms

Phone via sprint is an immediate open. Can not open in computer via cox...

billaustin
they call me Mr. Bill
MVM
join:2001-10-13
North Las Vegas, NV

billaustin

MVM

I get a similar traceroute, but it comes up on my PC with no issues.

Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 15 ms 7 ms 7 ms 10.104.0.1
3 9 ms 8 ms 9 ms 24-234-16-208.ptp.lvcm.net [24.234.16.208]
4 8 ms 8 ms 9 ms 24-234-6-68.ptp.lvcm.net [24.234.6.68]
5 30 ms 28 ms 29 ms sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]
6 21 ms 21 ms 21 ms ae22.pr04.sjc1.tfbnw.net [103.4.96.106]
7 31 ms 31 ms 29 ms ae3.bb04.sjc1.tfbnw.net [31.13.26.166]
8 29 ms 29 ms 29 ms ae30.bb02.sjc1.tfbnw.net [74.119.78.46]
9 91 ms 91 ms 90 ms be16.bb02.frc3.tfbnw.net [31.13.24.42]
10 87 ms 87 ms 88 ms ae61.dr03.frc3.tfbnw.net [173.252.64.65]
11 * * * Request timed out.
12 * * * Request timed out.
13 90 ms 90 ms 89 ms edge-star-shv-12-frc3.facebook.com [173.252.120.6]

Trace complete.

Mia
@72.193.53.x

Mia

Anon

Have had access to Facebook for severl hours, but not good Facebook acess last several weeks. We see again later and tomorrow, maybe same fail...
Mia

Mia to billaustin

Anon

to billaustin
Have had access to Facebook for several hours, but not good Facebook access last several weeks. We see again later and tomorrow, maybe same fail...
ChrisBurch
join:2002-02-03
San Diego, CA

ChrisBurch to namida12

Member

to namida12
I've had similar issues with facebook over the past week. It's been very unreliable on my computer and almost unusable on my phone. Once I disable the wifi, it works fine.
balut76
join:2011-09-27
Las Vegas, NV

balut76 to Mia

Member

to Mia
Same exact issue here. Cox Las Vegas, either can't access Facebook, or it will load but no icons or updates, or it will get stuck trying to load.

tracert www.facebook.com

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

1 1 ms 1 ms 1 ms www.routerlogin.com [192.168.1.1]
2 7 ms 6 ms 6 ms 10.89.128.1
3 7 ms 9 ms 19 ms 24-234-8-128.ptp.lvcm.net [24.234.8.128]
4 8 ms 9 ms 11 ms 24-234-6-232.ptp.lvcm.net [24.234.6.232]
5 30 ms 74 ms 30 ms sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]
6 33 ms 30 ms 30 ms ae27.pr03.sjc1.tfbnw.net [103.4.98.54]
7 30 ms 31 ms 30 ms po101.psw01b.sjc2.tfbnw.net [31.13.31.17]
8 * * * Request timed out.
9 33 ms 33 ms 35 ms 185.60.216.7

Trace complete.
namida12
join:2004-10-30
Las Vegas, NV

namida12

Member

Facebook kinda loads this morning, but web page does not scroll or Icons on left and right are not working. Firefox will not open website. This is nuts, making Facebook almost useless.

traceroute Facebook.com
traceroute to Facebook.com (173.252.120.6), 30 hops max, 60 byte packets
1 TEW-639GR (192.168.10.1) 1.051 ms 1.426 ms 1.419 ms
2 10.72.0.1 (10.72.0.1) 8.181 ms 12.568 ms 12.763 ms
3 24-234-16-232.ptp.lvcm.net (24.234.16.232) 13.229 ms 13.422 ms 13.617 ms
4 24-234-6-28.ptp.lvcm.net (24.234.6.28) 13.814 ms 13.801 ms 13.589 ms
5 sanjbprj02-ae0.0.rd.sj.cox.net (68.1.5.186) 33.718 ms 33.905 ms 34.228 ms
6 ae22.pr04.sjc1.tfbnw.net (103.4.96.106) 26.698 ms 22.692 ms 22.652 ms
7 ae3.bb04.sjc1.tfbnw.net (31.13.26.166) 22.840 ms ae1.bb03.sjc1.tfbnw.net (31.13.26.160) 22.135 ms ae3.bb04.sjc1.tfbnw.net (31.13.26.166) 23.196 ms
8 ae18.bb01.sjc1.tfbnw.net (74.119.77.74) 26.391 ms ae30.bb02.sjc1.tfbnw.net (74.119.78.46) 26.584 ms 26.577 ms
9 be16.bb02.frc3.tfbnw.net (31.13.24.42) 96.167 ms 95.952 ms be16.bb01.frc3.tfbnw.net (31.13.24.28) 93.301 ms
10 ae60.dr02.frc3.tfbnw.net (74.119.79.9) 93.695 ms ae60.dr01.frc3.tfbnw.net (204.15.23.247) 90.111 ms ae60.dr02.frc3.tfbnw.net (74.119.79.9) 93.824 ms
11 * * *
12 * * *
13 edge-star-shv-12-frc3.facebook.com (173.252.120.6) 93.234 ms 97.741 ms 97.526 ms

MarkRH
Premium Member
join:2005-02-08
Edmond, OK
ARRIS BGW210-700
ARRIS TM3402
Asus RT-AC68

MarkRH to namida12

Premium Member

to namida12
Facebook has been fine for me yesterday and today. Here's my traceroute:
Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     7 ms     6 ms     7 ms  10.2.0.1
  3     8 ms     9 ms     7 ms  COX-68-12-10-90-static.coxinet.net [68.12.10.90]
  4    11 ms     8 ms     9 ms  COX-68-12-8-12-static.coxinet.net [68.12.8.12]
  5    23 ms    23 ms    25 ms  mtc3dsrj02-ae4.0.rd.ok.cox.net [68.12.14.2]
  6    25 ms    29 ms    29 ms  68.1.2.121
  7    12 ms    13 ms    13 ms  ip70-167-150-182.at.at.cox.net [70.167.150.182]
  8    59 ms    59 ms    59 ms  be2.bb01.dfw1.tfbnw.net [31.13.29.192]
  9    49 ms    49 ms    47 ms  ae18.bb01.atl1.tfbnw.net [204.15.21.50]
 10    54 ms    59 ms    55 ms  be17.bb01.frc3.tfbnw.net [31.13.24.30]
 11    56 ms    55 ms    55 ms  ae60.dr04.frc3.tfbnw.net [74.119.79.29]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    53 ms    54 ms    53 ms  edge-star-shv-12-frc3.facebook.com [173.252.120.6]
 

Trace complete.
namida12
join:2004-10-30
Las Vegas, NV

namida12

Member

Click for full size
web page is an On and off situation since 3 PM today, but my lady is still not very happy...

Another traceroute tool

JR
korstj
join:2000-08-26
San Diego, CA

korstj to namida12

Member

to namida12
Your DNS is resolving Facebook to an IP address hosted at their server farm in Forest City, North Carolina. If you look above, some people are resolving to a San Jose IP address. You could try using that IP address (185.60.216.7) by making a hosts entry for facebook.com and see if that improves your situation. I suspect you may have more going on than just this, but at any rate this will speed things up regardless.

Also, just to note.. the 2 hops you see in your traceroute that do not relay back information (***) are not an indication of a problem. Those are just simply nodes in the path to their servers that are on internal IP addressing. They cannot send a response, but they can increment TTL and forward.

WiFiguru
To infinity... and beyond
Premium Member
join:2005-06-21
Seattle, WA

WiFiguru to namida12

Premium Member

to namida12
Just to add in, i've noticed slowness with Facebook as well here in Irvine. It especially is slow-to-load when I open up messages, or load more than the "initial page".

WiFiguru
Lerxst2112
join:2006-05-11
Cedar Park, TX

1 edit

Lerxst2112 to namida12

Member

to namida12
Facebook has been completely unusable at times for the last few weeks. There are times that it's fine, but it's hit or miss.

Edit: Been unusable for an hour or so. Tried switching to a VPN on the same computer and it's fine.
namida12
join:2004-10-30
Las Vegas, NV

namida12 to korstj

Member

to korstj
Wow, (185.60.216.7) brings up the webpage very rapidly, but no icons. second time icons but they are non functioning. Lower left of the browser indicated it is waiting for Facebook. 4 minutes later it finally opened a game. Lady is now happy, she left in a huff to make tea.