Digital_Reaper
Well-Known Member
Back up for me
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is the ultimate French toast topping?
Vox Telecom Fatpipe
- Thread starter MMMR_14
- Start date
throwaway420
Banned
- Joined
- Aug 24, 2015
- Messages
- 147
- Reaction score
- 0
Back up here too.
blaaislaai
Executive Member
Mine died 5min ago, restarted the PPPoE connection and working fine now.
sand_man
Honorary Master
Yeah, we running too but torrents are slooooooow..... Barely managing 25% of max line speed on well seeded and multiple torrents...
Anyone know what caused the total outage a few minutes ago? Was also experiencing very high pings (250~ms) to local google services on VOX FP Account for most of this morning. Will paste a trace if it happens tomorrow again.
Edit: saw the announcement about cable breaks, on previous page
Edit: saw the announcement about cable breaks, on previous page
Last edited:
Durban routes through JHB network, for now...
There have been two very odd issues with "sites" not being accessible on our DSL network.
1) Sites hosted at Hetzner -- temporary solution in place while we wait for our peer to correct their network.
2) Carbonite.co.za & prophecy.co.za not accessible; we haven't figured this one out yet. We've reached out to them to no avail. We aren't blocking this traffic and need to get their tech staff involved to find the problem with us.
C:\Users\Esea>tracert 152.111.192.241
Tracing route to 152.111.192.241 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 10.0.0.2
2 368 ms 384 ms 415 ms dsl-197-245-25-1.voxdsl.co.za [197.245.25.1]
3 * * * Request timed out.
4 486 ms 467 ms 394 ms 41.193.3.102
5 410 ms 424 ms 461 ms 196.41.12.0
6 444 ms 367 ms 299 ms 41.193.32.149
7 413 ms 339 ms 457 ms 41.193.32.202
8 455 ms 428 ms 468 ms 41.193.119.30
9 436 ms 478 ms 483 ms mweb.jb1.napafrica.net [196.46.25.145]
10 413 ms 336 ms 358 ms te0-7-0-3.vic-p-1.optinet.net [197.80.7.1]
11 559 ms 452 ms 417 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
12 483 ms 491 ms 509 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
13 439 ms 487 ms 513 ms 196.28.178.66
14 372 ms 386 ms 417 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
15 506 ms 502 ms 444 ms 152.111.192.241
Trace complete.
Just Picked a Random Battlefield 4 server
Tracing route to 152.111.192.241 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 10.0.0.2
2 368 ms 384 ms 415 ms dsl-197-245-25-1.voxdsl.co.za [197.245.25.1]
3 * * * Request timed out.
4 486 ms 467 ms 394 ms 41.193.3.102
5 410 ms 424 ms 461 ms 196.41.12.0
6 444 ms 367 ms 299 ms 41.193.32.149
7 413 ms 339 ms 457 ms 41.193.32.202
8 455 ms 428 ms 468 ms 41.193.119.30
9 436 ms 478 ms 483 ms mweb.jb1.napafrica.net [196.46.25.145]
10 413 ms 336 ms 358 ms te0-7-0-3.vic-p-1.optinet.net [197.80.7.1]
11 559 ms 452 ms 417 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
12 483 ms 491 ms 509 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
13 439 ms 487 ms 513 ms 196.28.178.66
14 372 ms 386 ms 417 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
15 506 ms 502 ms 444 ms 152.111.192.241
Trace complete.
Just Picked a Random Battlefield 4 server
At this time, there was a bit of network balancing going on from the earlier recover.
Please retest and let me know if this is still a problem.
Last edited:
This has been corrected.
FalconZA
Senior Member
p2p totally dead today.....Cape Town
works fine on WA, Afrihost, etc
works fine on WA, Afrihost, etc
Not congested at all, lots of room actually. P2P is the third largest consumption of bandwidth in Cape Town at the moment, it's working extremely well.
You sure your account isn't capped?
FalconZA
Senior Member
Pretty sure i am not capped.
Service Status Active Data Allocated 319.27 GB
Data Used 32.94 GB Data Available 286.32 GB
p2p just doesn't seem to be moving for me at all. Switch over to another ISP and its back to full line speed.....
Drifter
Honorary Master
Sigh, on 196.... DNS I get sub 1 mbps download and ping of > 200 ms, when I switch to Google DNS 8.8.8.8 I get
Last Result:
Download Speed: 8535 kbps (1066.9 KB/sec transfer rate)
Upload Speed: 728 kbps (91 KB/sec transfer rate)
Latency: 24 ms
2015/09/24, 9:29:05 AM
Last Result:
Download Speed: 8535 kbps (1066.9 KB/sec transfer rate)
Upload Speed: 728 kbps (91 KB/sec transfer rate)
Latency: 24 ms
2015/09/24, 9:29:05 AM
Drifter
Honorary Master
Line test using Zertop's lime tool
1st with VOX
Zertop's "Is it my Line" Results
Date/Time: Thu Sep 24 09:33:52 CAT 2015
Basic Report:
Your packet loss was 10%.
Your average ping was 181ms.
Your maximum ping was 273ms.
You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Changed to MWEB, line speed and line test:
Last Result:
Download Speed: 8763 kbps (1095.4 KB/sec transfer rate)
Upload Speed: 837 kbps (104.6 KB/sec transfer rate)
Latency: 24 ms
2015/09/24, 9:38:42 AM
Zertop's "Is it my Line" Results
Date/Time: Thu Sep 24 09:40:10 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 214ms.
Your maximum ping was 367ms.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
1st with VOX
Zertop's "Is it my Line" Results
Date/Time: Thu Sep 24 09:33:52 CAT 2015
Basic Report:
Your packet loss was 10%.
Your average ping was 181ms.
Your maximum ping was 273ms.
You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=210ms TTL=63
Reply from 155.239.255.250: bytes=32 time=273ms TTL=63
Reply from 155.239.255.250: bytes=32 time=131ms TTL=63
Reply from 155.239.255.250: bytes=32 time=83ms TTL=63
Reply from 155.239.255.250: bytes=32 time=204ms TTL=63
Reply from 155.239.255.250: bytes=32 time=221ms TTL=63
Reply from 155.239.255.250: bytes=32 time=214ms TTL=63
Reply from 155.239.255.250: bytes=32 time=120ms TTL=63
Reply from 155.239.255.250: bytes=32 time=173ms TTL=63
Reply from 155.239.255.250: bytes=32 time=229ms TTL=63
Reply from 155.239.255.250: bytes=32 time=171ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=229ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=120ms TTL=63
Reply from 155.239.255.250: bytes=32 time=131ms TTL=63
Reply from 155.239.255.250: bytes=32 time=205ms TTL=63
Reply from 155.239.255.250: bytes=32 time=131ms TTL=63
Reply from 155.239.255.250: bytes=32 time=240ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=221ms TTL=63
Reply from 155.239.255.250: bytes=32 time=221ms TTL=63
Reply from 155.239.255.250: bytes=32 time=71ms TTL=63
Reply from 155.239.255.250: bytes=32 time=197ms TTL=63
Reply from 155.239.255.250: bytes=32 time=232ms TTL=63
Reply from 155.239.255.250: bytes=32 time=152ms TTL=63
Reply from 155.239.255.250: bytes=32 time=97ms TTL=63
Reply from 155.239.255.250: bytes=32 time=215ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=177ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 273ms, Average = 181msChanged to MWEB, line speed and line test:
Last Result:
Download Speed: 8763 kbps (1095.4 KB/sec transfer rate)
Upload Speed: 837 kbps (104.6 KB/sec transfer rate)
Latency: 24 ms
2015/09/24, 9:38:42 AM
Zertop's "Is it my Line" Results
Date/Time: Thu Sep 24 09:40:10 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 214ms.
Your maximum ping was 367ms.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=284ms TTL=63
Reply from 155.239.255.250: bytes=32 time=156ms TTL=63
Reply from 155.239.255.250: bytes=32 time=161ms TTL=63
Reply from 155.239.255.250: bytes=32 time=239ms TTL=63
Reply from 155.239.255.250: bytes=32 time=164ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=144ms TTL=63
Reply from 155.239.255.250: bytes=32 time=180ms TTL=63
Reply from 155.239.255.250: bytes=32 time=183ms TTL=63
Reply from 155.239.255.250: bytes=32 time=296ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=225ms TTL=63
Reply from 155.239.255.250: bytes=32 time=117ms TTL=63
Reply from 155.239.255.250: bytes=32 time=363ms TTL=63
Reply from 155.239.255.250: bytes=32 time=204ms TTL=63
Reply from 155.239.255.250: bytes=32 time=181ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=187ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=162ms TTL=63
Reply from 155.239.255.250: bytes=32 time=182ms TTL=63
Reply from 155.239.255.250: bytes=32 time=171ms TTL=63
Reply from 155.239.255.250: bytes=32 time=173ms TTL=63
Reply from 155.239.255.250: bytes=32 time=315ms TTL=63
Reply from 155.239.255.250: bytes=32 time=186ms TTL=63
Reply from 155.239.255.250: bytes=32 time=281ms TTL=63
Reply from 155.239.255.250: bytes=32 time=216ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=141ms TTL=63
Reply from 155.239.255.250: bytes=32 time=212ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 367ms, Average = 214ms
Soul Assassin
Honorary Master
- Joined
- Mar 27, 2006
- Messages
- 11,758
- Reaction score
- 2,330
Maybe time to call Telkom?
We aren't that far from each other, my results:
Zertop's "Is it my Line" Results
Date/Time: Thu Sep 24 09:50:54 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 9ms.
Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 7msJust remember that high latency to Telkom's BRAS Anycast (155.239.255.250) would typically indicate either congestion at the exchange / that something else is already utilizing your line to its capacity / or that there is an inherent problem on your line causing the high packet loss. Pinging that address bypasses whatever ISP you're using, so you can't blame the latency on the ISP. If you need to do an ISP-specific test then you would have to use other addresses.
As for DNS - remember that (in this context at least) it is merely a service used to translate/resolve host/domain names to IP addresses and vice versa. So if you're getting better _transfer_ speeds using one DNS server rather than another, then it can only really be a case of the DNS servers resolving the speedtest server's hostname to a different IP address. As far as I know each speedtest server is usually reachable via one static IP address... are you sure you're testing on the same speedtest server each time?
As for DNS - remember that (in this context at least) it is merely a service used to translate/resolve host/domain names to IP addresses and vice versa. So if you're getting better _transfer_ speeds using one DNS server rather than another, then it can only really be a case of the DNS servers resolving the speedtest server's hostname to a different IP address. As far as I know each speedtest server is usually reachable via one static IP address... are you sure you're testing on the same speedtest server each time?
Last edited: