VOX is down

Status
Not open for further replies.
Local is also very odd:

C:\Users\Ant>tracert www.mybroadband.co.za

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 141 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 10 ms 10 ms 10 ms 41.193.121.9
4 225 ms 9 ms 9 ms 41.193.121.10
5 34 ms 12 ms 9 ms 209.203.1.41
6 10 ms 10 ms 10 ms 41.193.120.113
7 176 ms 176 ms 176 ms 196.41.24.174
8 242 ms 176 ms 176 ms ldn-b3-link.telia.net [213.248.100.161]
9 * * * Request timed out.
10 179 ms 177 ms 176 ms ldn-b5-link.telia.net [213.155.136.75]
11 318 ms 183 ms 177 ms cloudflare-ic-306325-ldn-b3.c.telia.net [62.115.
42.242]
12 181 ms 176 ms 176 ms 141.101.112.56

Trace complete.

C:\Users\Ant>
 
That's not what I wanted to hear... Yes, please send me any info, you might find something that looks like C###### or order number, or something like that. I can then find you on the network.

The problem here is that Vumatel manages the speed rates, we don't. If they aren't, I'd like to escalate to them but I need a user to show them where the problem is.

Send to my inbox when you can!

Thanks.

Thank you cvanwie. The issue has been resolved. Thank you for the support!
 
So what's happening now with pings?

C:\Users\Ant>tracert www.twitter.com

Tracing route to twitter.com [199.16.156.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 74 ms 9 ms 9 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 11 ms 10 ms 10 ms 41.193.121.9
4 8 ms 9 ms 8 ms 41.193.121.10
5 15 ms 11 ms 12 ms 209.203.1.41
6 10 ms 10 ms 9 ms 41.193.120.113
7 175 ms 176 ms 180 ms 196.41.24.174
8 177 ms 255 ms 176 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 177 ms 176 ms 288 ms ae-125-3511.edge5.london1.Level3.net [4.69.166.4
1]
10 184 ms 176 ms 297 ms ae-125-3511.edge5.london1.Level3.net [4.69.166.4
1]
11 176 ms 176 ms 176 ms TWITTER-INC.edge5.London1.Level3.net [195.50.120
.66]
12 284 ms 282 ms 609 ms ae65.atl1-er2.twttr.com [192.133.76.19]
13 276 ms 277 ms * 199.16.156.70
14 394 ms 276 ms 276 ms 199.16.156.70

Trace complete.

C:\Users\Ant>

Well, looks like there's quite a delay from Level3 to Twitter.

I drew a few things, which, I'm hoping help you understand a bit more:

http://i.imgur.com/eTP49v9.png

I found an article which I think might be a good idea to read: http://customer.xfinity.com/help-and-support/internet/run-traceroute-command/

You'll notice the latency is here:

11 176 ms 176 ms 176 ms TWITTER-INC.edge5.London1.Level3.net [195.50.120.66]
12 284 ms 282 ms 609 ms ae65.atl1-er2.twttr.com [192.133.76.19]

The last hop in the tracert is what you need to pay attention to, HOP#|RTT1|RTT2|RTT3|destination - there's no average, it's 3 pings to the destination and what each ping was.

You will see that the hand off from Telkom to our (VOX) network is wonderful; the problem is in a 3rd parties network.
 
Local is also very odd:

C:\Users\Ant>tracert www.mybroadband.co.za

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 141 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 10 ms 10 ms 10 ms 41.193.121.9
4 225 ms 9 ms 9 ms 41.193.121.10
5 34 ms 12 ms 9 ms 209.203.1.41
6 10 ms 10 ms 10 ms 41.193.120.113
7 176 ms 176 ms 176 ms 196.41.24.174
8 242 ms 176 ms 176 ms ldn-b3-link.telia.net [213.248.100.161]
9 * * * Request timed out.
10 179 ms 177 ms 176 ms ldn-b5-link.telia.net [213.155.136.75]
11 318 ms 183 ms 177 ms cloudflare-ic-306325-ldn-b3.c.telia.net [62.115.
42.242]
12 181 ms 176 ms 176 ms 141.101.112.56

Trace complete.

C:\Users\Ant>

Why does this look odd?

Looks like their website got moved to London for what ever reason at the time that you performed a test. They don't host with us.

If you look today, I'd imagine you see that they are local again.

Code:
traceroute to 141.101.112.56 (141.101.112.56), 64 hops max, 40 byte packets
 1  196.22.238.121 (196.22.238.121)  0.216 ms  0.196 ms  0.205 ms
 2  41.193.32.149 (41.193.32.149)  0.424 ms 41.193.32.137 (41.193.32.137)  0.414 ms  0.608 ms
 3  41.193.32.198 (41.193.32.198)  0.595 ms 41.193.32.202 (41.193.32.202)  0.778 ms 41.193.32.198 (41.193.32.198)  0.586 ms
 4  41.193.119.22 (41.193.119.22)  0.696 ms 41.193.119.30 (41.193.119.30)  0.634 ms  0.630 ms
 5  africainx.jb1.napafrica.net (196.46.25.135)  1.499 ms  1.457 ms  1.862 ms
 6  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net (41.66.181.59)  1.667 ms  1.855 ms  1.613 ms
 7  141.101.112.56 (141.101.112.56)  1.653 ms  1.600 ms  1.601 ms
 
Ping to Twitter after midnight now over 300ms. I thought it should not be that high?

Tracing route to twitter.com [199.16.156.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 13 ms 9 ms 10 ms 41.193.121.9
4 9 ms 9 ms 8 ms 41.193.121.10
5 9 ms 9 ms 22 ms 209.203.1.41
6 12 ms 12 ms 10 ms 41.193.120.89
7 21 ms 21 ms 21 ms 41.193.106.105
8 22 ms 21 ms 21 ms 41.193.106.97
9 27 ms 26 ms 27 ms 41.193.106.101
10 27 ms 27 ms 26 ms 41.193.32.198
11 200 ms 201 ms 200 ms 196.41.27.70
12 200 ms 200 ms 200 ms ldn-b5-link.telia.net [213.248.86.21]
13 200 ms 200 ms 199 ms ldn-bb3-link.telia.net [213.155.137.116]
14 201 ms 201 ms 200 ms ldn-b3-link.telia.net [62.115.134.135]
15 200 ms 200 ms 200 ms twitter-ic-302264-ldn-b3.c.telia.net [62.115.34.
10]
16 306 ms 306 ms 306 ms ae65.atl1-er2.twttr.com [192.133.76.19]
17 306 ms 306 ms 306 ms 199.16.156.6

Trace complete.
 
Ping to Twitter after midnight now over 300ms. I thought it should not be that high?

Tracing route to twitter.com [199.16.156.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 13 ms 9 ms 10 ms 41.193.121.9
4 9 ms 9 ms 8 ms 41.193.121.10
5 9 ms 9 ms 22 ms 209.203.1.41
6 12 ms 12 ms 10 ms 41.193.120.89
7 21 ms 21 ms 21 ms 41.193.106.105
8 22 ms 21 ms 21 ms 41.193.106.97
9 27 ms 26 ms 27 ms 41.193.106.101
10 27 ms 27 ms 26 ms 41.193.32.198
11 200 ms 201 ms 200 ms 196.41.27.70
12 200 ms 200 ms 200 ms ldn-b5-link.telia.net [213.248.86.21]
13 200 ms 200 ms 199 ms ldn-bb3-link.telia.net [213.155.137.116]
14 201 ms 201 ms 200 ms ldn-b3-link.telia.net [62.115.134.135]
15 200 ms 200 ms 200 ms twitter-ic-302264-ldn-b3.c.telia.net [62.115.34.
10]
16 306 ms 306 ms 306 ms ae65.atl1-er2.twttr.com [192.133.76.19]
17 306 ms 306 ms 306 ms 199.16.156.6

Trace complete.

The high latency starts outside of the vox network.

TL;DR - It isn't Vox's problem.
 
The high latency starts outside of the vox network.

TL;DR - It isn't Vox's problem.

to add

that ip appears to be in Canada, and AntiGanda doesn't seem to understand that distance affects latency...
 
I don't think AntiGanda is taking the time to read cvanwie's responses. After reading that website that was linked about traceroute it actually makes a lot more sense and would be self explanatory if AntiGanda just read it before posting. This is post #223.
 
I don't think AntiGanda is taking the time to read cvanwie's responses. After reading that website that was linked about traceroute it actually makes a lot more sense and would be self explanatory if AntiGanda just read it before posting. This is post #223.

I think he just likes to complain.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X