Official Vox DSL feedback thread

Seeyou said:
Thanks for the continued investigation and troubleshooting on this Chris - I'm sure everyone here appreciates it. Getting Telkom to respond was always going to be the tough part. MyBB is constantly trawling for news stories - I wonder if some publicity regarding the issue and Telkom's unwillingness to acknowledge it / help would speed up their response?

As a matter of interest - how does the temporary fix work? Routing around the congested hop?
Click to expand...

There's no need to point blame, this was a very unique scenario and easily something that could be missed without the testing that we did last night.

There was a moment where the testing instantly had an adverse outcome and we stopped everything, narrowed it down, did a few things, found the issue, disabled it, and resolved the issue immediately. This identified the exact problem.

Our temp fix, is doing the same action that we did to find the problem. Our senior network engineers will be handling this until the perm fix is in.
 
WOW, is all I can say. Getting 997kB/s on P2P(read torrent)at 14:00 in the day has previously been unheard of. Whatever you guys at VOX did, it worked. Thank you.
 
Drifter said:
WOW, is all I can say. Getting 997kB/s on P2P(read torrent)at 14:00 in the day has previously been unheard of. Whatever you guys at VOX did, it worked. Thank you.
Click to expand...

We did find a latency issue in JHB, which was our fault. We fixed that today. I have a feeling that's what you're talking about :)
 
cvanwie said:
We did find a latency issue in JHB, which was our fault. We fixed that today. I have a feeling that's what you're talking about :)
Click to expand...

@cvanwie - will the temp fix for CPT be in place this evening?
 
Seeyou said:
@cvanwie - will the temp fix for CPT be in place this evening?
Click to expand...

Unfortunately not. Telkom has accepted fault and want it demonstrated to them tonight. In order to do so, the latency issue must be in place.

Tomorrow though, temp fix will be enabled until Telkom gives us a perm solution.
 
What's one more night if it leads to the resolution of the issue. Great news!
 
Before I start complaining :p.
Who do I blame for the below.

7pm
Code: 
Tracing route to twitter.co.za [203.27.227.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3   181 ms   193 ms   158 ms  41.193.164.85
  4     *      163 ms   161 ms  41.193.164.86
  5   144 ms   141 ms   124 ms  41.193.164.92
  6   139 ms   167 ms   180 ms  41.193.119.45
  7   740 ms   842 ms   915 ms  196.41.27.70
  8   527 ms   487 ms   522 ms  xe-7-1-2.edge3.London1.Level3.net [212.113.15.33]
  9   552 ms   537 ms   535 ms  4.68.70.78
 10   885 ms   890 ms   739 ms  ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
 11   957 ms   922 ms   893 ms  v133.ae28.cr1.ord2.us.zip.zayo.com [64.125.30.112]
 12   897 ms   909 ms   775 ms  ae12.mpr1.den1.us.zip.zayo.com [64.125.20.250]
 13  1038 ms  1072 ms   910 ms  ae5.cr1.sjc2.us.zip.zayo.com [64.125.25.53]
 14  1100 ms  1047 ms   939 ms  ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
 15  1002 ms   840 ms   891 ms  64.125.170.226.t01617-01.above.net [64.125.170.226]
 16  1034 ms  1020 ms  1051 ms  182.255.80.41
 17  1022 ms     *      754 ms  dbsparked.melbourneit.com [203.27.227.220]

12:50am
Code: 
Tracing route to twitter.co.za [203.27.227.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    25 ms    12 ms     8 ms  41.193.164.85
  4    44 ms    21 ms    17 ms  41.193.164.86
  5    28 ms    38 ms    21 ms  41.193.164.92
  6    26 ms    34 ms    35 ms  41.193.119.45
  7   223 ms   212 ms   214 ms  196.41.27.70
  8   184 ms   184 ms   184 ms  xe-7-1-2.edge3.London1.Level3.net [212.113.15.33]
  9   183 ms   183 ms   184 ms  4.68.70.78
 10   184 ms   183 ms   184 ms  ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
 11   326 ms   326 ms   326 ms  v37.ae29.cr1.sjc2.us.zip.zayo.com [64.125.30.92]
 12   325 ms   326 ms   325 ms  ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
 13   326 ms   326 ms   325 ms  64.125.170.226.t01617-01.above.net [64.125.170.226]
 14   326 ms   326 ms   325 ms  182.255.80.41
 15   327 ms   326 ms   327 ms  dbsparked.melbourneit.com [203.27.227.220]

Should mention I am using Google DNS servers as VOX's stop working at random moments.
 
Pho3nix said:
Before I start complaining :p.
Who do I blame for the below.

7pm
Code: 
Tracing route to twitter.co.za [203.27.227.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3   181 ms   193 ms   158 ms  41.193.164.85
  4     *      163 ms   161 ms  41.193.164.86
  5   144 ms   141 ms   124 ms  41.193.164.92
  6   139 ms   167 ms   180 ms  41.193.119.45
  7   740 ms   842 ms   915 ms  196.41.27.70
  8   527 ms   487 ms   522 ms  xe-7-1-2.edge3.London1.Level3.net [212.113.15.33]
  9   552 ms   537 ms   535 ms  4.68.70.78
 10   885 ms   890 ms   739 ms  ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
 11   957 ms   922 ms   893 ms  v133.ae28.cr1.ord2.us.zip.zayo.com [64.125.30.112]
 12   897 ms   909 ms   775 ms  ae12.mpr1.den1.us.zip.zayo.com [64.125.20.250]
 13  1038 ms  1072 ms   910 ms  ae5.cr1.sjc2.us.zip.zayo.com [64.125.25.53]
 14  1100 ms  1047 ms   939 ms  ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
 15  1002 ms   840 ms   891 ms  64.125.170.226.t01617-01.above.net [64.125.170.226]
 16  1034 ms  1020 ms  1051 ms  182.255.80.41
 17  1022 ms     *      754 ms  dbsparked.melbourneit.com [203.27.227.220]

12:50am
Code: 
Tracing route to twitter.co.za [203.27.227.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    25 ms    12 ms     8 ms  41.193.164.85
  4    44 ms    21 ms    17 ms  41.193.164.86
  5    28 ms    38 ms    21 ms  41.193.164.92
  6    26 ms    34 ms    35 ms  41.193.119.45
  7   223 ms   212 ms   214 ms  196.41.27.70
  8   184 ms   184 ms   184 ms  xe-7-1-2.edge3.London1.Level3.net [212.113.15.33]
  9   183 ms   183 ms   184 ms  4.68.70.78
 10   184 ms   183 ms   184 ms  ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
 11   326 ms   326 ms   326 ms  v37.ae29.cr1.sjc2.us.zip.zayo.com [64.125.30.92]
 12   325 ms   326 ms   325 ms  ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
 13   326 ms   326 ms   325 ms  64.125.170.226.t01617-01.above.net [64.125.170.226]
 14   326 ms   326 ms   325 ms  182.255.80.41
 15   327 ms   326 ms   327 ms  dbsparked.melbourneit.com [203.27.227.220]

Should mention I am using Google DNS servers as VOX's stop working at random moments.
Click to expand...

Ping 155.239.255.250 the next time you have this issue and provide the results here.
 
Pho3nix said:
Before I start complaining :p.
Who do I blame for the below.

7pm
Code: 
Tracing route to twitter.co.za [203.27.227.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3   181 ms   193 ms   158 ms  41.193.164.85
  4     *      163 ms   161 ms  41.193.164.86
  5   144 ms   141 ms   124 ms  41.193.164.92
  6   139 ms   167 ms   180 ms  41.193.119.45
  7   740 ms   842 ms   915 ms  196.41.27.70
  8   527 ms   487 ms   522 ms  xe-7-1-2.edge3.London1.Level3.net [212.113.15.33]
  9   552 ms   537 ms   535 ms  4.68.70.78
 10   885 ms   890 ms   739 ms  ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
 11   957 ms   922 ms   893 ms  v133.ae28.cr1.ord2.us.zip.zayo.com [64.125.30.112]
 12   897 ms   909 ms   775 ms  ae12.mpr1.den1.us.zip.zayo.com [64.125.20.250]
 13  1038 ms  1072 ms   910 ms  ae5.cr1.sjc2.us.zip.zayo.com [64.125.25.53]
 14  1100 ms  1047 ms   939 ms  ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
 15  1002 ms   840 ms   891 ms  64.125.170.226.t01617-01.above.net [64.125.170.226]
 16  1034 ms  1020 ms  1051 ms  182.255.80.41
 17  1022 ms     *      754 ms  dbsparked.melbourneit.com [203.27.227.220]

12:50am
Code: 
Tracing route to twitter.co.za [203.27.227.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    25 ms    12 ms     8 ms  41.193.164.85
  4    44 ms    21 ms    17 ms  41.193.164.86
  5    28 ms    38 ms    21 ms  41.193.164.92
  6    26 ms    34 ms    35 ms  41.193.119.45
  7   223 ms   212 ms   214 ms  196.41.27.70
  8   184 ms   184 ms   184 ms  xe-7-1-2.edge3.London1.Level3.net [212.113.15.33]
  9   183 ms   183 ms   184 ms  4.68.70.78
 10   184 ms   183 ms   184 ms  ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
 11   326 ms   326 ms   326 ms  v37.ae29.cr1.sjc2.us.zip.zayo.com [64.125.30.92]
 12   325 ms   326 ms   325 ms  ae12.er1.sjc2.us.zip.zayo.com [64.125.25.22]
 13   326 ms   326 ms   325 ms  64.125.170.226.t01617-01.above.net [64.125.170.226]
 14   326 ms   326 ms   325 ms  182.255.80.41
 15   327 ms   326 ms   327 ms  dbsparked.melbourneit.com [203.27.227.220]

Should mention I am using Google DNS servers as VOX's stop working at random moments.
Click to expand...

I'd put money on exchange to be honest. I have the same issue on my link around the same time and it dies off after 10PM ish. My exchange is congested as there's only 1 in a huge radius :(
 
Method said:
I'd put money on exchange to be honest. I have the same issue on my link around the same time and it dies off after 10PM ish. My exchange is congested as there's only 1 in a huge radius :(
Click to expand...

Telkom applied changes last night, please test tonight after 6pm and let me know if you're still seeing latency issues. We are not 100% certain that their fix is the final one.
 
cvanwie said:
Telkom applied changes last night, please test tonight after 6pm and let me know if you're still seeing latency issues. We are not 100% certain that their fix is the final one.
Click to expand...

Definitely noticed an improvement in latency later last night. Pings to 8.8.8.8 were hovering around 50-60ms. It's not quite the 30ms of daytime, but it's a massive improvement over 200-300ms.
 
Method said:
I'd put money on exchange to be honest. I have the same issue on my link around the same time and it dies off after 10PM ish. My exchange is congested as there's only 1 in a huge radius :(
Click to expand...

Hmm.. New MSAN installed and everything goes to hell.

Will start complaining :)
 
cvanwie said:
Telkom applied changes last night, please test tonight after 6pm and let me know if you're still seeing latency issues. We are not 100% certain that their fix is the final one.
Click to expand...

Hey cvanwie,

I can confirm vast improvements in latency last night. Was hitting local servers at +-50ms as opposed to 200ms! :D
 
There's more to come. Change control just logged.

Big change coming Friday night at midnight. (that's early Saturday morning)

This weekend+ should be the permanent fix... fingers crossed.
 
cvanwie said:
Telkom applied changes last night, please test tonight after 6pm and let me know if you're still seeing latency issues. We are not 100% certain that their fix is the final one.
Click to expand...

Thanks! I'll have a look tonight.
 
cvanwie said:
There's more to come. Change control just logged.

Big change coming Friday night at midnight. (that's early Saturday morning)

This weekend+ should be the permanent fix... fingers crossed.
Click to expand...

Haven't been home for last few nights, keen to test the performance tonight.

More importantly, thank you for providing us with useful and prompt feedback. Wondering why I didn't sign-up with Vox years ago.... :cry::cry::cry:
 
bumbledore said:
More importantly, thank you for providing us with useful and prompt feedback. Wondering why I didn't sign-up with Vox years ago.... :cry::cry::cry:
Click to expand...

Cuz they weren't as prominent back then/ don't market half as much as the other ISPs? I only heard about Vox a few years ago because their public DNSs came up on a local DNS search using a tool called DNSBench cuz the Telkom ones at the time kept deciding that half the net didn't exist and wouldn't load this, that and everything else properly. The Vox ones were far more reliable at the time so I used them for a while as well.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X