Its weird because he has over 1000ms pings to his exchange - causing issues! However, although it shows that he has the same on MWEB, he says that it doesnt affect him? I know there are capcity issues, but I don't think this has anything to do with them
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your preferred computer operating system?
Afrihost Business Uncapped Feedback
- Thread starter Lino
- Start date
- Status
Its weird because he has over 1000ms pings to his exchange - causing issues! However, although it shows that he has the same on MWEB, he says that it doesnt affect him? I know there are capcity issues, but I don't think this has anything to do with them
i.got~issues
Expert Member
Zertop ... thanks for all your input.
For me the proof is in the using, and now on Mweb, my Skype is working, my Teamviewer is OK, Cirtix VPN is fine etc.
This weekend Citrix was a nightmare on AH. Constant disconnects. It used to be just fine.
A simple test I run is Twitch.tv. Not a scientific test, but it points to something not right.
Twitch used to work on Afrihost business on medium without buffering. Then something changed, it cannot stream now without buffering every 20-30s. All the time.
I switch to WebAfrica, and it streams smoothly... for as long as I leave it running, it streams on medium, and sometimes on high, without a buffer at all.
I stream on Mweb or Axxess buffer-free on medium for as long as the stream is open.
On Afrihost, it cannot stream on medium without constant buffering. It does not matter what time of day or night, or which stream, it buffers. Constantly.
If there is a line fault or exchange issue, I need this to be resolved. It will only be a matter of time before every ISP becomes schizo like AH is now.
If Telkom report back that all is OK, well then, time to give one of the others a run and see how long they behave for.
Your input and these tests have been very helpful. The last Mweb one shows that there is something amiss.
Perhaps these other ISPs are more fault tolerant than AH?
Thanks again for your time and input.
Firstly - no probs
Always happy to helpSecondly - Yea, i genuinely have no clue. It could be (as Chevron said), a capacity issue. However that doesn't explain the ridiculous pings. I guess if MWEB works for you, thats what you are going to have to use for now until you get some proper answers.
Z
eddief1
Expert Member
- Joined
- Feb 26, 2008
- Messages
- 1,523
- Reaction score
- 301
You can ping the exchange :wtf: I think you got it wrong, you actually pinging the ESR...the exchange is transparent and will not show up on pings and tracert's
Correct me if I'm wrong.
Hectic
Executive Member
I think I would agree with Zertop ito there is either a line fault or more probably exchange congestion at times.
I have seen several people mentioning that it seems that Telkom are working on lines and it seems to create havoc atm.
Not sure if that is applicable to the WC, maybe more in the rain affected areas?
I have seen several people mentioning that it seems that Telkom are working on lines and it seems to create havoc atm.
Not sure if that is applicable to the WC, maybe more in the rain affected areas?
Yea, definitely a line issue - cause thats pinging your exchange, and should be under ~25ms at all times! I think the best thing would be to report a fault
That could account for all your issues.
My networking knowledge is obviously not quite where you guys are (although its not bad
).A quick question then.
Why is i.got~issues MWEB Exchange IP 197.84.96.138, but his Afrihost Exchange IP 41.181.53.150. Is the exchange not the grey Telkom box sitting 1-3km away from his place? Why then do different ISP's use different Exchange IP's, if it's the same box?
My networking knowledge is obviously not quite where you guys are (although its not bad
A quick question then.
Why is i.got~issues MWEB Exchange IP 197.84.96.138, but his Afrihost Exchange IP 41.181.53.150. Is the exchange not the grey Telkom box sitting 1-3km away from his place? Why then do different ISP's use different Exchange IP's, if it's the same box?
The little grey box is called a DSLAM. Its pretty much the link between the Exchange and the User. The exchange is a physical building in a town where all the telkom lines come into. The "exchange" per se isn't shown, but rather is the middle link. The second hop of a tracert shows not the exchange, but rather the place just before getting onto the ISP's network.
Therefore - we can use it to calculate whether the problem lies with the ISP, or whether it lies with the line/exchange. Each ISP has a different "handler", which accounts for the different IP's
I could be wrong, because my knowledge on this isn't the greatest - but someone else should be able to tell you if that is correct
CrazYmonkeY159
Expert Member
I am sort of stuck as to where to go
I have sent a lengthy ticket to Afrihost a couple of weeks ago the performance of my line is kinda bad (ticket DUU-647-86661) nothing has improved, port resets etc
I have two accounts with afrihost 2meg business uncapped and a 10 gb capped account (I have a 4 meg line so I was hoping to get full line speed on the capped account)
To quote my ticket
Nothing has changed, the tracert is basically the same and so are general pings to services. YouTube buffers like hell
I have gotten port reset after port reset
Line Stats : http://imgur.com/d91Mi5G
What I dont get is I have a high attainable rate but my line is worse than a fish right now. Speedtests dont even go to half my line speed
I have sent a lengthy ticket to Afrihost a couple of weeks ago the performance of my line is kinda bad (ticket DUU-647-86661) nothing has improved, port resets etc
I have two accounts with afrihost 2meg business uncapped and a 10 gb capped account (I have a 4 meg line so I was hoping to get full line speed on the capped account)
To quote my ticket
Nothing has changed, the tracert is basically the same and so are general pings to services. YouTube buffers like hell
I have gotten port reset after port reset
Line Stats : http://imgur.com/d91Mi5G
What I dont get is I have a high attainable rate but my line is worse than a fish right now. Speedtests dont even go to half my line speed
savage
Expert Member
I would argue foul on this. You said it yourself, "but rather the place just before getting onto the ISP's network." It would thus NOT ONLY be the line/exchange as you put it, but it DOES rightfully also include things like IPC, and IPC congestion.
This also is why allot of people on Afrihost has issues with 2nd hop latencies (and Afrihost puppets are quick to jump and say 'exchange'), but as soon as they use a different ISP (different IPC), then the 2nd hop latency is gone. All of a sudden it's not a exchange issue.
Chevron
Serial breaker of phones
Exactly. Starting to think Zertop wants a job at AH.
Yea, something is a bit fishy there
Line stats look good, but pings are off :/Have you tried reporting a fault and getting a technician over?
Z
I was personally under the impression that the IPC is much further along the trail. However, as I said, Im no expert. However, if there is an IPC issue, the second hop should still be perfect!
My reasoning was this for i.got~issues; he was showing 1000ms pings to both his second hops (Namely the MWEB and Afrihost one's). This proves that the issue ran over both the accounts. Thats why I mentioned a line fault
Im quite sure, however, that the second hop excludes the ISP, and is the connection between the exchange and the user. (well, I think i just contradicted what I said previously in the past sentence, but oh well).
While the exchange doesnt show up as a physical IP, it shows up in the form of the first ISP router. So when your line enters the exchange, it gets routed to the ISP it belongs to... if that makes sense.
Last edited:
Im good right now thanks
Im not just helping Afrihost people, but also other users too!
Last edited:
Hi Elbad
Our Business accounts are definitely not shaped.
Please PM me your account info and any tests you have available so that I can have a look at this and diagnose further.
savage
Expert Member
ADSL (your line) -> DSLAM (Telkom) -> BRAS (Telkom) -> ISP (IPC) -> Breakout (ISP's network, peering, transit, etc). -> The Internet
That's how I've been led to understand it. I have seen some very detailed documentation on this though - I just can't remember where. Will have to see if I can dig it out again somewhere.
The little grey box is called a DSLAM. Its pretty much the link between the Exchange and the User. The exchange is a physical building in a town where all the telkom lines come into. The "exchange" per se isn't shown, but rather is the middle link. The second hop of a tracert shows not the exchange, but rather the place just before getting onto the ISP's network.
Therefore - we can use it to calculate whether the problem lies with the ISP, or whether it lies with the line/exchange. Each ISP has a different "handler", which accounts for the different IP's
I could be wrong, because my knowledge on this isn't the greatest - but someone else should be able to tell you if that is correct
If this is the case, then the fact that Afrihost and MWEB are using different buildings, may not meant here's a problem with his line per say. If his line connects to MWEB's exchange fine, but not to Afrihosts, then does that not mean the problem is not with his line, but somewhere between the DSLAM and the Exchange?
In this case, there does seem to be an issue with his line, but it seems worse connecting to the Afrihost Exchange? If Telkom are called out, and the ping to the Telkom Exchange is fine, then who does the fault lie with?
Yea, thats the impression I had.
-> Router (Hop 1 in most cases)
-> ADSL (your line)
-> DSLAM (Telkom)
-> BRAS (Telkom) (Hop 2)
-> ISP (IPC) (Hop 3,4)
-> Breakout (ISP's network, peering, transit, etc). (Hop 5)
-> The Internet (Hop 6)
CrazYmonkeY159
Expert Member
Yea, something is a bit fishy there
Have you tried reporting a fault and getting a technician over?
Z
No I will go call tomorrow. I have had multiple port resets but thats it.
The exchange is one physical telkom building, and that is where the lines come in to be routed to the different ISP's. That's why when the exchange is congested, these route switches cannot take place fast enough, causing higher latencies.
Thats why It is impossible to tell whether the issue is with the line or with the exchange in one tracert
- Status