Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Genie im excited for the Gian announcement next week :D I have a feeling we are all getting a Ferrari :crylaugh:
 
AfriGenie said:
:(

Our Team has to follow basic troubleshooting steps, but we're working to improve the communication internally to make sure our Team is as up to date as possible.
Click to expand...

Yeah I get there are basic troubleshooting steps but being able to read a traceroute to make decisions should really be important.

Just taking a secion out of a provided traceroute
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 22 ms 20 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 21 ms 20 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 23 ms 20 ms 20 ms 41.162.84.192
6 29 ms 29 ms 29 ms 172.18.1.162
7 * * * Request timed out.
8 350 ms 337 ms 346 ms if-ae-2-2.tcore1.jso-johannesburg.as6453.net [216.6.55.85]
9 376 ms 350 ms 340 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
Click to expand...

So just looking at that you can tell

1) Latency to local point of presence 20ms, line fine, router fine, exchange fine, durban fine
2) Latency to Johannesburg 350ms, exceeds norm by around 300ms, problem.
3) Elevate ticket.

Quite literally you just have to know dbn, cpt, jhb and what the number should be below.
Just my 2c
 
KinsZA said:
Yeah I get there are basic troubleshooting steps but being able to read a traceroute to make decisions should really be important.

-snip
Click to expand...

Looks like this traceroute is run from KZN, our team are working on latency affecting EU routes in the area.
 
I normally see 198 - 202ms
This started yesterday already?

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

1 * * * Request timed out.
2 22 ms 22 ms 21 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 27 ms 27 ms 27 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 22 ms 21 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 22 ms 21 ms 22 ms 41.162.84.192
6 30 ms 31 ms 30 ms 172.18.1.162
7 159 ms 163 ms 170 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 418 ms 356 ms 331 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 336 ms 343 ms 354 ms if-ae-5-10.tcore2.PV9-Lisbon.as6453.net [80.231.159.93]
10 327 ms 319 ms 333 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 352 ms 340 ms 335 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 337 ms * 338 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13 327 ms 348 ms 372 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
14 334 ms 338 ms 335 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 308 ms 316 ms 320 ms 195.219.83.102
16 361 ms 368 ms 360 ms ae-3-80.edge4.Frankfurt1.Level3.net [4.69.154.136]
17 357 ms 362 ms 367 ms ae-3-80.edge4.Frankfurt1.Level3.net [4.69.154.136]
18 324 ms 316 ms 308 ms te2-2.c102.f.de.plusline.net [212.162.24.58]
19 341 ms 345 ms 351 ms 82.98.102.13
20 358 ms 347 ms 346 ms 82.98.98.250
21 356 ms 351 ms 350 ms 212.19.42.26
22 319 ms 326 ms 366 ms sipgate.de [217.10.79.9]

Trace complete.
 
AfriGuy said:
Looks like this traceroute is run from KZN, our team are working on latency affecting EU routes in the area.
Click to expand...
Should you not be routing it to a different international breakout point (or one of your other upstream providers) in the Durban area itself?
 
Hummercellc said:
Network Status all green? :whistle: maybe something should be posted there?
Click to expand...

That's something that's up to our network team I'm afraid.
Only very specific routes affecting some clients is trended as a problem, so the impact is quite small. We're updating clients reactively on a case by case basis for now.
 
AfriGuy said:
That's something that's up to our network team I'm afraid.
Only very specific routes affecting some clients is trended as a problem, so the impact is quite small. We're updating clients reactively on a case by case basis for now.
Click to expand...

A problem is still a problem, as per your network status page:

"Our DSL Broadband network is running like a bomb! Everything is copacetic and we’re good to GO!"

No, no it's not, your network is broken in the KZN region and it's simply misleading to state otherwise. Gaming and streaming are very negatively affected for a lot of people I'm speaking to. Trying to stream on a bunch of other sites now and everything is stalling (Rapidgator, nitroflare, onevideo etc)

Constantly reassuring us that the team is working on solving it, is not helpful; this is the 3rd day since it's been reported and there has been no update on whether the problem has been identified. I'm basically getting the feeling this is not a priority for you guys right now.
 
Last edited:
Lishen23 said:
A problem is still a problem, as per your network status page:

Our DSL Broadband network is running like a bomb! Everything is copacetic and we’re good to GO!

No, no it's not, your network is broken in the KZN region and it's simply misleading to state otherwise. Gaming is and streaming is very negatively affected for a lot of people I'm speaking to. Trying to stream on a bunch of other sites now and everything is stalling (Rapidgator, nitroflare, onevideo etc)

Constantly reassuring us that the team is working on solving it, is not helpful; this is the 3rd day since it's been reported and there has been no update on whether the problem has been identified. I'm basically getting the feeling this is not a priority for you guys right now.
Click to expand...

We're doing our absolute best to get the issue resolved.
 
AfriGuy said:
We're doing our absolute best to get the issue resolved.
Click to expand...

Shouldn't the first step be to ACKNOWLEDGE and INFORM your customers that you have a issue? Like in, on your status page, which still says everything is fine?

You're once again, misleading and misinforming your customers.
 
savage said:
Shouldn't the first step be to ACKNOWLEDGE and INFORM your customers that you have a issue? Like in, on your status page, which still says everything is fine?

You're once again, misleading and misinforming your customers.
Click to expand...

As above:

AfriGuy said:
That's something that's up to our network team I'm afraid.
Only very specific routes affecting some clients is trended as a problem, so the impact is quite small. We're updating clients reactively on a case by case basis for now.
Click to expand...
 
Yesss, so it's not just me having streaming issues with Afrihost. I'm like wth is going on here for 2 days because streaming is terrible on my 4Mbps line :(. Afriguy. There's someone in the Gauteng region also having streaming issues.

Check it on this thread:
http://mybroadband.co.za/vb/showthread.php/839398-Afrihost-streaming-issues

Please let us know ASAP that this is resolved. I would really like to get back to my streaming :(
 
moedawood said:
Yesss, so it's not just me having streaming issues with Afrihost. I'm like wth is going on here for 2 days because streaming is terrible on my 4Mbps line :(. Afriguy. There's someone in the Gauteng region also having streaming issues.

Check it on this thread:
http://mybroadband.co.za/vb/showthread.php/839398-Afrihost-streaming-issues

Please let us know ASAP that this is resolved. I would really like to get back to my streaming :(
Click to expand...

If you're in the KZN region you may be affected, all depends on where the stream originates from. I'll jump on that thread now.
 
No Internet access at all. Gauteng area. Connects to afrihost network and then nothing. Had to connect to MWEB to post this
 
It's back.

Code: 
Target Name: 185.60.112.158
         IP: 185.60.112.158
  Date/Time: 2016/09/02 3:51:49 PM - 2016/09/02 4:01:49 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1     2    0    1.01    1.23    1.12  home.gateway.home.gateway [192.168.1.254]
  2     1  100       0       0       0   [-]
  3     2    0    6.97    7.86    7.41  dbn-up2.ip.adsl.co.za [169.1.5.174]
  4     2    0    6.96    7.04    7.00  dbn-in1.ip.adsl.co.za [169.1.5.204]
  5     2    0    7.33    7.39    7.36  41.162.84.192 [41.162.84.192]
  6     2    0   15.48   16.05   15.76  172.18.1.162 [172.18.1.162]
  7     1    0  168.38  168.38  168.38  if-ae-7-0.tcore2.JSO-Johannesburg.as6453.net [41.206.179.13]
  8     2    0  332.88  364.60  348.74  if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
  9     2    0  325.68  357.12  341.40  if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 10     2    0  318.68  348.48  333.58  if-ae-5-20.tcore2.PV9-Lisbon.as6453.net [80.231.159.61]
 11     2    0  319.99  350.53  335.26  if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
 12     2    0  314.12  348.23  331.17  if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
 13     2    0  310.03  350.75  330.39  if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
 14     2    0  309.85  350.81  330.33  if-ae-2-2.tcore1.WYN-Marseille.as6453.net [80.231.217.1]
 15     2    0  310.75  352.79  331.77  if-ae-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
 16     2    0  305.96  353.07  329.51  if-ae-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
 17     2    0  304.01  352.77  328.39  80.231.153.66 [80.231.153.66]
 
Hi guys

Seeing a trend of queries picking up in the North region - I've asked our team to investigate urgently. I'll post updates here as soon as they're available.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X