Vox Telecom Fatpipe

[bboy]

yep.. defos gone pear shaped

 

[karnuffel]

What area are you guys in? Downloading from steam running at full speed. Netflix also worked with no issues earlier.

 

[Saba'a]

Sorry for old question but how do I transfer my vox fatpipe 150gb promotion for R164 to my cousin so I am not responsible or not in my name anymore?

 

[myKey]

Sorry for old question but how do I transfer my vox fatpipe 150gb promotion for R164 to my cousin so I am not responsible or not in my name anymore?

you can't

 

[Fox1]

What's going on with Vox in Durban? Pings and speed is totally slow.

 

[Saba'a]

you can't

Would assume so also but recall seeing advice to the contrary unless I am mistaken.

Not an issue if one cant. Its just a cleaner process.

 

[roguemat]

What's going on with Vox in Durban? Pings and speed is totally slow.

Arg, so damn slow.

 

[Fox1]

Still not fixed. Looks like its going to be like this all night

 

[SirFooK'nG]

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\>tracert www.voxtel.co.za

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

1 2 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 603 ms 530 ms 544 ms 41.193.73.213
4 599 ms 575 ms 558 ms 41.193.73.214
5 583 ms 531 ms 520 ms 41.193.73.220
6 558 ms 583 ms 585 ms 41.193.72.5
7 589 ms 572 ms 538 ms 41.193.119.114
8 663 ms 593 ms 588 ms 41.193.32.197
9 577 ms 561 ms 569 ms 41.193.32.134
10 597 ms 583 ms 561 ms hz-osfw.voxcore.co.za [196.41.8.5]
11 585 ms 605 ms 550 ms 196.3.169.151

Trace complete.

C:\>ping 196.3.169.151

Pinging 196.3.169.151 with 32 bytes of data:
Reply from 196.3.169.151: bytes=32 time=551ms TTL=118
Reply from 196.3.169.151: bytes=32 time=583ms TTL=118
Reply from 196.3.169.151: bytes=32 time=590ms TTL=118
Reply from 196.3.169.151: bytes=32 time=557ms TTL=118

Ping statistics for 196.3.169.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 551ms, Maximum = 590ms, Average = 570ms

 

[JonesY]

@Everyone, anyone else notice an increase in your in-game ping from 7pm to 12am in the evening's on Vox? My latency on EU servers jumps from 180ms to 250ms, then drops after 12am again like clockwork.

 

[SirFooK'nG]

Well, after emailing all the trace routes, identifying the exact ip in their network where the ping gets borked, Vox still phoned me to do the same tests :wtf: Even after telling them its not the telkom network that's funky, because afrihost works 100%. They still insisted i run a speedtest on SAIX.Net via the the telkom guest account after "testing" another vox account from them... Fianlly the issue has been escalated.

This is Telkoms ping ...


I see now that there is some work happening on VOX, the ping is up & down all over now, but improving...

 

[requiem]

Vox completely ****ing borked in JHB.

Can barely watch youtube....

Who do I move to next?

 

[SirFooK'nG]

C:\ping www.voxtel.co.za -t

Pinging www.voxtel.co.za [196.3.169.151] with 32 bytes of data:
Reply from 196.3.169.151: bytes=32 time=63ms TTL=119
Reply from 196.3.169.151: bytes=32 time=86ms TTL=119
Reply from 196.3.169.151: bytes=32 time=97ms TTL=119
Reply from 196.3.169.151: bytes=32 time=74ms TTL=119
Reply from 196.3.169.151: bytes=32 time=97ms TTL=119
Reply from 196.3.169.151: bytes=32 time=107ms TTL=119
Reply from 196.3.169.151: bytes=32 time=133ms TTL=119
Reply from 196.3.169.151: bytes=32 time=136ms TTL=119
Reply from 196.3.169.151: bytes=32 time=164ms TTL=119
Reply from 196.3.169.151: bytes=32 time=161ms TTL=119
Reply from 196.3.169.151: bytes=32 time=91ms TTL=119
Reply from 196.3.169.151: bytes=32 time=68ms TTL=119
Reply from 196.3.169.151: bytes=32 time=97ms TTL=119
Reply from 196.3.169.151: bytes=32 time=116ms TTL=119
Reply from 196.3.169.151: bytes=32 time=74ms TTL=119
Reply from 196.3.169.151: bytes=32 time=105ms TTL=119
Reply from 196.3.169.151: bytes=32 time=119ms TTL=119
Reply from 196.3.169.151: bytes=32 time=121ms TTL=119
Reply from 196.3.169.151: bytes=32 time=148ms TTL=119
Reply from 196.3.169.151: bytes=32 time=154ms TTL=119
Reply from 196.3.169.151: bytes=32 time=162ms TTL=119
Reply from 196.3.169.151: bytes=32 time=107ms TTL=119
Reply from 196.3.169.151: bytes=32 time=119ms TTL=119

Ping statistics for 196.3.169.151:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 164ms, Average = 113ms

C:\>tracert www.voxtel.co.za

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

1 2 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 251 ms 203 ms 207 ms 41.193.72.125
4 62 ms 70 ms 66 ms 41.193.72.126
5 149 ms 140 ms 156 ms 41.193.72.132
6 88 ms 85 ms 86 ms 41.193.119.114
7 69 ms 74 ms 72 ms 41.193.32.197
8 150 ms 153 ms 161 ms 41.193.32.134
9 154 ms 156 ms 161 ms hz-osfw.voxcore.co.za [196.41.8.5]
10 90 ms 93 ms 91 ms 196.3.169.151

Trace complete.

C:\ping 41.193.72.125 -t (The Offending IP!)

Pinging 41.193.72.125 with 32 bytes of data:
Reply from 41.193.72.125: bytes=32 time=155ms TTL=251
Reply from 41.193.72.125: bytes=32 time=87ms TTL=251
Reply from 41.193.72.125: bytes=32 time=108ms TTL=251
Reply from 41.193.72.125: bytes=32 time=111ms TTL=251
Reply from 41.193.72.125: bytes=32 time=134ms TTL=251
Reply from 41.193.72.125: bytes=32 time=143ms TTL=251
Reply from 41.193.72.125: bytes=32 time=154ms TTL=251
Reply from 41.193.72.125: bytes=32 time=47ms TTL=251
Reply from 41.193.72.125: bytes=32 time=67ms TTL=251
Reply from 41.193.72.125: bytes=32 time=98ms TTL=251
Reply from 41.193.72.125: bytes=32 time=86ms TTL=251
Reply from 41.193.72.125: bytes=32 time=121ms TTL=251
Reply from 41.193.72.125: bytes=32 time=133ms TTL=251
Reply from 41.193.72.125: bytes=32 time=147ms TTL=251
Reply from 41.193.72.125: bytes=32 time=71ms TTL=251
Reply from 41.193.72.125: bytes=32 time=91ms TTL=251
Reply from 41.193.72.125: bytes=32 time=106ms TTL=251
Reply from 41.193.72.125: bytes=32 time=119ms TTL=251
Reply from 41.193.72.125: bytes=32 time=140ms TTL=251
Reply from 41.193.72.125: bytes=32 time=145ms TTL=251
Reply from 41.193.72.125: bytes=32 time=87ms TTL=251
Reply from 41.193.72.125: bytes=32 time=105ms TTL=251

Ping statistics for 41.193.72.125:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 155ms, Average = 111ms

 

[straffe]

@Everyone, anyone else notice an increase in your in-game ping from 7pm to 12am in the evening's on Vox? My latency on EU servers jumps from 180ms to 250ms, then drops after 12am again like clockwork.

Yes, happens about 7:30pm
Switching to Afrihost is fine

Normal 39 google dns ping goes up to 90-100
Normal 180 EU server ping goes up to 240'ish
Vox dns goes from 22'ish to 65-70

For at least 2 weeks now

 

[Mr.Jax]

@Everyone, anyone else notice an increase in your in-game ping from 7pm to 12am in the evening's on Vox? My latency on EU servers jumps from 180ms to 250ms, then drops after 12am again like clockwork.

Yup, same problem here. If I want to game online, I have to switch to my free webafrica account.

 

[Hummercellc]

Vox completely ****ing borked in JHB.

Can barely watch youtube....

Who do I move to next?

Afrihost FTW. You won't be sorry.

 

[Drifter]

My Vox was pretty decent last night again. Streaming Netflix at 1080p with zero buffering.

 

[SirFooK'nG]

Seems to be up & running well again!

 

[BigBear]

Netflix and other services seem OK but P2P dead... Blocking or Broken VOX ??

..

Switched to Other ISP acc and Instant FULL Line Speed...

 

[Type RSA]

Vox seems to be dead at the moment. Line not authenticating