Vox Telecom Fatpipe

If your second hop doesn't display, simply ping telkom-bras.vox.co.za (will only work while on a DSL line).

That means that you are on Telkom's Alcatel equipment instead of the Huawei. Nothing major, just the equipment doesn't allow ICMP traffic.

Get the same as AntiGanda, not sure if it is important, but thought I'd post it anyway. In Cape Town:

Code:
Pinging telkom-bras.vox.co.za [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Hmmm... no problem here...

C:\>ping telkom-bras.vox.co.za

Pinging telkom-bras.vox.co.za [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=20ms TTL=64
Reply from 155.239.255.250: bytes=32 time=19ms TTL=64
Reply from 155.239.255.250: bytes=32 time=32ms TTL=64
Reply from 155.239.255.250: bytes=32 time=20ms 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 = 19ms, Maximum = 32ms, Average = 22ms


Cape Town southern suburbs...

Edit:

For what it's worth:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         155.239.255.250 -    0 |  100 |  100 |   18 |   20 |   41 |   20 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Last edited:
Is that the link to use when your connection goes Tits Up ?

Only when my b@lls are to the wall :erm:

TBH though I maintain a number of accounts for redundancy sake and TI has proved pretty bullet proof over the last few years, they may not be the cheapest or the fastest, but they hardly ever go down.
 
where do i post my issue on vox? this thread or the official one?


Tracing route to www.netflix.com.netflix-cluster.unostructure.com [173.208.224.4
5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 123 ms 16 ms 98 ms 41.193.164.85
4 1224 ms 1643 ms 2242 ms 41.193.164.86
5 3163 ms 2627 ms 2686 ms 41.193.164.92
6 3143 ms 2290 ms 1220 ms 41.193.119.45
7 1484 ms 2243 ms 2971 ms 196.41.27.70
8 3709 ms 2003 ms 999 ms 196.41.27.114
9 1663 ms 2021 ms 2759 ms 40ge1-3.core1.lon2.he.net [195.66.224.21]
10 * * 910 ms 100ge1-1.core1.nyc4.he.net [72.52.92.166]
11 1919 ms 2377 ms 1737 ms 100ge7-2.core1.chi1.he.net [184.105.223.161]
12 637 ms 533 ms 479 ms 10ge3-3.core1.mci1.he.net [72.52.92.2]
13 828 ms 549 ms 700 ms 10ge1-1.core1.mci2.he.net [184.105.213.2]
14 350 ms 844 ms 1327 ms wholesale-internet-inc.10gigabitethernet1-3.core
1.mci2.he.net [216.66.78.90]
15 1077 ms 1234 ms 1115 ms lag-to-oak.edge-a.clay1.mci.us.as32097.net [69.3
0.209.163]
16 877 ms 535 ms 585 ms lag-core-b.dist-1-2.clay1.mci.us.as32097.net [20
8.110.88.3]
17 463 ms * 1193 ms 173.208.224.45

Trace complete.


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

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 * 1327 ms 613 ms 41.193.164.85
4 3327 ms * * 41.193.164.86
5 3433 ms * * 41.193.164.92
6 2862 ms 2183 ms 1109 ms 41.193.119.45
7 449 ms 881 ms * 196.41.27.70
8 1375 ms 1690 ms 2047 ms ldn-b5-link.telia.net [213.248.86.21]
9 3120 ms * 3793 ms ldn-bb2-link.telia.net [213.155.136.6
10 1724 ms 2552 ms 3540 ms ldn-b5-link.telia.net [80.91.249.180]
11 2553 ms 1765 ms 3142 ms cloudflare-ic-306325-ldn-b3.c.telia.n
42.242]
12 * 3550 ms 996 ms 104.20.71.110

Trace complete.
 
Youtube browsing buffering badly. Been iffy for at least the last two days.

Have a 40Mbps line and on multiple fatpipe accounts.
 
Youtube browsing buffering badly. Been iffy for at least the last two days.

Have a 40Mbps line and on multiple fatpipe accounts.

Could you please post a speedtest? I'm currently getting rate limited, and I think it's because of the telkom exchange.
 
Only when my b@lls are to the wall :erm:

TBH though I maintain a number of accounts for redundancy sake and TI has proved pretty bullet proof over the last few years, they may not be the cheapest or the fastest, but they hardly ever go down.

have to agree with you, I have had an account with them since 2002, and it is still my fall back acount when my current ISP of the month goes down or when I have a mission critical download to do. Slow and dependable. That said, I have considered canceling it a couple of times but am too scared that they may misinterpret the request and cancel my ADSL connection :) can't risk that till I have fiber.
 
Could you please post a speedtest? I'm currently getting rate limited, and I think it's because of the telkom exchange.

what speed is your line? What are you being limited to?

Think i'm experiencing the same thing.
 
Bottom line, you need to run mtr tests to see where the packet loss is happening and solve the fundamental problem with the dropped packets. It's a fairly simple process and is why we don't use tracerts much in our business as they only tell half the story. My suspicion is the packets are dropping on hop 1 or 2. If 3, it's Vox's issue. If it's 2, it's Telkom's issue. If it's on 1 (or your internal network) it's your problem, and your ISP can assist to trace the root cause...

DJ - just to clear this up. Telkom is hop 2 and 3, we start at hop 4.

Hop 3 is the Telkom Upload VLAN to our IPC.

Regarding pingplotter, what I said AntiGanda was that it could not be trusted for packet loss reporting, please stop misquoting me.
 
If the problem was to do with ICMP equipment affecting it, then the traces should be consistent.
They are not.


{This trace was from this morning at around 10AM}

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 * * * Request timed out.
4 8 ms 9 ms 9 ms 41.193.121.10
5 10 ms 10 ms 9 ms 209.203.1.41
6 9 ms 10 ms 10 ms 41.193.120.113
7 177 ms 175 ms 176 ms 196.41.24.174
8 176 ms 176 ms 176 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 * * * Request timed out.
10 * * * Request timed out.
11 193 ms 229 ms 192 ms 195.16.162.254
12 190 ms 190 ms 191 ms core11.hetzner.de [213.239.203.137]
13 190 ms 190 ms 190 ms core13.hetzner.de [213.239.203.198]
14 193 ms 192 ms 192 ms ex9k2.rz1.hetzner.de [213.239.203.214]
15 190 ms 190 ms 189 ms dedi354.nur4.host-h.net [78.46.9.234]
===

{I repeated this trace at 1:35PM}
Tracing route to www.avcom.co.za [78.46.9.234]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 9 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 10 ms 10 ms 9 ms 41.193.121.9
4 9 ms 11 ms 9 ms 41.193.121.10
5 9 ms 10 ms 10 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 176 ms 183 ms 176 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 186 ms 185 ms 255 ms ae-1-60.edge7.Frankfurt1.Level3.net [4.69.154.11
]
10 186 ms * 187 ms ae-1-60.edge7.Frankfurt1.Level3.net [4.69.154.11
]
11 191 ms 190 ms 190 ms 195.16.162.254
12 190 ms 190 ms 190 ms core12.hetzner.de [213.239.245.25]
13 193 ms 193 ms 192 ms core13.hetzner.de [213.239.203.202]
14 193 ms 192 ms 192 ms ex9k2.rz1.hetzner.de [213.239.203.214]
15 191 ms 191 ms 190 ms dedi354.nur4.host-h.net [78.46.9.234]

Trace complete.

Great traces! This shows that the Vox network was consistent. Once it leaves our network, I'm not sure what you are expecting.

Hop 1 = your house
Hop 2 = Telkom dslam/exchange
Hop 3 = Telkom Upload VLAN to Vox IPC
Hop 4-7 = Vox network
Hop 8+ other providers.

I cannot say this any differently. Vox does not control nor can influence Level 3 nor Hetzner. Contact those providers to complain about their latency. This is not a Vox issue.
 
Top
Sign up to the MyBroadband newsletter
X