Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Unless some logs can be accessed regarding what happened last night, checking the network now for issues is next to pointless. As explained the problem only showed up in the evening so they need to wait till the evening until any issues will crop up. My account type is capped dsl. Cheers.

Last nights traffic was reviewed, our Network team know that running checks now for an issue that was reported last night doesn't work ;) Please run the tests I suggested on post #5913.
 
Last nights traffic was reviewed, our Network team know that running checks now for an issue that was reported last night doesn't work ;) Please run the tests I suggested on post #5913.

Good to know. Unfortunately it seems your logging might be ineffective, but that is to be expected I guess.
I'll be back on google dns for the foreseeable future, so I won't run into the issue again.
 
Good to know. Unfortunately it seems your logging might be ineffective, but that is to be expected I guess.
I'll be back on google dns for the foreseeable future, so I won't run into the issue again.

Bit unfair to criticise our logging, if we see trending issues we get on them and fix them - there haven't been any trending issues. As mentioned, if you do continue to experience issues please run the recommended tests and paste the data here so we have a better idea of what's going on.
 
Bit unfair to criticise our logging, if we see trending issues we get on them and fix them - there haven't been any trending issues. As mentioned, if you do continue to experience issues please run the recommended tests and paste the data here so we have a better idea of what's going on.

I said it seems ineffective to me as you couldn't detect myself and jannier's issue that in all likelihood affected many more users as well. As I said I will be running google dns so won't be able to provide you with any tests related to afri's dns.
 
I said it seems ineffective to me as you couldn't detect myself and jannier's issue that in all likelihood affected many more users as well. As I said I will be running google dns so won't be able to provide you with any tests related to afri's dns.

If there was something we saw on your sessions that we could fix, we would. That wasn't the case, we couldn't pick up any issues on both sessions.
 
Mind running Google's DNS servers now until this evening to see if the issues can be replicated?

FYI: I had the exact same problems last night. I did switch to Google's DNS, and the problem did not resolve. Some videos would scream down the pipe, others would only work at lower resolutions.

Sometimes videos would play at lower resolutions up to a point, and then just stop - necessitating a switch to a different resolution to continue. (Sometimes this was, strangely, a higher resolution. And some videos I could never get to start.)

My DNS does reset to Afrihost though once the connection drops - will check tonight if it is still on Google and report back if it happens again.
 
FYI: I had the exact same problems last night. I did switch to Google's DNS, and the problem did not resolve. Some videos would scream down the pipe, others would only work at lower resolutions.

Sometimes videos would play at lower resolutions up to a point, and then just stop - necessitating a switch to a different resolution to continue. (Sometimes this was, strangely, a higher resolution. And some videos I could never get to start.)

My DNS does reset to Afrihost though once the connection drops - will check tonight if it is still on Google and report back if it happens again.

Very odd, please grab some tests tonight if you see this re-occur :)
 
Have been using telkom as isp for almost 2 years now and am happy. Got the email about the R1 promo and though il try a capped account from afrihost. Using a 10mb adsl line syncing at the full 10 and am in fibre area so exchanges etc have been upgraded

Man they suck. Every afternoon cannot stream YouTube bbc iplayer or netflix which 90% of the time would work on telkom at any time of the dah or night.

Cant open reddit or imgur or other sites do not display any pictures.

Hopeless
 
Hi guys

Just added a notice to the site, we're seeing high latency to international destinations affecting our North IPC.

DSL Status said:
We’re seeing reports of high latency affecting international services for clients in the North (Gauteng and surrounds).
Our team are aware and working with upstream providers to see latency normalised.
 
Have been using telkom as isp for almost 2 years now and am happy. Got the email about the R1 promo and though il try a capped account from afrihost. Using a 10mb adsl line syncing at the full 10 and am in fibre area so exchanges etc have been upgraded

Man they suck. Every afternoon cannot stream YouTube bbc iplayer or netflix which 90% of the time would work on telkom at any time of the dah or night.

Cant open reddit or imgur or other sites do not display any pictures.

Hopeless

Sorry to hear about the poor experience here :(
Are you only seeing the issues now, or before today too? We're seeing international latency affecting clients in the North which may be the cause. Where abouts are you based?
 
Sorry to hear about the poor experience here :(
Are you only seeing the issues now, or before today too? We're seeing international latency affecting clients in the North which may be the cause. Where abouts are you based?
For a few days. Generally during the afternoon. Based in central Johannesburg
 
The East not looking so good.

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 21ms, Average = 14ms



Pinging afrihost.com [104.20.31.244] with 32 bytes of data:
Request timed out.
Reply from 104.20.31.244: bytes=32 time=538ms TTL=58
Reply from 104.20.31.244: bytes=32 time=30ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 104.20.31.244: bytes=32 time=1448ms TTL=58
Request timed out.
Request timed out.
Reply from 104.20.31.244: bytes=32 time=1629ms TTL=58
Reply from 104.20.31.244: bytes=32 time=31ms TTL=58
Reply from 104.20.31.244: bytes=32 time=32ms TTL=58
Request timed out.
Reply from 104.20.31.244: bytes=32 time=72ms TTL=58

Ping statistics for 104.20.31.244:
Packets: Sent = 17, Received = 7, Lost = 10 (58% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 1629ms, Average = 540ms

Tracing route to afrihost.com [104.20.31.244]
over a maximum of 30 hops:

1 * * * Request timed out.
2 30 ms 27 ms 29 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 27 ms 27 ms 28 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 27 ms 26 ms 26 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 27 ms 27 ms 27 ms 41.162.84.192
6 36 ms 45 ms 29 ms 172.18.1.162
7 59 ms 38 ms 48 ms cloudflare.ixp.joburg [196.46.25.198]
8 30 ms * * 104.20.31.244
9 3560 ms 30 ms 31 ms 104.20.31.244

Trace complete.



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

1 * * * Request timed out.
2 23 ms 20 ms 21 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 31 ms 28 ms 28 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 23 ms 21 ms 21 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 54 ms 54 ms 53 ms optinet.ixp.durban [196.10.141.75]
6 71 ms 71 ms 69 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
7 80 ms 78 ms 75 ms te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
8 93 ms 96 ms 90 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
9 74 ms 72 ms 70 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
10 69 ms 69 ms 121 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
11 88 ms 107 ms 104 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

12 * * * Request timed out.
13 * * * Request timed out.
 
Hi guys

Just added a notice to the site, we're seeing high latency to international destinations affecting our North IPC.

Since Durban traffic seems to route through JHB and then down to Cape Town. Does the East IPC get affected by things that affect the North IPC or are they completely separate things?
 
Since Durban traffic seems to route through JHB and then down to Cape Town. Does the East IPC get affected by things that affect the North IPC or are they completely separate things?

It should be separate, just waiting on confirmation from our Networking team :)
 
I could try that a bit later

Revert to auto dns and run which test?

Yeah, auto-DNS and then let's take a look at a local and international speedtest and a few traceroutes and take it from there :)
We'll need to wait for the current latency issue to be fixed up though.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X