Afrihost New Network Feedback - Part 2

[kohlhtor]

I open a ticket 2 days no respond it is the same problem
In 2 years the support has not improved always blame telkom or the exchange

 

[AfriGuy]

I open a ticket 2 days no respond it is the same problem
In 2 years the support has not improved always blame telkom or the exchange

Sorry about that, is there a ref# I can take a look at for you?

 

[kohlhtor]

I send you yesterday a PM to check the Ticket you ask for

 

[AfriGuy]

I send you yesterday a PM to check the Ticket you ask for

Don't have a PM from you, did you perhaps send a PM to another one of the reps?

 

[kohlhtor]

Don't have a PM from you, did you perhaps send a PM to another one of the reps?

Sorry it was AfriGenie
GWV-785-39542

 

[AfriGuy]

Sorry it was AfriGenie
GWV-785-39542

Thanks. Looks like the ticket landed itself into the Lines queue. I've updated it to be in DSL Support and asked our team to attend ASAP.

 

[nan0s0ldier]

Our peering links are in order, I'm afraid we can't control traffic outside of our network.

so what would be the best course of action? Sorry i dont want to be a douche but I can fool around with this any longer. I play critical league games all week round.

 

[AfriGuy]

so what would be the best course of action? Sorry i dont want to be a douche but I can fool around with this any longer. I play critical league games all week round.

I believe we've had our network team run a few tests from our end and can't find any issues on our network. It's impossible for us to control traffic outside of our network, I can only recommend getting in touch with the destination hosts to see what can be done from their end.

 

[nan0s0ldier]

I believe we've had our network team run a few tests from our end and can't find any issues on our network. It's impossible for us to control traffic outside of our network, I can only recommend getting in touch with the destination hosts to see what can be done from their end.

so who would that be? Mweb?

 

[AfriGuy]

so who would that be? Mweb?

From the test you've posted it does look like it, yes.

 

[DreamKing]

Sorry about the delay here, Dreamking. Due to the high attenuation on your line this is proving to be a bit harder than anticipated. We're working on it!

will my line be fixed today?

or better to cancel the adsl to go for fibre?

 

[AfriGuy]

will my line be fixed today?

or better to cancel the adsl to go for fibre?

We won't be able to give you an ETR on your line fix, the second we hear anything we'll be in touch though

 

[kohlhtor]

Still packed loss and hi latency after living Afrihost Network

Every night the same problem

 

[AfriGenie]

Still packed loss and hi latency after living Afrihost Network

Every night the same problem

It looks like the Cloudflare setup is routing you a bit strangely. Are you seeing that sort of latency to any other sites?

 

[kohlhtor]

Yes

 

[AfriGenie]

Yes

Would you mind posting a traceroute to the affected sites or services.

 

[medicnick83]

My line is misbehaving...

Just a brief example;

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=290ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=56ms TTL=53
Reply from 8.8.8.8: bytes=32 time=59ms TTL=53
Reply from 8.8.8.8: bytes=32 time=70ms TTL=53
Reply from 8.8.8.8: bytes=32 time=418ms TTL=53
Reply from 8.8.8.8: bytes=32 time=198ms TTL=53
Reply from 8.8.8.8: bytes=32 time=317ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=270ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=258ms TTL=53
Reply from 8.8.8.8: bytes=32 time=259ms TTL=53
Reply from 8.8.8.8: bytes=32 time=257ms TTL=53
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=236ms TTL=53
Reply from 8.8.8.8: bytes=32 time=293ms TTL=53
Reply from 8.8.8.8: bytes=32 time=469ms TTL=53
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=428ms TTL=53
Reply from 8.8.8.8: bytes=32 time=246ms TTL=53
Reply from 8.8.8.8: bytes=32 time=257ms TTL=53
Reply from 8.8.8.8: bytes=32 time=229ms TTL=53
Reply from 8.8.8.8: bytes=32 time=268ms TTL=53
Reply from 8.8.8.8: bytes=32 time=263ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=321ms TTL=53
Reply from 8.8.8.8: bytes=32 time=271ms TTL=53
Reply from 8.8.8.8: bytes=32 time=298ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=292ms TTL=53
Reply from 8.8.8.8: bytes=32 time=285ms TTL=53
Reply from 8.8.8.8: bytes=32 time=411ms TTL=53
Reply from 8.8.8.8: bytes=32 time=259ms TTL=53

 

[JesseG]

I'm having some issues with my line.
One minute it's fine and the next it's super slow...
Youtube continually buffers, websites are slow to load, online gaming is horrendous...
I have to reboot or restart my router and then it's okay for about half an hour or so...
I have had telkom recreate my port as well Afrihost clear any line errors as well, no change...
Is anyone experiencing the same problem?

 

[Johnatan56]

I'm having some issues with my line.
One minute it's fine and the next it's super slow...
Youtube continually buffers, websites are slow to load, online gaming is horrendous...
I have to reboot or restart my router and then it's okay for about half an hour or so...
I have had telkom recreate my port as well Afrihost clear any line errors as well, no change...
Is anyone experiencing the same problem?

I am.

 

[AfriGuy]

My line is misbehaving...

Just a brief example;

-snip

Huge amounts of latency and packet loss here
Is there a traceroute I can check to see where the issues are creeping in?