dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3472
share rss forum feed


Perhaps

@enitel.net.ni

[DSL] Dsl lag problem from 12pm until 10pm

Downloads run at max speed of 520kb consistently, the problem is when I try to play any games from 12pm to 10pm there are constant lag spikes. I have contacted my provider and they replaced the phone line from the house going to outside, new dsl modem, new phone jack. The line has been perfect for nearly 2 years, just about 1 month ago this issue started. Nothing works. I noticed the hec erors are at 306 right now only for upstream. Here is all the results

1.»/tweakr/block:···a=normal

2.»i.imgur.com/LzjbE.jpg 4.35mbps down 0.85mbps up

3. My ip address is not pingable 190.212.xx.xx

4.Dsl, Claro Nicaragua, Broadtech Adsl2+8186-V2

5.Dsl connection is always on no need to connect.

6. n/a

7. Max Osx Lion

8. 5mb down 1mb up

9. Direct connect to dsl modem

10. n/a


Irish Shark
Play Like A Champion Today
Premium,MVM
join:2000-07-29
Las Vegas, NV
kudos:5
• There is nothing to "tweak" since you are on Lion. OS X is self tuning like Vista, Win7 and Win8.

• Run a ping test to any of the game servers.

• Run a tracert to the same server.

• Open your MODEM/router page and see what the line specs are.

• Do the same as above when the issue starts.

Post what you get here.
--
"You can observe a lot by watching". Yogi Berra


perhaps

@enitel.net.ni
Battlenet doesn't allow their servers to be pinged.

traceroute to 12.129.206.130 (12.129.206.130), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.915 ms 1.841 ms 1.609 ms
2 1-64-212-190.enitel.net.ni (190.212.64.1) 21.991 ms 21.616 ms 22.072 ms
3 10.192.103.1 (10.192.103.1) 22.349 ms 22.546 ms 21.871 ms
4 63.245.90.9 (63.245.90.9) 67.973 ms 80.978 ms 68.045 ms
5 xe-0-0-1.usa.brx-teracore02.columbus-networks.com (63.245.5.67) 67.929 ms 68.058 ms 67.363 ms
6 12.250.187.5 (12.250.187.5) 70.099 ms 69.463 ms 69.472 ms
7 12.122.155.178 (12.122.155.178) 135.995 ms 134.102 ms 135.746 ms
8 cr2.ormfl.ip.att.net (12.122.1.45) 138.369 ms 135.241 ms 140.344 ms
9 cr1.ormfl.ip.att.net (12.122.5.185) 133.714 ms 133.360 ms 136.217 ms
10 cr2.hs1tx.ip.att.net (12.122.1.5) 137.325 ms * 139.075 ms
11 cr1.dlstx.ip.att.net (12.122.28.157) 134.739 ms 134.852 ms 135.393 ms
12 cr2.dlstx.ip.att.net (12.122.1.210) 136.101 ms 134.631 ms 135.496 ms
13 cr2.la2ca.ip.att.net (12.122.28.178) 134.852 ms 133.940 ms 135.663 ms
14 gar29.la2ca.ip.att.net (12.122.129.241) 131.588 ms 133.452 ms 131.855 ms
15 12-122-254-234.attens.net (12.122.254.234) 154.888 ms
12-122-254-238.attens.net (12.122.254.238) 147.803 ms 144.062 ms
16 mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 134.508 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 132.977 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 131.792 ms
17 * * *
18 * * *
19 * * *

device Info

Board ID: 96338A-122
Software Version: C111-312NIC-C01_R01
Bootloader (CFE) Version: 1.0.37-12.2-4
Wireless Driver Version: 4.170.16.0.cpe2.1sd
ADSL Version: A2pB023k.d20k_rc2

This information reflects the current status of your DSL connection.

Line Rate - Upstream (Kbps): 1021
Line Rate - Downstream (Kbps): 5120
LAN IPv4 Address: 192.168.1.1
Default Gateway: 190.212.64.1
Primary DNS Server: 8.8.8.8
Secondary DNS Server: 8.8.8.2

The Lag spikes are happening right now, it's 7:55pm my time which is 9:55 est. Everything stops at exactly 12am est or 10pm my time.

aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2
said by perhaps :

Battlenet doesn't allow their servers to be pinged.

traceroute to 12.129.206.130 (12.129.206.130), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.915 ms 1.841 ms 1.609 ms
2 1-64-212-190.enitel.net.ni (190.212.64.1) 21.991 ms 21.616 ms 22.072 ms
3 10.192.103.1 (10.192.103.1) 22.349 ms 22.546 ms 21.871 ms
4 63.245.90.9 (63.245.90.9) 67.973 ms 80.978 ms 68.045 ms
5 xe-0-0-1.usa.brx-teracore02.columbus-networks.com (63.245.5.67) 67.929 ms 68.058 ms 67.363 ms
6 12.250.187.5 (12.250.187.5) 70.099 ms 69.463 ms 69.472 ms
7 12.122.155.178 (12.122.155.178) 135.995 ms 134.102 ms 135.746 ms
8 cr2.ormfl.ip.att.net (12.122.1.45) 138.369 ms 135.241 ms 140.344 ms
9 cr1.ormfl.ip.att.net (12.122.5.185) 133.714 ms 133.360 ms 136.217 ms
10 cr2.hs1tx.ip.att.net (12.122.1.5) 137.325 ms * 139.075 ms
11 cr1.dlstx.ip.att.net (12.122.28.157) 134.739 ms 134.852 ms 135.393 ms
12 cr2.dlstx.ip.att.net (12.122.1.210) 136.101 ms 134.631 ms 135.496 ms
13 cr2.la2ca.ip.att.net (12.122.28.178) 134.852 ms 133.940 ms 135.663 ms
14 gar29.la2ca.ip.att.net (12.122.129.241) 131.588 ms 133.452 ms 131.855 ms
15 12-122-254-234.attens.net (12.122.254.234) 154.888 ms
12-122-254-238.attens.net (12.122.254.238) 147.803 ms 144.062 ms
16 mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 134.508 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 132.977 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 131.792 ms

The Lag spikes are happening right now, it's 7:55pm my time which is 9:55 est. Everything stops at exactly 12am est or 10pm my time.

From what you have gathered in the trace and based on where you're located, I would have to say that I don't see anything really "bad" in the times.

Hop #4 is where your ISP goes to their transit provider "Columbus Networks", then hop #6 is where it transitions to the AT&T network here in the states and stays there all the way to L.A. Ca. From what I can see, your ISP isn't doing anything wrong.

Does Battle Net have any other server locations? (I'm not a gamer).

For comparison purposes if you could do another trace route after the congestion disappears might shed some light.


Irish Shark
Play Like A Champion Today
Premium,MVM
join:2000-07-29
Las Vegas, NV
kudos:5
reply to Perhaps
It seems like everything that I have read is that there are tons of folks experiencing the same thing; and at the exact time as you.

That is really curious; I have not seen any resolutions to the issue.

Folks are pointing to AT&T as the problem.

So, it is not you or your ISP. Don't make any changes on your end. You can ask your ISP to look at the tracerts and ask them to contact AT&T.

Sorry, that is the best that I can do.
--
"You can observe a lot by watching". Yogi Berra


perhaps

@enitel.net.ni
reply to aguen
The time is now 2am Est and there is no lag at all. Unfortunately battlenet does not give an option to change the server, i stuck with what it is connecting to.

Here is another traceroute at 2am est.

traceroute to 12.129.206.130 (12.129.206.130), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.382 ms 2.135 ms 2.173 ms
2 1-64-212-190.enitel.net.ni (190.212.64.1) 22.591 ms 22.191 ms 22.133 ms
3 10.192.103.1 (10.192.103.1) 22.172 ms 21.763 ms 22.687 ms
4 63.245.90.9 (63.245.90.9) 67.872 ms 132.335 ms 67.471 ms
5 xe-1-0-1.usa.brx-teracore02.columbus-networks.com (63.245.5.79) 67.080 ms 66.851 ms 66.999 ms
6 12.250.187.5 (12.250.187.5) 69.094 ms 68.537 ms 68.560 ms
7 12.122.155.178 (12.122.155.178) 134.609 ms 133.618 ms 132.963 ms
8 cr2.ormfl.ip.att.net (12.122.1.45) 163.206 ms 135.001 ms 131.834 ms
9 cr1.ormfl.ip.att.net (12.122.5.185) 133.877 ms 133.889 ms 136.712 ms
10 cr2.hs1tx.ip.att.net (12.122.1.5) 133.058 ms 133.679 ms 132.210 ms
11 cr1.dlstx.ip.att.net (12.122.28.157) 134.037 ms 133.493 ms 131.834 ms
12 cr2.dlstx.ip.att.net (12.122.1.210) 135.437 ms 134.645 ms 134.320 ms
13 cr2.la2ca.ip.att.net (12.122.28.178) 132.002 ms 132.201 ms 132.167 ms
14 gar29.la2ca.ip.att.net (12.122.129.241) 130.264 ms 363.951 ms 129.117 ms
15 12-122-254-238.attens.net (12.122.254.238) 130.705 ms
12-122-254-234.attens.net (12.122.254.234) 130.545 ms
12-122-254-238.attens.net (12.122.254.238) 131.023 ms
16 mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 130.594 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 129.907 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 130.731 ms
17 * * *
18 * * *

aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2
reply to Perhaps
Well, just a quick look at these times indicates that there is little to no real difference in response times in the path as far as we are allowed to see into it. Supposition would be that any lag would be on the server itself or something traffic related that cannot be seen with just a trace route.


perhaps

@enitel.net.ni
Ok thanks for all of your help, I'll keep contacting blizzard and see if they can tell me anything. I found on another forum it seems like all of Central America is being affected. I'm glad to know it's not just me. »us.battle.net/wow/en/forum/topic···age=5#90

aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2
reply to Perhaps
without more details from the other folks being impacted, it's not possible to even guess at a "common" cause other than something at the server side of the connection.