diepeterpan
Well-Known Member
Our team is seeing some progress on this, services should return to normal soon.
Where were u last night Afriman! Seems like you got the ball rolling, can we duplicate you
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Our team is seeing some progress on this, services should return to normal soon.
Where were u last night Afriman! Seems like you got the ball rolling, can we duplicate you![]()
LOL.
As much as I'd like to say I helped fix it, I didn'tGot home from a family holiday earlier this morning and saw things where a little pear shaped. Coincidence that it was fixed up after I arrived
Just to update you guys quickly, monitoring looks to be returning to normal and we're seeing good reports on Twitter/ Facebook. We'll continue to monitor though. I'm gonna need more coffee!
Anybody got recommendations for a better ISP than Afrihost?
My requirements are:
- Have a stable network
- Actually do something about network issues
- Business accounts with no shaping/limits
- Reasonable price.
Hi guys
I'm sincerely sorry about the lack of feedback here, I understand that the South IPC has been an issue since yesterday.
We are working hard on getting this sorted out - I'll have any updates posted here as soon as they're available.
Looks like pretty severe congestion. I can imagine this must be really awful![]()
Tracing route to saix.net [196.25.1.204]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 497 ms 717 ms 1028 ms 196-210-144-129.dynamic.isadsl.co.za [196.210.144.129]
3 1204 ms 912 ms 752 ms 196.38.73.113
4 595 ms 640 ms 776 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 816 ms 808 ms 882 ms 168.209.1.140
6 1230 ms 1262 ms 924 ms 196.26.0.130
7 613 ms 1011 ms 1108 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.46.89]
8 971 ms 990 ms 1004 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 830 ms 475 ms 228 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
10 * * wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] reports: Destination net unreachable.
Trace complete.
So this is it? Telkom just saying they don't see congestion, if there is I need to contact my ISP but it's out of Afrihost's hands and I should just make peace with being F***edThose telkom reps you talk to are SO clueless
A previous time I asked them how to report exchange congestion and the guy had NO CLUE what i was talking about... Asked if I could repeat it in layman's terms
:wtf: He actually forwarded me to an accounts department after I repeated the question a couple of times...
no jokes...
Here we go again!!!!!
Latency through the roof.... Still having issues browsing.
Telkom Tech just left my house (YES! On a Sunday!)... line test perfectly on both his modem and my router, and on 4 different ISP accounts.
Afrihost accounts (Business and Capped) STILL causing problems.
W T F ???????
AfriGuy I just want to understand how come it takes Afrihost 12+ hours to update the status on the site. Lots of people have been complaining about this slow response, but we've seen no improvement. That is the first port of call for lots of people, but we end up having to resort to forums to figure out problems.
This lack of immediate transparency is probably the biggest thing currently driving me away as a customer. Your customer service and openness was the reason I switched to you in the first place.
I don't want Gian begging for forgiveness weeks after issues surface. I want to go to your site and see there is a balls up in my region. It is not mass panic when you say on the site we've received reports of xyz happening. More updates coming.
Really disappointing service again for the nth time.
Shame. Why did you have Telkom send someone over when we're all aware that Afrihost has collapsed in the South? You could have tested a free Web Africa or Telkom guest account yourself.
YouTube borked again??? No local cache anymore?
All Google sites are now being routed internationally.
Even 240p buffering, oh the joy...
Tracing route to youtube.com [74.125.233.0]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
3 24 ms 24 ms 23 ms 41.181.221.214
4 24 ms 24 ms 23 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 229 ms 205 ms 205 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
6 70 ms 222 ms 72 ms ct-cr-2.za--rb-cr-1.za.mtnns.net [196.44.31.68]
7 45 ms 256 ms 45 ms ct-cr-1.za--ct-cr-2.za-a.mtnns.net [196.44.31.109]
8 211 ms 237 ms 234 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
9 237 ms 232 ms 228 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
10 229 ms 204 ms 223 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
11 208 ms 214 ms * 209.85.255.76
12 238 ms 209 ms 233 ms 66.249.95.9
13 210 ms 187 ms 204 ms 72.14.237.239
14 255 ms 230 ms 217 ms jnb01s07-in-f0.1e100.net [74.125.233.0]
Trace complete.
Yip, I know, can't stream anything higher than 480p and that evens buffers at times.....
But Afriguy says it's an isolated incident and not affecting everyone.....
When I leave soon, guess it's not going to affect them as well....