Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Does anything like switching our DNS work?

I have given up switching DNS between yours, Googles and a combination of yours and Googles.

I just leave it on Google's permanently and switch ISPs when the MTN borked begins.

Nothing Afrihost ADSL worked this weekend, and only an ISP switch worked.
 
Google services were unusable on Saturday but improved a bit on Sunday. Youtube was buffering even on 144p, usually 1080p has no buffering. Downloading from Google drive peaked at a massive 20kbit. The routing seemed to be the problem, on FNB Connect it was under 30ms. I tried multiple DNS servers but this had no effect. Downloads on HTTP didn't seem to be a problem with speeds around 8mbit/s.

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

  1     2 ms     1 ms     2 ms  10.9.8.2 
  2     *        *        *     Request timed out.
  3    49 ms    10 ms    12 ms  41.181.54.85 
  4    23 ms    10 ms    10 ms  ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 
  5    11 ms     9 ms     9 ms  tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.186] 
  6    13 ms    10 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  7     *      225 ms   225 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66] 
  8   226 ms   225 ms   226 ms  ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114] 
  9   234 ms   234 ms   233 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183] 
 10   218 ms   220 ms   210 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141] 
 11   217 ms   218 ms   214 ms  core2.ams.net.google.com [80.249.209.100] 
 12   233 ms   234 ms   233 ms  209.85.240.63 
 13   243 ms   217 ms   222 ms  209.85.253.249 
 14   254 ms   254 ms   253 ms  216.239.48.75 
 15   254 ms   253 ms   252 ms  216.239.51.6 
 16   413 ms     *      410 ms  66.249.95.9 
 17   394 ms   393 ms   392 ms  72.14.237.239 
 18   414 ms   412 ms   413 ms  jnb01s07-in-f3.1e100.net [216.58.223.3] 

Trace complete.

This is on a 10mb line.
 
GMail won't load.... eventually after countless "This conversation could not be loaded" it loaded the e-mail I was trying to access.
Thanks Afrihost... this is it... I have had enough.

Just a quick attempt to be positive and hopefully the info will help others, when the Google issues started for me on Friday I switched my DNS from Afrihost to the Google DNS server. It helped a lot but on Saturday I switched to my Telkom account as I had time critical things to do and couldn't trust Afrihost to be stable enough.

Maybe it is a DNS issue that progressively worsened as the weekend progressed?
I am still on Telkom so can't test right now.

EDIT:

Whilst I was typing the above several others mentioned DNS, looks like I was barking up the wrong tree.
 
Last edited:
Google services were unusable on Saturday but improved a bit on Sunday. Youtube was buffering even on 144p, usually 1080p has no buffering. Downloading from Google drive peaked at a massive 20kbit. The routing seemed to be the problem, on FNB Connect it was under 30ms. I tried multiple DNS servers but this had no effect. Downloads on HTTP didn't seem to be a problem with speeds around 8mbit/s.

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

  1     2 ms     1 ms     2 ms  10.9.8.2 
  2     *        *        *     Request timed out.
  3    49 ms    10 ms    12 ms  41.181.54.85 
  4    23 ms    10 ms    10 ms  ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 
  5    11 ms     9 ms     9 ms  tb-dca-2.za--qux-i.za.mtnbusiness.net [66.8.11.186] 
  6    13 ms    10 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  7     *      225 ms   225 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66] 
  8   226 ms   225 ms   226 ms  ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114] 
  9   234 ms   234 ms   233 ms  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.183] 
 10   218 ms   220 ms   210 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141] 
 11   217 ms   218 ms   214 ms  core2.ams.net.google.com [80.249.209.100] 
 12   233 ms   234 ms   233 ms  209.85.240.63 
 13   243 ms   217 ms   222 ms  209.85.253.249 
 14   254 ms   254 ms   253 ms  216.239.48.75 
 15   254 ms   253 ms   252 ms  216.239.51.6 
 16   413 ms     *      410 ms  66.249.95.9 
 17   394 ms   393 ms   392 ms  72.14.237.239 
 18   414 ms   412 ms   413 ms  jnb01s07-in-f3.1e100.net [216.58.223.3] 

Trace complete.

This is on a 10mb line.

Thanks for this report, gives me a lot of specifics to work with. Routing definitely seems a little weird. Let's see if this can help us :)
 
Just a quick attempt to be positive and hopefully the info will help others, when the Google issues started for me on Friday I switched my DNS from Afrihost to the Google DNS server. It helped a lot but on Saturday I switched to my Telkom account as I had time critical things to do and couldn't trust Afrihost to be stable enough.

Maybe it is a DNS issue that progressively worsened as the weekend progressed?
I am still on Telkom so can't test right now.

It's possible, that's why I've asked a few people what DNS they have been using. Routing on the tests someone just posted is a little off, so not sure whether that could be DNS related. Let's see what the network guys make of it.
 
I have given up switching DNS between yours, Googles and a combination of yours and Googles.

I just leave it on Google's permanently and switch ISPs when the MTN borked begins.

Nothing Afrihost ADSL worked this weekend, and only an ISP switch worked.

Totally understand that. Would help us to know if there was a DNS related problem on our side. We should receive alerts if any part of our cluster is faling, but could make sense. I think lots of people do use Google DNS these days. Might be why some people had absolutely nothing coming through while others seemed fine except for Google services :(
 
My currently plan is I'm signing up to a secondary ISP, the better of the two by the end of this week will stay. My wife is at home sick and I don't have Dstv, we rely 100% on streaming our TV. So I'm forced to shell out from my pocket to have decent internet in the mean time.

I totally understand that. I can't say we'll have solutions in place by the end of this week, but I do hope that we can at least have some information out there so everyone of our clients can get insight into what our network is actually going through and how it will be fixed. I'm sure it may not be enough for some (respect that) but I get the sense that for many the lack of insight behind the scenes is a source of additional frustration :(
 
No , whats frustrating is that this has been happening at least twice a week the past two months.
 
Only the social media team (including MyBB) take the weekends and public holidays off). Support is available 24/7 on email, live chat and SMS and telephone lines are open till late in the week and 3pm on public holidays and weekends.

They are probably very busy then, since they haven't responded to my ticket SLE-515-71275 logged Sat, 27 Jun 2015 at 15:32.
 
Can you give me any specifics? Are other services normal but just Gmail slow? Can you maybe run a traceroute to Google or Gmail so I can take a quick look?


Tracing route to gmail.com [216.58.223.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 * * * Request timed out.
3 21 ms 21 ms * 41.181.221.213
4 * 19 ms 18 ms 41.181.221.214
5 19 ms 18 ms 18 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
6 232 ms 232 ms 256 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.15
5]
7 233 ms 232 ms * jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
8 219 ms 218 ms 218 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

9 * 225 ms 226 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
10 223 ms 223 ms * am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
11 230 ms 232 ms 233 ms core2.ams.net.google.com [80.249.209.100]
12 * 224 ms 224 ms 209.85.240.63
13 234 ms 234 ms 233 ms 209.85.253.249
14 * 246 ms * 216.239.48.77
15 245 ms 244 ms 244 ms 209.85.244.241
16 404 ms * 404 ms 66.249.95.9
17 384 ms 384 ms 401 ms 72.14.237.239
18 404 ms 404 ms * jnb01s07-in-f5.1e100.net [216.58.223.5]
19 404 ms 404 ms 425 ms jnb01s07-in-f5.1e100.net [216.58.223.5]

Trace complete.


Just logged into Gmail. Takes me about 3-7min to load an e-mail.
 
Can you give me any specifics? Are other services normal but just Gmail slow? Can you maybe run a traceroute to Google or Gmail so I can take a quick look?
Why was speedtest suddenly brilliant, yet streaming, gaming and other things so slow and unusable yesterday?
 
Why was speedtest suddenly brilliant, yet streaming, gaming and other things so slow and unusable yesterday?

I think generally speeds would have been good becuase demand and latency were low all weekend. Whatever seems to have happened seems to be some kind of anomaly.

Which DNS do you use?
 
They are probably very busy then, since they haven't responded to my ticket SLE-515-71275 logged Sat, 27 Jun 2015 at 15:32.

I think we did have a helluva lot of tickets over the weekend. I can try to see if I can get this one looked at for you :(
 
Tracing route to gmail.com [216.58.223.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 * * * Request timed out.
3 21 ms 21 ms * 41.181.221.213
4 * 19 ms 18 ms 41.181.221.214
5 19 ms 18 ms 18 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
6 232 ms 232 ms 256 ms rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.15
5]
7 233 ms 232 ms * jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
8 219 ms 218 ms 218 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

9 * 225 ms 226 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
10 223 ms 223 ms * am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
11 230 ms 232 ms 233 ms core2.ams.net.google.com [80.249.209.100]
12 * 224 ms 224 ms 209.85.240.63
13 234 ms 234 ms 233 ms 209.85.253.249
14 * 246 ms * 216.239.48.77
15 245 ms 244 ms 244 ms 209.85.244.241
16 404 ms * 404 ms 66.249.95.9
17 384 ms 384 ms 401 ms 72.14.237.239
18 404 ms 404 ms * jnb01s07-in-f5.1e100.net [216.58.223.5]
19 404 ms 404 ms 425 ms jnb01s07-in-f5.1e100.net [216.58.223.5]

Trace complete.


Just logged into Gmail. Takes me about 3-7min to load an e-mail.

Weird, it's like Google routed you to what looks like London to route you back to JHB. What DNS were you using?
 
This seems a little more extreme that the other reports I've seen here and on other social channels, support etc.
If there was a unusual problem, which seems to be the case with YouTube from the reports coming in, then hopefully we will have identified it and got something going.

Could you problem have been related to generally bad throughput and high latency. Any results you run that I could check out?

I ran the check my line tool on ClientZone from a HSDPA coonnection, everything checked out.
 
I have no words for how astoundingly terrible things are running today.

Tracing route to gmail.com [216.58.223.5]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [10.0.0.2]
2 * * * Request timed out.
3 1321 ms 1488 ms 1589 ms 41.181.53.213
4 * 1698 ms 1979 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 * 1656 ms 1478 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
6 921 ms 1712 ms 1858 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 2408 ms 2490 ms 2221 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

8 2028 ms 2421 ms 2186 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
9 1716 ms 2480 ms 2475 ms am-cr-1.nl--ls-cr-2.uk-a.mtnns.net [196.44.31.18
3]
10 1561 ms 1966 ms 2455 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
11 2170 ms 1440 ms 2002 ms core2.ams.net.google.com [80.249.209.100]
12 2320 ms 1964 ms 2186 ms 209.85.240.61
13 2349 ms 2463 ms 2286 ms 209.85.240.138
14 2297 ms 1879 ms 2001 ms 209.85.240.29
15 1881 ms * 2258 ms 216.239.51.4
16 2323 ms 1907 ms 2465 ms 209.85.244.240
17 1512 ms 1381 ms 2170 ms 72.14.232.210
18 * 1904 ms 2481 ms 216.239.43.43
19 * 2461 ms 1553 ms 72.14.232.103
20 1900 ms 1538 ms 2258 ms 72.14.237.239
21 1907 ms 2682 ms 2533 ms jnb01s07-in-f5.1e100.net [216.58.223.5]

Trace complete.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X