Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Shaping profiles are identical, both being unshaped.
As mentioned, please continue to troubleshoot with our Critical Care team.
I will do so. But after 2 months of back and forth to Critical Care I expect to see results now. I am sure you can understand my frustration.
Thank you for your time. Hopefully CC will sort it out once and for all. Tired of this.
Have a good evening.
 
sipgate telkom
Traceroute has started…

traceroute to sipgate.de (217.10.79.9), 64 hops max, 72 byte packets
1**fritz.box (192.168.178.1)**0.634 ms**0.421 ms**0.301 ms
2*** * *
3**wblv-ip-hsll-2-gi3-0-0-vl102.telkom-ipnet.co.za (105.226.0.5)**40.916 ms**39.369 ms**39.389 ms
4**ipc-1-up.south.dsl.telkomsa.net (105.226.0.6)**41.077 ms**40.348 ms**38.963 ms
5**ipc-aggr-1.south.dsl.telkomsa.net (105.226.0.13)**46.820 ms**46.278 ms**46.340 ms
6**wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45)**46.486 ms**46.691 ms**46.115 ms
7**fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.110)**209.881 ms**209.574 ms**209.695 ms
8**c13-1.netzquadrat.net (80.81.192.75)**202.526 ms**202.253 ms**203.173 ms
9**sipgate.de (217.10.79.9)**202.677 ms**202.298 ms**202.385 ms

Tracing route to sipgate.de [217.10.79.9]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.138
2 10 ms 8 ms 7 ms 194-166-247-254.adsl.highway.telekom.at [194.166.247.254]
3 27 ms 18 ms 30 ms AUX1-GRAX1.highway.telekom.at [195.3.68.129]
4 * * * Request timed out.
5 26 ms 25 ms 25 ms c13-1.netzquadrat.net [80.81.192.75]
6 48 ms 43 ms 49 ms sipgate.de [217.10.79.9]

Trace complete.

Pinging sipgate.de [217.10.79.9] with 32 bytes of data:
Reply from 217.10.79.9: bytes=32 time=51ms TTL=58
Reply from 217.10.79.9: bytes=32 time=47ms TTL=58
Reply from 217.10.79.9: bytes=32 time=59ms TTL=58
Reply from 217.10.79.9: bytes=32 time=49ms TTL=58

Ping statistics for 217.10.79.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 59ms, Average = 51ms

Wish I had latency like this in South Africa :(
All good at home in RSA as well from what my family tells me.
 
10 pm (literally on the dot) my p2p is back to full speed. So is international throughput.

Google play store still wonky though.

EDIT: 10:05 pm and Google play store back to normal as well.
 
Last edited:
10 pm (literally on the dot) my p2p is back to full speed. So is international throughput.

Google play store still wonky though.

EDIT: 10:05 pm and Google play store back to normal as well.

Also been having terrible speeds the last hour or so. Seems to be better now though
 
10 pm (literally on the dot) my p2p is back to full speed. So is international throughput.

Google play store still wonky though.

EDIT: 10:05 pm and Google play store back to normal as well.

Glad to hear things are back to normal! :) Please make sure to report your findings to our CC Team.
 
Hectic again this morning. Request time outs and all. Cape Town East region.

Latency to high to attach a screen-shot from trace software...


tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * 420 ms * 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 478 ms * 530 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 424 ms 426 ms 420 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 449 ms * 492 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 451 ms 415 ms 448 ms 41.164.52.40
7 440 ms 410 ms 391 ms 172.18.1.162
8 487 ms 506 ms * 72.14.194.206
9 * 449 ms 429 ms 72.14.237.239
10 * 412 ms * www.google.com [216.58.223.4]
11 * 429 ms 406 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 401 ms 412 ms 405 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 * * * Request timed out.
4 421 ms 427 ms 426 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 489 ms * 472 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 * 428 ms 489 ms 41.164.52.40
7 * 443 ms 419 ms 172.18.1.162
8 519 ms * * 72.14.194.206
9 444 ms 425 ms 439 ms 72.14.237.239
10 * 437 ms 436 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.
 
And there goes mybroadband also.

Website is offline
No cached version of this page is available.
Error 522 Ray ID: 2c1b1c24eabf15f2 • 2016-07-13 07:44:48 UTC
Connection timed out

:wtf:
 
Lots of timed out requests, high ping, and fluctuating ping for me in Cape Town.

Problem was present yesterday, and is unfortunately still present this morning.

General browsing and streaming experience is poor.

Hopefully the tech team figures out what's going on soon.
 
Local Latency also high in KZN.
All Mweb Sites are timing out



Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 148 ms 141 ms 156 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 17 ms 15 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 15 ms 15 ms 16 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 131 ms 125 ms 128 ms optinet.db1.napafrica.net [196.10.141.75]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
 
Local Latency also high in KZN.
All Mweb Sites are timing out



Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 148 ms 141 ms 156 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 17 ms 15 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 15 ms 15 ms 16 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 131 ms 125 ms 128 ms optinet.db1.napafrica.net [196.10.141.75]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

Was it like that yesterday as well?
 
Yeah for a bit, I was not able to access News24 yesterday.

It only seems to be Afrihost, My IS account can access Mweb Sites.

I was surprised to see that the network status is green on the Afrihost site this morning. Figured they would've realized and drawn attention to the problem by now.

A lot of sites today are timing out and only load upon refreshing the page.

At least you've got another account to use instead.
 
Same here. For the last 3 nights I have not been able to use News24.com In the day it is fine but in the evening it is as if someone just pulled the plug. Just will not load.
 
Hectic again this morning. Request time outs and all. Cape Town East region.

Latency to high to attach a screen-shot from trace software...


tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * 420 ms * 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 478 ms * 530 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 424 ms 426 ms 420 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 449 ms * 492 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 451 ms 415 ms 448 ms 41.164.52.40
7 440 ms 410 ms 391 ms 172.18.1.162
8 487 ms 506 ms * 72.14.194.206
9 * 449 ms 429 ms 72.14.237.239
10 * 412 ms * www.google.com [216.58.223.4]
11 * 429 ms 406 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 401 ms 412 ms 405 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 * * * Request timed out.
4 421 ms 427 ms 426 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 489 ms * 472 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 * 428 ms 489 ms 41.164.52.40
7 * 443 ms 419 ms 172.18.1.162
8 519 ms * * 72.14.194.206
9 444 ms 425 ms 439 ms 72.14.237.239
10 * 437 ms 436 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

Latency seems to be coming in really early here... Do you have another test account that you could compare results with?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X