There's definitely something wrong here, could you PM me your line number so I can check things out?
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your stance on AI?
Afrihost Business Uncapped Feedback
- Thread starter Lino
- Start date
- Status
There's definitely something wrong here, could you PM me your line number so I can check things out?
Crusader
Executive Member
Guys on your Twitter account are trying to assist. Will reset line and see if that helps.
MrGray
Honorary Master
The MSSQL/MySQL connectivity problems that started on Monday night with our Capped and Business Uncapped accounts have still not been resolved. If it isn't better by tomorrow, we have no choice but to cancel our Afrihost accounts and ask for a refund for October as we simply cannot use them for our core business purpose.
Even when it sort of works, so many packets are dropped that it is too slow to do anything. Frequently, sql client connections time out. I have analysed the traffic on wireshark, and while I am not a network guru, the most obvious difference between a connection with any other ISP and Afrihost is that on Afrihost it looks like packets bigger than about 1200 bytes mostly fail - this must be why it sometimes works better with the MySQL compression turned on as that seems to generate smaller packets. And no, it is not our MTU setting on the router.
There has been email communication back and forth with critical care but there is always a long delay between each response, which has gone like this:
Tues morning: "We block access to our shared servers".
My response: We don't use your shared servers, I don't understand your response.
Tues afternoon: Got a phone call from someone who sounded very concerned, promised to get back to me. Connectivity deteriorated. Sent an email pointing out it was worse - responded that he'd respond first thing next morning. Never heard from that person again.
Wed morning (1am?! - is the support in India?): "We don't block ports, check your router/firewall"
My response: The port is not blocked. That is not the point. Re-explained the problem.
Thur morning (2am!?): "Check your MTU, set it to 1492".
My Response: It has always been 1492. Nothing has changed.
So, four days into this and absolutely no progress. I await tomorrow morning's 2am response with interest.
Even when it sort of works, so many packets are dropped that it is too slow to do anything. Frequently, sql client connections time out. I have analysed the traffic on wireshark, and while I am not a network guru, the most obvious difference between a connection with any other ISP and Afrihost is that on Afrihost it looks like packets bigger than about 1200 bytes mostly fail - this must be why it sometimes works better with the MySQL compression turned on as that seems to generate smaller packets. And no, it is not our MTU setting on the router.
There has been email communication back and forth with critical care but there is always a long delay between each response, which has gone like this:
Tues morning: "We block access to our shared servers".
My response: We don't use your shared servers, I don't understand your response.
Tues afternoon: Got a phone call from someone who sounded very concerned, promised to get back to me. Connectivity deteriorated. Sent an email pointing out it was worse - responded that he'd respond first thing next morning. Never heard from that person again.
Wed morning (1am?! - is the support in India?): "We don't block ports, check your router/firewall"
My response: The port is not blocked. That is not the point. Re-explained the problem.
Thur morning (2am!?): "Check your MTU, set it to 1492".
My Response: It has always been 1492. Nothing has changed.
So, four days into this and absolutely no progress. I await tomorrow morning's 2am response with interest.
Thanks, I'll follow up with them on the feedback.
Has this info been passed onto our Critical Care team? I believe they're still running tests with you.
I haven't been able to replicate any of the issues on my end.
MrGray
Honorary Master
Yes, that was on Tuesday, and the last email response was they'd get back to us on Wednesday. I kind of assumed that they would be included on the subsequent communications - is it up to me to discern which email communications are from "critical care" and which are not?
You'll be dealing with one of the guys from the team
I'll see who you've been dealing with to see if I can get you some feedback.
Crusader
Executive Member
The line reset didn't help much.
Here's the result from the Afrihost network test.
Here's the result from the Afrihost network test.
Code:
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=50 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=76 ms
Request timeout for icmp_seq 3
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=54 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=48 ms
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=174 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=218 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Trace Test:
traceroute -n 197.242.144.102
1 192.168.0.1 1 ms 1 ms
2 105.236.4.1 27 ms 29 ms
3 41.181.221.2 24 ms 35 ms
4 196.44.18.2 30 ms
41.181.198.1 26 ms
5 196.44.31.6 51 ms
196.44.18.2 25 ms
6 196.44.0.2 64 ms
196.44.31.1 27 ms
7 196.30.1.5 52 ms
196.44.31.6 55 ms
8 196.31.63.2 73 ms
196.30.1.5 59 ms
9 196.30.42.1 50 ms
196.31.220.2 58 ms
10 196.31.63.2 47 ms
11 197.242.144.1 70 ms
traceroute -n 8.8.8.8
1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.4.1 23 ms
Request timed out * *
3 41.181.53.2 37 ms
Request timed out * *
4 Request timed out * * *
5 Request timed out * *
196.44.18.2 30 ms
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 * *
13 Request timed out * *
14 Request timed out * *
15 Request timed out * *
16 Request timed out *
17 Request timed out *
18 Request timed out *
19 Request timed out *
20 Request timed out *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *
29 Request timed out *
30 Request timed out *
DNS Test:
nslookup www.afrihost.com
Name: www.afrihost.com
Address: 197.242.144.102
nslookup www.google.com
Name: www.google.com
Address: 74.125.230.241
Name: www.google.com
Address: 74.125.230.240
Name: www.google.com
Address: 74.125.230.244
Name: www.google.com
Address: 74.125.230.243
Name: www.google.com
Address: 74.125.230.242
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAINI see our team on Twitter are still troubleshooting this with you.
richardrpg
Well-Known Member
- Joined
- Jan 11, 2013
- Messages
- 198
- Reaction score
- 2
And now for the 3rd day in a row, get to 3pm and all my torrents just crash, they now fluctuate between 5kb/s to max 40kb/s.
But I suppose I'll just wait till 10pm as usual and then they all run at full speed again once shaping on other packages eases.
2mb Business Line Cape Town.
But I suppose I'll just wait till 10pm as usual and then they all run at full speed again once shaping on other packages eases.
2mb Business Line Cape Town.
Ok this is officially bull****!!!
Line was completely down from Sat till Tue night.
Get home today and guess what, line dead again!
Paying for a "premium service" but can even get it to work.
You have fail Afrihost, I always recommended you but no more.
The we will get better and stronger excuse doesn't work anymore.
Before you ask for tracert (which I can't do or keeps timing out), my log # is ZCL-387-49572.
And that is just one of many log on the system still open since beginning of Sept.
Line was completely down from Sat till Tue night.
Get home today and guess what, line dead again!
Paying for a "premium service" but can even get it to work.
You have fail Afrihost, I always recommended you but no more.
The we will get better and stronger excuse doesn't work anymore.
Before you ask for tracert (which I can't do or keeps timing out), my log # is ZCL-387-49572.
And that is just one of many log on the system still open since beginning of Sept.
Apologies for this, has any feedback been given around the fault that was logged?
We do our best to have Telkom attend to faults as quickly as possible - but it does depend on their workload in the area at the end of the day
Apologies for this, has any feedback been given around the fault that was logged?
We do our best to have Telkom attend to faults as quickly as possible - but it does depend on their workload in the area at the end of the day
No feedback has been given.
And I'm in Centurion so don't think it would take 6days for Telkom to fix a problem/exchange port. Maybe in Twee buffels met een skoot door geskiet fontein...
I'll have this fault escalated for you, however I see the latest update is that there's no dialtone on your voice line either?
Is this still the case?
Yes, dead as a dodo dead.
No dialtone will result in no DSL
Can you give Telkom a shout and have a fault logged for voice on your end please?
Nothing has been confirmed at this stage.
requiem
Expert Member
- Joined
- May 10, 2009
- Messages
- 4,070
- Reaction score
- 1,161
So the email I got is lying?
- Status