Vox Telecom Fatpipe

Electric · Oct 16, 2015

Ping was very high last night.

techead · Oct 16, 2015

Chris, I will ride this out. You guys might be having some issues but your approach and attitude is commendable, nothing like what I had to deal with from Afrihost.

I hope you guys come right. Meanwhile, I've got a fault on my line

but that's not your problem

Drifter · Oct 16, 2015

Dont know what is happening, but my P2P was running at a solid 6kB/s at 04:45 this morning.

cvanwie · Oct 16, 2015

techead said:
Chris, I will ride this out. You guys might be having some issues but your approach and attitude is commendable, nothing like what I had to deal with from Afrihost.

I hope you guys come right. Meanwhile, I've got a fault on my line but that's not your problem

Thanks techead. I'm doing everything I can.

So here's the feedback:

We reported issues from Telkom's exchange through to the Telkom upload VLAN (41.193.121.9 and 41.192.121.38
) in Cape Town to our IPC. Telkom decided to test only from the upload VLAN, ignoring the exchange. There was no latency from the Telkom Upload VLAN to our IPC, so it seems the congestion (latency) seems to be between the exchange and their upload vlan.

Here's there tests that Telkom performed from their equipement (upload vlan) using our VRF (handing off to our IPC):

Code:

wwg-ip-bng-1#traceroute vrf ********* www.rt.com
Translating "www.rt.com"...domain server (196.43.1.11) [OK]

Type escape sequence to abort.
Tracing the route to www.rt.com (37.48.108.112)
VRF info: (vrf in name/id, vrf out name/id)
1 41.193.121.38 [AS 11845] 4 msec 2 msec 6 msec
2 196.41.29.233 [AS 11845] 3 msec 2 msec 1 msec
3 41.193.120.121 [AS 11845] [MPLS: Label 365232 Exp 0] 3 msec 2 msec 2 msec
4 196.41.24.174 [AS 11845] 169 msec 168 msec 169 msec
5 xe-10-2-2.edge4.London1.Level3.net (195.50.120.13) 178 msec 175 msec 176 mse
c
6 ae-234-3610.edge3.Amsterdam1.Level3.net (4.69.162.214) 177 msec
ae-233-3609.edge3.Amsterdam1.Level3.net (4.69.162.210) 177 msec
ae-236-3612.edge3.Amsterdam1.Level3.net (4.69.162.222) 177 msec
7 FIBERRING-B.edge3.Amsterdam1.Level3.net (213.244.164.54) 200 msec
FIBERRING-B.edge3.Amsterdam1.Level3.net (212.72.33.218) 199 msec
FIBERRING-B.edge3.Amsterdam1.Level3.net (212.72.42.134) 197 msec
8 po1003.ngn-ams1-cs2-new.leaseweb.net (37.48.95.201) 188 msec
po1001.ngn-ams1-cs1-new.leaseweb.net (5.79.79.239) 188 msec 188 msec
9 * * *
10

Code:

wwg-ip-bng-1#traceroute vrf ********* www.twitter.com
Translating "www.twitter.com"...domain server (196.43.1.11) [OK]

Type escape sequence to abort.
Tracing the route to twitter.com (199.16.156.70)
VRF info: (vrf in name/id, vrf out name/id)
1 41.193.121.38 [AS 11845] 2 msec 2 msec 2 msec
2 196.41.29.233 [AS 11845] 2 msec 2 msec 3 msec
3 41.193.120.121 [AS 11845] [MPLS: Label 365232 Exp 0] 3 msec 2 msec 2 msec
4 196.41.24.174 [AS 11845] 169 msec 168 msec 169 msec
5 xe-10-2-2.edge4.London1.Level3.net (195.50.120.13) 178 msec 176 msec 176 mse
c
6 ae-123-3509.edge5.London1.Level3.net (4.69.166.33) 179 msec
ae-124-3510.edge5.london1.Level3.net (4.69.166.37) 178 msec 179 msec
7 ae-126-3512.edge5.london1.Level3.net (4.69.166.45) 178 msec
ae-235-3611.edge5.london1.Level3.net (4.69.166.57) 178 msec
ae-236-3612.edge5.London1.Level3.net (4.69.166.61) 178 msec
8 TWITTER-INC.edge5.London1.Level3.net (195.50.120.66) 157 msec 158 msec 157 m
sec
9 ae65.atl1-er2.twttr.com (192.133.76.19) 257 msec 264 msec 265 msec
10 * * *
11 * * *
12

There's no testing of the .9 which was requested and no testing from exchange to upload vlan as requested.

I suppose some hand holding will be required tonight.

I'll push for another test tonight and will do it with them to ensure that they actually do a good job and stop wasting ALL OF OUR time.

I sympathize with everyone in Cape Town who is struggling with high latency. It's not fair and it's frustrating. I assure you, we will continue to push Telkom for resolution.

-Chris

Yuu · Oct 16, 2015

@cvanwie , may i kindly ask that a notice be sent out to the CT customers only or to everyone either via email, sms or a notice on all pages on the Vox site to say that this is currently being worked on. I think it will help with those who do not visit the forum to get such detailed feedback

.

Heres hoping for a resolution after tonight's testing for all of you having problems.

Seeyou · Oct 16, 2015

Yuu said:
@cvanwie , may i kindly ask that a notice be sent out to the CT customers only or to everyone either via email, sms or a notice on all pages on the Vox site to say that this is currently being worked on. I think it will help with those who do not visit the forum to get such detailed feedback .

Heres hoping for a resolution after tonight's testing for all of you having problems.

You are overestimating Telkom

First you have to get them to look into it.

Then you have to get them to acknowledge it.

Then you have to get them to commit to fixing it.

Then you have to wait for them to fix it.

cvanwie · Oct 16, 2015

Yuu said:
@cvanwie , may i kindly ask that a notice be sent out to the CT customers only or to everyone either via email, sms or a notice on all pages on the Vox site to say that this is currently being worked on. I think it will help with those who do not visit the forum to get such detailed feedback .

Heres hoping for a resolution after tonight's testing for all of you having problems.

The problem is that not all customers in Cape Town are affected. We don't have visibility to the customers on the 3rd gen equipment that we believe is the cause of the problem.

There are a number of Cape Town users which have reported that they are not affected; imagine if we notify them that there's a problem which doesn't affect them. It's a double edge sword.

Electric · Oct 16, 2015

cvanwie said:
The problem is that not all customers in Cape Town are affected. We don't have visibility to the customers on the 3rd gen equipment that we believe is the cause of the problem.

There are a number of Cape Town users which have reported that they are not affected; imagine if we notify them that there's a problem which doesn't affect them. It's a double edge sword.

Is this only isolated to Cape Town or will this also cause the high pings that we are experiencing in PE?

AntiGanda · Oct 16, 2015

cvanwie said:
The problem is that not all customers in Cape Town are affected. We don't have visibility to the customers on the 3rd gen equipment that we believe is the cause of the problem.

There are a number of Cape Town users which have reported that they are not affected; imagine if we notify them that there's a problem which doesn't affect them. It's a double edge sword.

How could new equipment make things worse? I'd love to know the reasoning.

ghostR · Oct 16, 2015

Seeyou said:
You are overestimating Telkom

First you have to get them to look into it.

Then you have to get them to acknowledge it.

Then you have to get them to commit to fixing it.

Then you have to wait for them to fix it.

*First you have to find someone who is willing to look into it.

cvanwie · Oct 16, 2015

Electric said:
Is this only isolated to Cape Town or will this also cause the high pings that we are experiencing in PE?

I believe that PE will route through our Cape Town network as does East London

Electric · Oct 16, 2015

cvanwie said:
I believe that PE will route through our Cape Town network as does East London

Thanks

Any chance you'll be able to do some tests with me later regarding Twitch?

Aquiva · Oct 16, 2015

@cvanwie / voxy

Can anyone please help! it has been 5 days since logging the ticket, and now help to a simple question! Even the Chat Support is absolutely poor!!!

Aquiva said:
@Voxy, do you guys have SLA's/Turnaround time on tickets logged? I logged a ticket to have my debit order changed from my Credit Card to my Cheque account on Monday, and still have not received feedback.

Code:

Print 
10/16/2015 12:16:42 p.m.	Vox Telecom Support:	Welcome to IC!
12:16:42 p.m.	Vox Telecom Support:	Interaction transferred to Vox Web Chat.
12:16:42 p.m.	Vox Telecom Support:	Interaction alerting Excellent Mokoena.
12:16:46 p.m.	Vox Telecom Support:	Excellent Mokoena has joined the conversation.
12:16:57 p.m.	Excellent Mokoena:	Good day ******
12:17:17 p.m.	Excellent Mokoena:	How may I assist you this afternoon/
12:17:43 p.m.	*****.com:	Hi Mokoena, I would just like to follow up on a ticket please...
12:17:49 p.m.	*****.com:	Ref no. ATL7012539
12:18:07 p.m.	Excellent Mokoena:	Please hold while I am checking for you.
12:18:25 p.m.	*****.com:	Thanks!
12:19:40 p.m.	Excellent Mokoena:	Thanks for holding, Your query is with our accounts department. I trust you won't mind if I transfer you to Accounts.
12:19:54 p.m.	*****.com:	that would be great thanks!
12:20:08 p.m.	Excellent Mokoena:	have a lovely weekend.
12:20:12 p.m.	Vox Telecom Support:	Interaction transferred to Accounts.
12:20:12 p.m.	Vox Telecom Support:	Interaction alerting Jean-Pierre Serfontein.
12:20:36 p.m.	Vox Telecom Support:	Jean-Pierre Serfontein has joined the conversation.
12:20:52 p.m.	*****.com:	Hi Jean-Pierre
12:29:05 p.m.	*****.com:	?
12:33:32 p.m.	*****.com:	anyone? no one?
12:34:36 p.m.	*****.com:	Great! Thanks for the "great" service!
Print 
*Some links may not be valid after the chat ends.

cvanwie · Oct 16, 2015

Electric said:
Thanks
Any chance you'll be able to do some tests with me later regarding Twitch?

I just looked at this from our LAN (imagine the speed...) Twitch using Source, is still horrible using Twitch.com

I've loaded the following:

Livestreamer Twitch GUI: https://github.com/bastimeyer/livestreamer-twitch-gui/releases
Livestreamer: https://github.com/chrippa/livestreamer/releases
VLC player: http://www.videolan.org/vlc/download-windows.html

Here's the config I used: http://pastebin.com/QztBDbhD

Running source beautifully.

From what I've read about trying to watch Twitch (Source) from the Twitch website, it's not very good. Livestreamer seems to be the way forward.

The issue you're experiencing is not related to the DSL network.

Seems like Livestreamer GUI loads Livestreamer which then loads VLC.

Good luck, I hope this helps you.

Seeyou · Oct 16, 2015

cvanwie said:
I just looked at this from our LAN (imagine the speed...) Twitch using Source, is still horrible using Twitch.com

I've loaded the following:

Livestreamer Twitch GUI: https://github.com/bastimeyer/livestreamer-twitch-gui/releases
Livestreamer: https://github.com/chrippa/livestreamer/releases
VLC player: http://www.videolan.org/vlc/download-windows.html

Here's the config I used: http://pastebin.com/QztBDbhD

Running source beautifully.

From what I've read about trying to watch Twitch (Source) from the Twitch website, it's not very good. Livestreamer seems to be the way forward.

The issue you're experiencing is not related to the DSL network.

Seems like Livestreamer GUI loads Livestreamer which then loads VLC.

Good luck, I hope this helps you.

Wow, just set this up in Ubuntu. This is orders of magnitude better than twitch's own client. They should buy it and integrate ti.

Yuu · Oct 16, 2015

Seeyou said:
You are overestimating Telkom

First you have to get them to look into it.

Then you have to get them to acknowledge it.

Then you have to get them to commit to fixing it.

Then you have to wait for them to fix it.

cvanwie said:
The problem is that not all customers in Cape Town are affected. We don't have visibility to the customers on the 3rd gen equipment that we believe is the cause of the problem.

There are a number of Cape Town users which have reported that they are not affected; imagine if we notify them that there's a problem which doesn't affect them. It's a double edge sword.

Thanks for explaining, did not think this through

.

Electric · Oct 16, 2015

cvanwie said:
I just looked at this from our LAN (imagine the speed...) Twitch using Source, is still horrible using Twitch.com

I've loaded the following:

Livestreamer Twitch GUI: https://github.com/bastimeyer/livestreamer-twitch-gui/releases
Livestreamer: https://github.com/chrippa/livestreamer/releases
VLC player: http://www.videolan.org/vlc/download-windows.html

Here's the config I used: http://pastebin.com/QztBDbhD

Running source beautifully.

From what I've read about trying to watch Twitch (Source) from the Twitch website, it's not very good. Livestreamer seems to be the way forward.

The issue you're experiencing is not related to the DSL network.

Seems like Livestreamer GUI loads Livestreamer which then loads VLC.

Good luck, I hope this helps you.

Thanks, I was going this route but thought it may have been ISP related.
Nice to have some clarification and a solution.

Drifter · Oct 16, 2015

Drifter said:
Going to switch back to Google DNS tonight and see if that helps.

I did just that right now, and I have full line speed. Automatically assigned DNS gives me 10% line speed. Why would that be? I was under the impression the DSN issue has been resolved. I must add, this is since the BIG outage.

My P2P downloads went from 6kB/s this morning in off peak, to 835 kB/s now in peak.

benitok · Oct 16, 2015

Drifter said:
I did just that right now, and I have full line speed. Automatically assigned DNS gives me 10% line speed. Why would that be? I was under the impression the DSN issue has been resolved. I must add, this is since the BIG outage.

My P2P downloads went from 6kB/s this morning in off peak, to 835 kB/s now in peak.

Is that 6kB/s with Vox DNS and 835 kB/s Google DNS?

Seeyou · Oct 16, 2015

Perhaps there are still DNS problems with Vox's auto-assigned servers. Bittorrent is a connect-heavy protocol - if your client is trying and failing to resolve a lot of addresses, that could account for the poor speeds.

Join the MyBroadband community

Get started

Vox Telecom Fatpipe

Honorary Master

Honorary Master

Honorary Master

Senior Member

Executive Member

Expert Member

Senior Member

Honorary Master

Banned

Executive Member

Senior Member

Honorary Master

Senior Member

Senior Member

Expert Member

Executive Member

Honorary Master

Honorary Master

Senior Member

Expert Member