Double my usual ping

James946

James946

Well-Known Member
Joined
Jul 18, 2019
Messages
178
Reaction score
64
Like 3 or so days ago my internet went out for a hour or two, weird but ok. But after it came back on my ping to local servers have doubled from 10-12ms to 24-25ms, this also affects my ping to eu since my ping went from 155ms to london to 180-200 (uk vpn doesnt help much, drops it to around 178)

Vuma reach port elizabeth

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 38 byte packets
1 102.132.249.129 (102.132.249.129) 22.795 ms 24.598 ms 27.156 ms
2 154.0.2.241 (154.0.2.241) 22.507 ms 22.425 ms 22.529 ms
3 100.98.0.20 (100.98.0.20) 22.530 ms 22.526 ms 22.580 ms
4 100.98.0.1 (100.98.0.1) 22.634 ms 22.425 ms 22.553 ms
5 100.98.0.12 (100.98.0.12) 22.572 ms 22.482 ms 22.559 ms
6 cloudflare.ixp.capetown (196.60.70.198) 30.067 ms 22.991 ms 23.243 ms
7 one.one.one.one (1.1.1.1) 22.665 ms 22.542 ms 22.561 ms

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 102.132.249.129 (102.132.249.129) 22.542 ms 22.726 ms 22.396 ms
2 154.0.2.241 (154.0.2.241) 22.615 ms 22.399 ms 33.059 ms
3 100.98.0.20 (100.98.0.20) 22.491 ms 22.484 ms 22.421 ms
4 100.98.0.1 (100.98.0.1) 22.488 ms 22.470 ms 22.514 ms
5 100.98.1.18 (100.98.1.18) 39.070 ms 44.618 ms 39.190 ms
6 100.99.1.250 (100.99.1.250) 38.444 ms 38.253 ms 38.396 ms
7 196-60-9-113.ixp.joburg (196.60.9.113) 40.295 ms 41.067 ms 40.156 ms
8 * * *
9 dns.google (8.8.8.8) 39.076 ms 38.946 ms 38.985 ms
 
James946 said:
Like 3 or so days ago my internet went out for a hour or two, weird but ok. But after it came back on my ping to local servers have doubled from 10-12ms to 24-25ms, this also affects my ping to eu since my ping went from 155ms to london to 180-200 (uk vpn doesnt help much, drops it to around 178)

Vuma reach port elizabeth

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 38 byte packets
1 102.132.249.129 (102.132.249.129) 22.795 ms 24.598 ms 27.156 ms
2 154.0.2.241 (154.0.2.241) 22.507 ms 22.425 ms 22.529 ms
3 100.98.0.20 (100.98.0.20) 22.530 ms 22.526 ms 22.580 ms
4 100.98.0.1 (100.98.0.1) 22.634 ms 22.425 ms 22.553 ms
5 100.98.0.12 (100.98.0.12) 22.572 ms 22.482 ms 22.559 ms
6 cloudflare.ixp.capetown (196.60.70.198) 30.067 ms 22.991 ms 23.243 ms
7 one.one.one.one (1.1.1.1) 22.665 ms 22.542 ms 22.561 ms

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 102.132.249.129 (102.132.249.129) 22.542 ms 22.726 ms 22.396 ms
2 154.0.2.241 (154.0.2.241) 22.615 ms 22.399 ms 33.059 ms
3 100.98.0.20 (100.98.0.20) 22.491 ms 22.484 ms 22.421 ms
4 100.98.0.1 (100.98.0.1) 22.488 ms 22.470 ms 22.514 ms
5 100.98.1.18 (100.98.1.18) 39.070 ms 44.618 ms 39.190 ms
6 100.99.1.250 (100.99.1.250) 38.444 ms 38.253 ms 38.396 ms
7 196-60-9-113.ixp.joburg (196.60.9.113) 40.295 ms 41.067 ms 40.156 ms
8 * * *
9 dns.google (8.8.8.8) 39.076 ms 38.946 ms 38.985 ms
Click to expand...

Hi, your first hop has 22ms worth of latency, which FNO and area?
 
James946 said:
Vuma reach port elizabeth
it used to be half that a week ago
Click to expand...
Yes so this means there is a fault on the South bound route of their (Vumatels) NLD so you would typically route PE-KZN-JHB-CPT, hence the bloated latency. Once their primary PE-CPT is restored your latency all also restore.
 
PBCool said:
Yes so this means there is a fault on the South bound route of their (Vumatels) NLD so you would typically route PE-KZN-JHB-CPT, hence the bloated latency. Once their primary PE-CPT is restored your latency all also restore.
Click to expand...
Thanks for the information. How long does it take vuma to fix a route usually?
 
Not sure to be honest, we have had this sort of issue with Frogfoot and Octotel in the past but not Vumatel. We have also seen FNOs do this when they have capacity constraints. I will reach out and see if I can get some info.
 
Feedback is Vumatel has multiple failures and their replacement kit is due to be installed by the end of next week.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X