Puzzling and weird latency issue.

[Rickster]

Ok short and sweet, I have a 2meg line with a 1meg account with AH, I do have a spare account that I use when the internet is being destroyed by youtube and phone updates, so when I see the internet getting slow I dial in the second account but I see crazy pings. How is this possible if im on a different network?

Here are some traceroutes when im on the dialed up account.

PS C:\WINDOWS\system32> ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=1683ms TTL=64
Reply from 155.239.255.250: bytes=32 time=1730ms TTL=64
Reply from 155.239.255.250: bytes=32 time=1636ms TTL=64
Reply from 155.239.255.250: bytes=32 time=1748ms TTL=64

Ping statistics for 155.239.255.250:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1636ms, Maximum = 1748ms, Average = 1699ms
PS C:\WINDOWS\system32> tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.10.169]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2  1601 ms  1501 ms  1318 ms  cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]
  3  1238 ms   508 ms   190 ms  196.38.73.85
  4   902 ms  1220 ms  1470 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
  5  1821 ms  1563 ms  1561 ms  core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
  6  1723 ms     *     1228 ms  196.26.0.130
  7   873 ms   783 ms   862 ms  cloudflare.ixp.joburg [196.46.25.198]
  8   915 ms   972 ms   972 ms  104.20.10.169

Trace complete.
PS C:\WINDOWS\system32> tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.10.169]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2  1433 ms   984 ms  1177 ms  cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]
  3  1163 ms  1090 ms  1313 ms  196.38.73.85
  4   206 ms    83 ms   203 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
  5   341 ms   888 ms  1175 ms  core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
  6  1517 ms  1961 ms  1777 ms  196.26.0.130
  7  1893 ms  1869 ms  1685 ms  cloudflare.ixp.joburg [196.46.25.198]
  8  1356 ms  1393 ms  1394 ms  104.20.10.169

Killing the wifi brings the pings back to normal.


Please help me with this guys, its really bothering me because it doesnt make any sense.

 

[PPLdude]

Have you/are you connected via cable?

edit

1 * * * Request timed out.

How is this timing out? Isn't the 1st response from your local router?

 

[HavocXphere]

Best guess is you've got some device connected on wifi downloading stuff. On a 2 meg line thats enough to kill the pipe's latency. If the physical ADSL link is maxed then it doesn't matter what you dial in...its going to be kark.

Also...jirre man...that post is flippen incoherent as fk. You mention two accounts, don't even bother telling us what provider the second one is then post some arbitrary ping to only one of the two??? Oh and then randomly throw in a wifi comment. How do you expect anyone to deduce something meaningful from that? Garbage in, garbage out. But yeah try and disconnect wifi devices one by one till it goes away...maybe I deduced the answer correctly.

 

[irBosOtter]

Also ping your router and see if the latency is on your internal network perhaps, could be router causing it for some reason

 

[Rickster]

Best guess is you've got some device connected on wifi downloading stuff. On a 2 meg line thats enough to kill the pipe's latency. If the physical ADSL link is maxed then it doesn't matter what you dial in...its going to be kark.

Did you even read?

If the router has a 1meg account then I should have 1meg of my own Internet via dial in.

Main account is AH and second is IS

 

[HavocXphere]

Did you even read?

I attempted it, but as I said:

that post is flippen incoherent as fk.

Try what I said - disconnect wifi devices one by one. You'll see I'm right - one of them is downloading heavily - heavily enough to fk with your latency on the physical line, but not 100% of the time which will get you inconsistent patterns exactly like you're seeing - high latency with random OK ones.

1 * * * Request timed out.
2 1601 ms 1501 ms 1318 ms cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]
3 1238 ms 508 ms 190 ms 196.38.73.85
4 902 ms 1220 ms 1470 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 1821 ms 1563 ms 1561 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 1723 ms * 1228 ms 196.26.0.130
7 873 ms 783 ms 862 ms cloudflare.ixp.joburg [196.46.25.198]
8 915 ms 972 ms 972 ms 104.20.10.169

Trace complete.
PS C:\WINDOWS\system32> tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.10.169]
over a maximum of 30 hops:

1 * * * Request timed out.
2 1433 ms 984 ms 1177 ms cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]
3 1163 ms 1090 ms 1313 ms 196.38.73.85
4 206 ms 83 ms 203 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 341 ms 888 ms 1175 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 1517 ms 1961 ms 1777 ms 196.26.0.130
7 1893 ms 1869 ms 1685 ms cloudflare.ixp.joburg [196.46.25.198]
8 1356 ms 1393 ms 1394 ms 104.20.10.169

Thats assuming the baseline stats are fine - can't comment on that because well you didn't post them. So we might be looking at a combination of exchange congestion and a wifi device downloading for all we know.

Gut feeling - and again guessing (since flying blind) I'd say 50% chance that you're looking at two problems here: semi-congested exchange *and* some wifi device downloading. I assume you took those measurements roughly at when you posted your OP...09:43 PM. Well thats roughly the time when semi-congested exchanges sht themselves.

hmm...just realised the above is an example of very passive-aggressive troubleshoot. Interesting.

 

[Rickster]

I attempted it, but as I said:


Try what I said - disconnect wifi devices one by one. You'll see I'm right - one of them is downloading heavily - heavily enough to fk with your latency on the physical line, but not 100% of the time which will get you inconsistent patterns exactly like you're seeing - high latency with random OK ones.



Thats assuming the baseline stats are fine - can't comment on that because well you didn't post them. So we might be looking at a combination of exchange congestion and a wifi device downloading for all we know.

Gut feeling - and again guessing (since flying blind) I'd say 50% chance that you're looking at two problems here: semi-congested exchange *and* some wifi device downloading. I assume you took those measurements roughly at when you posted your OP...09:43 PM. Well thats roughly the time when semi-congested exchanges sht themselves.

hmm...just realised the above is an example of very passive-aggressive troubleshoot. Interesting.

The device on wifi can download as much as is wants to but it cant affect the dial up account as the wifi is limited to 1meg whereas the dial in account has access to 2meg.

I think ive narrowed it down to upload, some device is doing some sort of upload.

I didnt post line stats because i know its not that and i know how to read it.

 

[HavocXphere]

The device on wifi can download as much as is wants to but it cant affect the dial up account as the wifi is limited to 1meg whereas the dial in account has access to 2meg.

Hahaha. You're very wrong about that. Wish I could put money on this...

Latency gets fk'd even if you run two 1meg accounts on a 2meg line. Grade 1 maths suggests it should work but in the real world it doesn't.

I didnt post line stats because i know its not that and i know how to read it.

The fact that you think I'm asking for line stats pretty much says it all...

I actually wanted a trace during a time when your internet is fine according to you (i.e. "baseline"). As I said - I suspect a semi-congested exchange. This is something that you'll never be able to see in line stats (physically not possible).

The lowest result you've got in the (*ahm*) limited info available is 83ms. If this is a device downloading flat out @1meg account on a 2 meg line then I would have expected something closer to 20-40ms as the lowest value for a local IS server on IS account because routers tend to interleave downloads if devices compete for limited capacity. Or put differently if two devices compete for capacity then you should see sporadically good latency. Which you are (the 83ms)....but its not good enough - there is still an anomaly there.

That combined with the overall higher than expected latencies (way too many results north of 1000ms. I'd expect 500-800 mostly) still suggests to me that we're looking at two issues here.

 

[Rickster]

Hahaha. You're very wrong about that. Wish I could put money on this...

Latency gets fk'd even if you run two 1meg accounts on a 2meg line. Grade 1 maths suggests it should work but in the real world it doesn't.

Depends, you can run 2x100KB/s downloads no problem but when it comes to gaming there has to be some limit on the side you are playing games online, online gaming needs some down and upload speed otherwise you lag.

 

[Genisys]

I want to test a theory, but I really don't have the time to test it (my setup is too complex to change it to just replicate this, it will take a few hours just to get it "normal", and then it will take a few hours to get it to where it needs to be again).

I've had the same issue half and half a while ago. I have two accounts as well, and neither would work properly. Issue at the end of the day was upload. Devices would upload photos to the Google cloud platform, saturating the upload, causing heavy ping spikes and packet loss. Do yourself a favour, monitor your upload bandwidth, and make sure one account isn't saturating the upload.

 

[access]

what is your upstream sync rate and what are you data packages upstream.

the 2x 1mbps might fit nicely into 2mbps, but does the upstream fit nicely too?