Skipping Like A Japanese Schoolgirl

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 12:27 am

So, everyone has been complaining about me skipping around these days, but no one knows how to fix it. I've been trying to find a solution for two weeks now to no avail. I'm absolutely sure it's not my in-game rates because any combination still results in me skipping everywhere. Everything on my screen is smooth to me except maybe switching between guns sometimes, but my ping often spikes between the usual 60-90 up to the 200s sometimes.

I called my ISP and they upgraded my modem. I am on a wired connection. I get 55down when I'm connected directly to the modem, so I think my router is throttling it to ~35down. That's still more than enough bandwidth though. I still skip around when directly connected to the modem with 55down, too. Pingtest results can sometimes be in the 80s with ~70ms variance (to an LA, from SF). This happens even when no one in the house is downloading or streaming anything.

I'm about to try reinstalling DoD, but I highly doubt it will have any effect since the same lag issues happen in every other program that accesses the internet (Vent, Diablo 3, etc.). Fix it and I'll be eternally grateful. Let me know if you need more information.

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 5:05 am

Hmm... beas might've help me fix it. Bad ethernet cable apparently. I'll leave this here in case the problem persists.

Joey · Post by **Joey** » Sat May 11, 2013 5:24 am

SoCal Dustin needs a solution too

avenger · Post by **avenger** » Sat May 11, 2013 8:42 am

hmm i wonder if this will fix my skipping. kind of annoying being told to fix my rates every 2 seconds.

Tin Bad · Post by **Tin Bad** » Sat May 11, 2013 9:24 am

avenger wrote:hmm i wonder if this will fix my skipping. kind of annoying being told to fix my rates every 2 seconds.

FIX YOUR RATES SEAN!!!

stile · Post by **stile** » Sat May 11, 2013 9:28 am

Bay Area Internet sucks.

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 1:10 pm

aLpha.cn-[tang] wrote:Hmm... beas might've help me fix it. Bad ethernet cable apparently. I'll leave this here in case the problem persists.

So... it was fine after I had swapped out the cable last night. I was pubbing for about 30 minutes and it was still fine until about 10 minutes ago when I started to notice huge spikes in my netgraph again.

dogfire · Post by **dogfire** » Sat May 11, 2013 3:16 pm

Did your ISP run any signal/power tests on your modem?

Check this article out. It's old but it does a good job at explaining the basics of downstream/upstream power and signal to noise ratios.

http://www.speedguide.net/articles/cabl ... evels-1197

EDIT: If you know the modem's model number I can probably show you how to check the levels yourself.

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 5:00 pm

dogfire wrote:Did your ISP run any signal/power tests on your modem?

Check this article out. It's old but it does a good job at explaining the basics of downstream/upstream power and signal to noise ratios.

http://www.speedguide.net/articles/cabl ... evels-1197

EDIT: If you know the modem's model number I can probably show you how to check the levels yourself.

Ubee U10C035.30.
When I first complained to my ISP, they had me upgrade my old Motorola modem to this one (some upgrade from DOCSIS 2 to DOCSIS 3 or something?).

chaos · Post by **chaos** » Sat May 11, 2013 5:18 pm

take a look at your jitter..its 22ms...wayyyyyyyyyyyyyyyy to high..should be a hell of alot lower..thats your problem

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 5:26 pm

chaos wrote:take a look at your jitter..its 22ms...wayyyyyyyyyyyyyyyy to high..should be a hell of alot lower..thats your problem

The jitter gets to about 100 sometimes when it gets really bad. I'm aware this is the problem. I'm trying to figure out why it happens.

motive · Post by **motive** » Sat May 11, 2013 6:25 pm

Just a guess, but this has fixed some very odd network problems in several games for me.

Start > Programs > Accessories, right-click on Command Prompt and run as administrator.

Run this command:

Code: Select all

netsh interface ipv4 set subinterface "Local Area Connection" mtu=2000 store=persistent

If your network adapter that connects you to the internet has a different name than "Local Area Connection" you'll have to change it appropriately.

You can try changing the MTU to higher numbers, maybe in increments of 1000. If you get to 10k - 15k and nothing is changed I'd say it's a dead end.

Jakimo · Post by **Jakimo** » Sat May 11, 2013 7:08 pm

if changing ethernet cables helps anything, someone should probably contact westy

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 7:26 pm

motive wrote:Just a guess, but this has fixed some very odd network problems in several games for me.

Start > Programs > Accessories, right-click on Command Prompt and run as administrator.

Run this command:
Code: Select all
netsh interface ipv4 set subinterface "Local Area Connection" mtu=2000 store=persistent
If your network adapter that connects you to the internet has a different name than "Local Area Connection" you'll have to change it appropriately.

You can try changing the MTU to higher numbers, maybe in increments of 1000. If you get to 10k - 15k and nothing is changed I'd say it's a dead end.

This did not work. Still skipping.

Gorillabc · Post by **Gorillabc** » Sat May 11, 2013 7:33 pm

Hope you get it working like it was early this morning Andy, was nice seeing you move in a server and not skip like an old Leann Rimes CD. Just want to post this here because I was quite surprised and am quite proud of my middle of the nowhere internet connection. Never done pingtest before and I'm quite happy with the results.

The biggest problem I have is my routing. I have garbage routing to everywhere. For example, I was in vent with a Euro one night (forget which one). We both did tracerts to my Dallas NFO. I got 14 hops, he got 6. That's pretty ridiculous. Is there anything I can even do about that?

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 8:03 pm

I'm pretty sure it's not a router-related problem since this is what my connection looks like directly connected to the modem. If that's true, it would either be my computer settings or a line problem. I ran the computer in safe mode with all the startup applications disabled. I only ran vent, steam, and dod and I was still skipping with packet loss (1-5) every couple of seconds. You can see below that I'm not actually getting any packet loss.

Code: Select all

Ping statistics for 208.113.155.9:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 155ms, Average = 94ms

I accessed the modem control panel and here's the Downstream and Upstream panels.

According to this, downstream SNR (MxMER, I assume) is >30. Downstream power level is between -8 and 8. I don't see upstream SNR, but upstream power is <55. So, given that the information in that link is accurate, I should theoretically have a solid connection. I'm calling the ISP right now to hopefully have them send a tech out.

chaos · Post by **chaos** » Sat May 11, 2013 8:24 pm

i belive andy has shitty cable internet like i do that doesent have enough bandwith..just like me..i run like a 150-200 ping in servers after 5pm that eayler in the day i might run a 30 to..call your isp and tell them your going to gangrape them..problem solved

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sat May 11, 2013 8:33 pm

(I tested it five minutes ago and I was getting 50 ping and 40+ jitter to a server less than 10 miles away.)

The ISP is sending a tech out, but if anyone still has any suggestions in the meantime, let me know.

chaos · Post by **chaos** » Sat May 11, 2013 9:09 pm

get off the comcast cable and get dsl...much better sometimes

paintball_ · Post by **paintball_** » Sat May 11, 2013 9:23 pm

Your Jitter should be around 0. That explains why your skipping... Because your ping is spiking. It's not the router if you get spikes when directly connected to the modem. Although a new modem should of fixed your problem lol. If you can't fix it just keep the skip, as long as you keep picking me on your team in 12 mans

nunz · Post by **nunz** » Sat May 11, 2013 9:41 pm

avenger wrote:hmm i wonder if this will fix my skipping. kind of annoying being told to fix my rates every 2 seconds.

all i could think of was u while reading this.

avenger · Post by **avenger** » Sat May 11, 2013 11:26 pm

nunz wrote:
avenger wrote:hmm i wonder if this will fix my skipping. kind of annoying being told to fix my rates every 2 seconds.
all i could think of was u while reading this.

stile · Post by **stile** » Sat May 11, 2013 11:59 pm

To a server in my own city. Get on my level.

mike · Post by **mike** » Sun May 12, 2013 12:06 am

My ping test to Chicago

My ping test to Brooklyn

dogfire · Post by **dogfire** » Sun May 12, 2013 12:55 am

aLpha.cn-[tang] wrote:I'm pretty sure it's not a router-related problem since this is what my connection looks like directly connected to the modem. If that's true, it would either be my computer settings or a line problem. I ran the computer in safe mode with all the startup applications disabled. I only ran vent, steam, and dod and I was still skipping with packet loss (1-5) every couple of seconds. You can see below that I'm not actually getting any packet loss.
Code: Select all
Ping statistics for 208.113.155.9:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 155ms, Average = 94ms
I accessed the modem control panel and here's the Downstream and Upstream panels.

According to this, downstream SNR (MxMER, I assume) is >30. Downstream power level is between -8 and 8. I don't see upstream SNR, but upstream power is <55. So, given that the information in that link is accurate, I should theoretically have a solid connection. I'm calling the ISP right now to hopefully have them send a tech out.

Yeah from what your modem is reporting everything looks good. My guess is that the issues that you're having are unfortunately not under your control. Test your network connection on another computer just to make sure. If you get the same issue the only real thing you can do is bitch until someone fixes it.

reddogg · Post by **reddogg** » Sun May 12, 2013 3:27 am

Boycotting all Dallas servers

CharlieGiteau · Post by **CharlieGiteau** » Sun May 12, 2013 4:34 am

My ping test results came out really well except for SF (all grade A's with max 1 jitter). Thing is, I'm having a lot of loss and choke in public servers only. Chicago, NY, and Dallas came out really well, FL could've been a bit better though. I'm hardwired into my router, perhaps wiring into my modem would be better?

Edit: I have RoadRunner like Reddogg, but apparently its better in SW Ohio.

mogers · Post by **mogers** » Sun May 12, 2013 8:08 am

If you're not skipping on your side then who cares. Just make everyone mad and shit on them. Per the usual.

mogers · Post by **mogers** » Sun May 12, 2013 8:10 am

Cage · Post by **Cage** » Sun May 12, 2013 8:14 am

Still 150-200 ping

chaos · Post by **chaos** » Sun May 12, 2013 9:14 am

talk to traiz andy he had that bad comcast where your at and got something alot better for awile...dono what but it made him amazing

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sun May 12, 2013 12:27 pm

mogers wrote:If you're not skipping on your side then who cares. Just make everyone mad and shit on them. Per the usual.

I'd say it's smooth 85% of the time and the other 15% is just me spiking to 200 ping and my screen actually freezing and unfreezing. There are other small, but noticeable moments when I'm switching guns and the animation (or my model) will rubberband a little. The same thing happens in other games, too.

Maybe it'll even fix the fact that I can't ever hit anything. Ever.

chaos wrote:talk to traiz andy he had that bad comcast where your at and got something alot better for awile...dono what but it made him amazing

I don't think switching ISPs is really feasible atm. Hopefully, this tech that's coming today will actually fix the problem or, at least, tell me what the problem is. Thanks though.

moosh wrote:I have the same internet as you in the same market. You shouldn't be having problems.

Who says I live near you? No one. That's who.

SoCal-Dustin · Post by **SoCal-Dustin** » Sun May 12, 2013 12:36 pm

im also very skippy and choppy up the ass to other people..

stile · Post by **stile** » Sun May 12, 2013 12:55 pm

Post what the tech says. I'm interested in what he will say.

Sears · Post by **Sears** » Sun May 12, 2013 1:03 pm

So my internet is terrible and I'm on wireless and can hardly reach the the modem from where my office/computer is located, and this is this what I got...

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sun May 12, 2013 2:03 pm

stile wrote:Post what the tech says. I'm interested in what he will say.

So I showed him all of my recent pingtest results, the following being the worst:

He checked bandwidth at speedtest.comcast.net and my ping was consistently under 15ms (bandwidth was normal, too) despite the jitter on pingtest at the time was ~10ms to an SF server. He checked the line for noise outside the apartment complex and inside the apartment and he said everything was fine. I asked if he's encountered this same problem in the area, but he hadn't. I asked if he knew of any possible solutions to the problem and he said no. He said that Comcast can only guarantee that the bandwidth is there and the ping at their site was pretty consistently low. He pretty much said that Comcast will tell you that, when it comes to ping variance, it is not responsible for the rest of the internet.

He did replace all the wall connections. Hopefully, it'll make a difference. Otherwise, back to square one.

Here are traceroutes to New York, Chicago, and Dallas servers, respectively.

New York

Code: Select all

Pinging renamed.game.nfoservers.com [192.223.24.249] with 32 bytes of data:
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=98ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=117ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=81ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=84ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=82ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=85ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115
Reply from 192.223.24.249: bytes=32 time=83ms TTL=115

Ping statistics for 192.223.24.249:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 81ms, Maximum = 117ms, Average = 84ms

Tracing route to renamed.game.nfoservers.com [192.223.24.249]
over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    36 ms    16 ms    41 ms  
  3    11 ms    10 ms    11 ms  te-7-8-ur01.oakland.ca.sfba.comcast.net [68.86.1
42.89]
  4    13 ms    11 ms    11 ms  te-0-11-0-13-ar01.sfsutro.ca.sfba.comcast.net [6
9.139.199.78]
  5    18 ms    23 ms    22 ms  he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.91.229]
  6    13 ms    28 ms    12 ms  er1-tengig2-4.sanjoseequinix.savvis.net [206.24.
222.1]
  7    66 ms    33 ms    27 ms  er2-xe-7-0-0.SanJoseEquinix.savvis.net [204.70.1
98.142]
  8    16 ms    53 ms    15 ms  cr2-tengig0-7-3-0.sanfrancisco.savvis.net [204.7
0.206.57]
  9    98 ms    83 ms    85 ms  cr2-tengig-0-15-0-0.NewYork.savvis.net [204.70.1
96.118]
 10    83 ms    83 ms    82 ms  er2-tengig-8-8.newyork.savvis.net [204.70.224.24
9]
 11    83 ms    82 ms    83 ms  208.173.129.62
 12    84 ms    87 ms    85 ms  border1.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.
14]
 13    82 ms    85 ms    83 ms  c-192-223-24-249.internap-nyc.nfoservers.com [19
2.223.24.249]

Trace complete.

Chicago

Code: Select all

Pinging xmvc.game.nfoservers.com [72.5.195.119] with 32 bytes of data:
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=81ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=80ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=67ms TTL=52
Reply from 72.5.195.119: bytes=32 time=66ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=66ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=67ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=66ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=80ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=77ms TTL=52
Reply from 72.5.195.119: bytes=32 time=95ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52
Reply from 72.5.195.119: bytes=32 time=67ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=65ms TTL=52
Reply from 72.5.195.119: bytes=32 time=64ms TTL=52

Ping statistics for 72.5.195.119:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 64ms, Maximum = 95ms, Average = 67ms

Tracing route to xmvc.game.nfoservers.com [72.5.195.119]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    22 ms    29 ms    26 ms  
  3    26 ms    12 ms    10 ms  te-7-8-ur01.oakland.ca.sfba.comcast.net [68.86.1
42.89]
  4    43 ms    15 ms    11 ms  te-0-11-0-13-ar01.sfsutro.ca.sfba.comcast.net [6
9.139.199.78]
  5    23 ms    23 ms    35 ms  he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.91.229]
  6    16 ms    13 ms    12 ms  er1-tengig2-4.sanjoseequinix.savvis.net [206.24.
222.1]
  7    13 ms    13 ms    13 ms  er2-xe-11-3-0.SanJoseEquinix.savvis.net [204.70.
198.146]
  8    14 ms    15 ms    13 ms  cr2-tenge-0-5-0-2.sanfrancisco.savvis.net [204.7
0.200.198]
  9    65 ms    66 ms    66 ms  cr2-tengig-0-7-0-0.chicago.savvis.net [204.70.19
6.246]
 10    64 ms    63 ms    63 ms  ber2-te-4-0-1.chicagoequinix.savvis.net [204.70.
195.118]
 11    66 ms    83 ms    96 ms  208.173.180.134
 12    64 ms    65 ms    64 ms  border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
 13    65 ms    64 ms    65 ms  c-72-5-195-119.managed-vds.internap-chicago.nfos
ervers.com [72.5.195.119]

Trace complete.

Dallas

Code: Select all

Pinging dreamliner.game.nfoservers.com [66.150.214.122] with 32 bytes of data:
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=59ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=87ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=58ms TTL=52
Reply from 66.150.214.122: bytes=32 time=63ms TTL=52
Reply from 66.150.214.122: bytes=32 time=70ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=59ms TTL=52
Reply from 66.150.214.122: bytes=32 time=58ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=58ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=89ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=58ms TTL=52
Reply from 66.150.214.122: bytes=32 time=58ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=95ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=56ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52
Reply from 66.150.214.122: bytes=32 time=57ms TTL=52

Ping statistics for 66.150.214.122:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 95ms, Average = 59ms

Tracing route to dreamliner.game.nfoservers.com [66.150.214.122]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    26 ms    27 ms    29 ms  76.21.28.1
  3    16 ms    10 ms    14 ms  te-7-8-ur01.oakland.ca.sfba.comcast.net [68.86.1
42.89]
  4    12 ms    27 ms    15 ms  te-0-2-0-3-ar01.sfsutro.ca.sfba.comcast.net [68.
85.154.214]
  5    21 ms    34 ms    24 ms  he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.90.157]
  6    20 ms    13 ms    13 ms  pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.86.122]
  7    14 ms    13 ms    28 ms  te0-0-0-12.ccr21.sjc04.atlas.cogentco.com [154.5
4.13.17]
  8    16 ms    15 ms    13 ms  be2017.mpd21.sfo01.atlas.cogentco.com [154.54.2.
165]
  9    95 ms    92 ms    96 ms  te0-1-0-2.ccr22.mci01.atlas.cogentco.com [154.54
.30.70]
 10    97 ms   112 ms   100 ms  te0-5-0-7.ccr21.dfw01.atlas.cogentco.com [154.54
.85.158]
 11    92 ms    93 ms    90 ms  te0-5-1-0.ccr21.dfw03.atlas.cogentco.com [154.54
.82.30]
 12    58 ms    58 ms    57 ms  38.104.204.74
 13    57 ms    73 ms    59 ms  border1.ge4-1-bbnet2.ext1a.dal.pnap.net [216.52.
191.84]
 14    57 ms    57 ms    55 ms  c-66-150-214-122.internap-dallas.nfoservers.com
[66.150.214.122]

Trace complete.

Sears wrote:So my internet is terrible and I'm on wireless and can hardly reach the the modem from where my office/computer is located, and this is this what I got...

=] .sraeS, flesruoy kcuf oG

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sun May 12, 2013 5:08 pm

So, I think I've narrowed it down to a modem problem--correct me if I'm wrong. As I mentioned before, they recently had me swap out my old Motorola DOCSIS 2.0 modem for a Ubee DOCSIS 3.0 modem, which was most likely previously used and/or refurbished.

I've been tracking my ping using PingPlotter in 10 minute intervals. The following are graphs for New York, Chicago, and Dallas servers, respectively, again.

In all of those charts, the ping deviation at the second hop (modem) is enormous. Apparently, Comcast customer service said they couldn't give me a brand new one from corporate and couldn't guarantee I'd get a brand new one at their local office. I'm taking the modem in tomorrow and, hopefully, not get a shitty one in return.

Post by **BoxeR** » Sun May 12, 2013 5:32 pm

No clue why my jitter is so high to Dallas when I'm pretty close to it...

Sears · Post by **Sears** » Sun May 12, 2013 5:42 pm

http://www.newegg.com/Product/Product.a ... 6825390001

willeh · Post by **willeh** » Sun May 12, 2013 5:44 pm

I had the same problem a couple years ago with my comcast. It took about 2 months, it had to do with too many amplifiers going into my house.

dogfire · Post by **dogfire** » Sun May 12, 2013 7:42 pm

Have you tried to play DoD on a different computer? Pretty much an essential diagnostic step.

aLpha.cn-[tang] · Post by **aLpha.cn-[tang]** » Sun May 12, 2013 7:56 pm

dogfire wrote:Have you tried to play DoD on a different computer? Pretty much an essential diagnostic step.

This problem is not exclusive to my computer or DoD. I tracked pings on my netbook and a housemate's laptop both directly connected to the modem. The same thing happens.

ward · Post by **ward** » Sun May 12, 2013 8:23 pm

So half the community that can't get hit must be having the exact same problems! Mystery solved!

Katsato · Post by **Katsato** » Mon May 13, 2013 2:51 am

People on my team should know that I sometimes complain about my internet being bad. Now I have proof!

CharlieGiteau · Post by **CharlieGiteau** » Mon May 13, 2013 4:40 am

Katsato wrote:People on my team should know that I sometimes complain about my internet being bad. Now I have proof!

Call your ISP. That's just terrible. Unless you're not paying for it.

chaos · Post by **chaos** » Mon May 13, 2013 10:40 am

OR stealing it from nextdoor

Katsato · Post by **Katsato** » Mon May 13, 2013 10:53 am

CharlieGiteau wrote: Call your ISP. That's just terrible. Unless you're not paying for it.

They checked the line when I called said there was a problem but they fixed it from there end. They've told me that twice now. Think I should look into another ISP by now.