Vox Telecom Fatpipe

[caroper]

Good Morning Caroper

This is good to hear, we did some testing in Cape Town last night and received great results.

Regards,
Voxy

Thanks Voxy,

We only used SD, as the content she wanted had no HD version, but Streaming was fine.

Will stay on VOX for the next few days and see how it goes in general.

 

[lestoran]

Any advice on how one gets VOX support to respond to a query?

My card payment failed for some strange reason and my account got suspended as I missed the email notification thinking its a statement.

Paid immediately by EFT and sent a note to VOX support asking to re-enable my account. That was yesterday morning at about 7 and so far all I have received is an automated notification.

Not looking good next to CrystalWeb who both times I mailed answered in under an hour...

2 days later and still no response to my query and my online statement still shows I'm overdue :-(

Seriously VOX this not acceptable!

 

[Valhallan]

Streaming youtube was slightly better this morning/ but still not as good as it was. I run DU meter which gives non-averaged per sec throughput readings on internet traffic.

In the past I could play 2160p and traffic would read full speed between 2MB/s and 2.2MB/s but I'm still only achieving +-300KB/s

Just enough to play 1080p without too much buffering but not as good as it was. Been like this since the international links went down.

23mb/s sync - FatPie
FTP/ speedtest giving full speed

 

[Voxy]

Vox was superb yesterday and last night.

Yay.

Here's hoping it is back to its' amazeballsness!

Hi igotissues

This is good to hear. We will be doing testing tonight to see where we can further improve.

Regards,
Voxy

 

[Voxy]

Last night +- 10PM youtube streaming on 1080 was useless - buffering

Ave 2.5Mbps some peaked up to 5Mbps on my 20Mbps VDSL line

Netflix USA was fine but then again that's only 720p anyways....(Android box)

Cape Town - South Peninsula

Hi avr-rulez

I apologise for this. We will be looking into this issue tonight to see why some are experiencing issues and others none.

 

[Voxy]

2 days later and still no response to my query and my online statement still shows I'm overdue :-(

Seriously VOX this not acceptable!

Hi lestoran

Have you spoken to our accounts team? Or do you have an account manager?

 

[roguemat]

My connection is dead in Durban. Is there any general issue right now?

 

[roguemat]

My connection is dead in Durban. Is there any general issue right now?

 

[caroper]

fine in cape town

 

[Voxy]

My connection is dead in Durban. Is there any general issue right now?

My connection is dead in Durban. Is there any general issue right now?

Hi roguemat

No known issues.
Have you spoken to our support desk yet?

Regards,
Voxy

 

[Soul Assassin]

Voxy on the ball today, I like it.

 

[fragtion]

Hi Voxy. Thanks for the updates and it's really great news to hear that things are improving in CPT now. Are there any similar developments or ETA timelines with regards to the high evening latency in JHB, namely between 41.193.164.85 and 41.193.164.86? Thank you

 

[Voxy]

Hi fragtion

PM me your account details and I will call you tonight to do some testing.

Regards,

 

[Voxy]

Voxy on the ball today, I like it.

Hi

Lol, ja was a bit off it the past week.

 

[Adenoid Hynkel]

Why is traffic being routed from CT to JNB and back to CT? This has been going on for a while now.

 

[Mr.Jax]

Vox

Latency is not looking good in the evenings (Pretoria). It's been like this for the past few weeks already:
Occasional packet loss also observed.


Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=39ms TTL=55
Reply from 216.58.223.3: bytes=32 time=57ms TTL=55
Reply from 216.58.223.3: bytes=32 time=55ms TTL=55
Reply from 216.58.223.3: bytes=32 time=61ms TTL=55
Reply from 216.58.223.3: bytes=32 time=68ms TTL=55
Reply from 216.58.223.3: bytes=32 time=68ms TTL=55
Reply from 216.58.223.3: bytes=32 time=67ms TTL=55
Reply from 216.58.223.3: bytes=32 time=67ms TTL=55
Reply from 216.58.223.3: bytes=32 time=66ms TTL=55
Reply from 216.58.223.3: bytes=32 time=60ms TTL=55

Ping statistics for 216.58.223.3:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 68ms, Average = 60ms


Tracing route to google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 19 ms 19 ms 19 ms 41.193.3.101
4 19 ms 42 ms 19 ms 41.193.3.102
5 35 ms 34 ms 31 ms 196.41.12.0
6 66 ms 65 ms 66 ms 41.193.32.137
7 53 ms 55 ms 56 ms 41.193.32.198
8 70 ms * 59 ms 41.193.119.90
9 * 64 ms 71 ms 72.14.220.136
10 20 ms 20 ms 20 ms 72.14.237.239
11 68 ms 63 ms 60 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Tracing route to voxtelecom.co.za [196.41.6.140]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 19 ms 20 ms 19 ms 41.193.3.101
4 31 ms 61 ms 23 ms 41.193.3.102
5 32 ms 29 ms 28 ms 196.41.12.0
6 20 ms 20 ms 20 ms 196.41.6.140

Using an Afrihost free account, all latencies are good to go.

Please fix.

 

[Voxy]

Vox

Latency is not looking good in the evenings (Pretoria). It's been like this for the past few weeks already:
Occasional packet loss also observed.


Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=39ms TTL=55
Reply from 216.58.223.3: bytes=32 time=57ms TTL=55
Reply from 216.58.223.3: bytes=32 time=55ms TTL=55
Reply from 216.58.223.3: bytes=32 time=61ms TTL=55
Reply from 216.58.223.3: bytes=32 time=68ms TTL=55
Reply from 216.58.223.3: bytes=32 time=68ms TTL=55
Reply from 216.58.223.3: bytes=32 time=67ms TTL=55
Reply from 216.58.223.3: bytes=32 time=67ms TTL=55
Reply from 216.58.223.3: bytes=32 time=66ms TTL=55
Reply from 216.58.223.3: bytes=32 time=60ms TTL=55

Ping statistics for 216.58.223.3:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 68ms, Average = 60ms


Tracing route to google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 19 ms 19 ms 19 ms 41.193.3.101
4 19 ms 42 ms 19 ms 41.193.3.102
5 35 ms 34 ms 31 ms 196.41.12.0
6 66 ms 65 ms 66 ms 41.193.32.137
7 53 ms 55 ms 56 ms 41.193.32.198
8 70 ms * 59 ms 41.193.119.90
9 * 64 ms 71 ms 72.14.220.136
10 20 ms 20 ms 20 ms 72.14.237.239
11 68 ms 63 ms 60 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Tracing route to voxtelecom.co.za [196.41.6.140]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 19 ms 20 ms 19 ms 41.193.3.101
4 31 ms 61 ms 23 ms 41.193.3.102
5 32 ms 29 ms 28 ms 196.41.12.0
6 20 ms 20 ms 20 ms 196.41.6.140

Using an Afrihost free account, all latencies are good to go.

Please fix.

Hi

I'm glad to hear
Though i stayed up to loon for issues....

Hope you experience stays good though.

Regards,
Voxy

 

[MickeyD]

Hi

I'm glad to hear
Though i stayed up to loon for issues....

Hope you experience stays good though.

Regards,
Voxy

I think you should re-read the post...

 

[Seeyou]

Things are still pretty crappy at night in CPT. 3000ms+ pings to the Tygerberg IPC hop makes everything feel sluggish.

 

[Drifter]

Evenings have been the issue for a while now. Seems like they cant get it fixed. After 18:00 everything slows down to a crawl, even though speed tests show normal. Oh, and I am on the capped package.