Afrihost New Network Feedback - Part 2

[krustyrsa]

Will do!

soz I meant Afriguy, but maybe you can help, I will forward you the PM

 

[LaraC]

No change.

 

[LaraC]

YouTube flawless.



https://www.youtube.com/watch?v=pvI9PuGorwI

 

[AfriGuy]

soz I meant Afriguy, but maybe you can help, I will forward you the PM

I'm not officially here
Just replied to your PM.

 

[LaraC]

I'm not officially here
Just replied to your PM.

No problem, we'll ask you unofficially too.

 

[Hummercellc]

Does anyone know if a port refresh/recreate forces AISSA to regrade your line?

 

[Johnatan56]

Does anyone know if a port refresh/recreate forces AISSA to regrade your line?

It might change the line stats which could results in ASSIA upping the line stats, but it would probably be temporary as the underlying issue would still persist.

 

[Hummercellc]

It might change the line stats which could results in ASSIA upping the line stats, but it would probably be temporary as the underlying issue would still persist.

Why i ask is i have one line syncing just shy of 20meg and it has far better line stats than my other lines syncing at 24meg. Weird.

 

[Johnatan56]

Why i ask is i have one line syncing just shy of 20meg and it has far better line stats than my other lines syncing at 24meg. Weird.

Probably a line/port issue then, ask an Afripep to check your line and see if anything comes up.
Or is one ADSL and the other VDSL?

 

[Hummercellc]

Probably a line/port issue then, ask an Afripep to check your line and see if anything comes up.
Or is one ADSL and the other VDSL?

All ADSL, no MSAN here, I wish.

 

[AfriGuy]

Does anyone know if a port refresh/recreate forces AISSA to regrade your line?

Shouldn't do.
ASSIA monitors the line for drops and isn't directly linked to port resets. If ASSIA picks up line/ port related drops it may intervene though.

 

[AfriGuy]

No problem, we'll ask you unofficially too.

 

[Masik3R]

No worries
Was it just 169.1.5.128 where you saw an issue?

Its both 169.1.5.128 and 169.1.5.82 that I'm guessing are congested during the evening. Don't touch any local gaming on my Afrihost account in the evenings...

169.1.5.128:

C:\Users\Ryan>ping -n 30 169.1.5.128

Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=71ms TTL=60
Reply from 169.1.5.128: bytes=32 time=68ms TTL=60
Reply from 169.1.5.128: bytes=32 time=80ms TTL=60
Reply from 169.1.5.128: bytes=32 time=27ms TTL=60
Reply from 169.1.5.128: bytes=32 time=59ms TTL=60
Reply from 169.1.5.128: bytes=32 time=71ms TTL=60
Reply from 169.1.5.128: bytes=32 time=31ms TTL=60
Reply from 169.1.5.128: bytes=32 time=50ms TTL=60
Request timed out.
Reply from 169.1.5.128: bytes=32 time=27ms TTL=60
Reply from 169.1.5.128: bytes=32 time=42ms TTL=60
Reply from 169.1.5.128: bytes=32 time=78ms TTL=60
Reply from 169.1.5.128: bytes=32 time=76ms TTL=60
Reply from 169.1.5.128: bytes=32 time=27ms TTL=60
Reply from 169.1.5.128: bytes=32 time=58ms TTL=60
Reply from 169.1.5.128: bytes=32 time=33ms TTL=60
Reply from 169.1.5.128: bytes=32 time=78ms TTL=60
Request timed out.
Reply from 169.1.5.128: bytes=32 time=42ms TTL=60
Reply from 169.1.5.128: bytes=32 time=55ms TTL=60
Reply from 169.1.5.128: bytes=32 time=69ms TTL=60
Reply from 169.1.5.128: bytes=32 time=29ms TTL=60
Reply from 169.1.5.128: bytes=32 time=36ms TTL=60
Reply from 169.1.5.128: bytes=32 time=38ms TTL=60
Reply from 169.1.5.128: bytes=32 time=41ms TTL=60
Reply from 169.1.5.128: bytes=32 time=29ms TTL=60
Reply from 169.1.5.128: bytes=32 time=28ms TTL=60
Reply from 169.1.5.128: bytes=32 time=38ms TTL=60
Reply from 169.1.5.128: bytes=32 time=109ms TTL=60
Reply from 169.1.5.128: bytes=32 time=43ms TTL=60

Ping statistics for 169.1.5.128:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 27ms, Maximum = 109ms, Average = 51ms

169.1.5.82:

C:\Users\Ryan>ping -n 30 169.1.5.82

Pinging 169.1.5.82 with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=37ms TTL=59
Reply from 169.1.5.82: bytes=32 time=63ms TTL=59
Reply from 169.1.5.82: bytes=32 time=73ms TTL=59
Reply from 169.1.5.82: bytes=32 time=88ms TTL=59
Reply from 169.1.5.82: bytes=32 time=37ms TTL=59
Reply from 169.1.5.82: bytes=32 time=34ms TTL=59
Reply from 169.1.5.82: bytes=32 time=35ms TTL=59
Reply from 169.1.5.82: bytes=32 time=43ms TTL=59
Reply from 169.1.5.82: bytes=32 time=95ms TTL=59
Reply from 169.1.5.82: bytes=32 time=68ms TTL=59
Reply from 169.1.5.82: bytes=32 time=34ms TTL=59
Reply from 169.1.5.82: bytes=32 time=37ms TTL=59
Reply from 169.1.5.82: bytes=32 time=33ms TTL=59
Reply from 169.1.5.82: bytes=32 time=62ms TTL=59
Reply from 169.1.5.82: bytes=32 time=39ms TTL=59
Reply from 169.1.5.82: bytes=32 time=34ms TTL=59
Reply from 169.1.5.82: bytes=32 time=41ms TTL=59
Reply from 169.1.5.82: bytes=32 time=69ms TTL=59
Reply from 169.1.5.82: bytes=32 time=94ms TTL=59
Reply from 169.1.5.82: bytes=32 time=120ms TTL=59
Reply from 169.1.5.82: bytes=32 time=56ms TTL=59
Reply from 169.1.5.82: bytes=32 time=95ms TTL=59
Reply from 169.1.5.82: bytes=32 time=112ms TTL=59
Reply from 169.1.5.82: bytes=32 time=53ms TTL=59
Reply from 169.1.5.82: bytes=32 time=100ms TTL=59
Reply from 169.1.5.82: bytes=32 time=106ms TTL=59
Reply from 169.1.5.82: bytes=32 time=101ms TTL=59
Reply from 169.1.5.82: bytes=32 time=58ms TTL=59
Reply from 169.1.5.82: bytes=32 time=82ms TTL=59
Reply from 169.1.5.82: bytes=32 time=68ms TTL=59

Ping statistics for 169.1.5.82:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 120ms, Average = 65ms

bras:

C:\Users\Ryan>ping -n 30 bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63

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

Edit: Just to add, this happens every single night without fail and has been for the last 2 months at least. It definitely isn't an isolated issue that only affects certain customers in the Cape, they just aren't aware it's happening. I wouldn't even notice if I didn't game as every other service I use is on point even when these routers are playing up. Downloads fly 24/7 and streaming is pretty good so keep that up

EDIT 2: For e.g, Doesn't effect a speed test result.

 

[AfriGuy]

Its both 169.1.5.128 and 169.1.5.82 that I'm guessing are congested during the evening. Don't touch any local gaming on my Afrihost account in the evenings...

-snip
Edit: Just to add, this happens every single night without fail and has been for the last 2 months at least. It definitely isn't an isolated issue that only affects certain customers in the Cape, they just aren't aware it's happening. I wouldn't even notice if I didn't game as every other service I use is on point even when these routers are playing up. Downloads fly 24/7 and streaming is pretty good so keep that up

EDIT 2: For e.g, Doesn't effect a speed test result.
View attachment 382709

Thanks for posting these results. I don't have 169.1.5.82 setup on monitoring but my other IPC hops looked solid last night.
Not sure if this would be a backhaul issue, I see you're in PE.

Drop me a PM with your DSL username and I'll see if I can find anything.

Here are the results from my home connection last night. ignore the latency spikes - various downloads/ updates.

 

[Icemanbrfc]

YouTube flawless.

View attachment 382655

https://www.youtube.com/watch?v=pvI9PuGorwI

Well lately i have no issues as well. Probably because ive secretly become your neighbour

 

[AfriGuy]

Well lately i have no issues as well. Probably because ive secretly become your neighbour

Haha!!
Change all the passwords, Lara

 

[Icemanbrfc]

Haha!!
Change all the passwords, Lara

no dont Lara.

 

[LaraC]

Well lately i have no issues as well. Probably because ive secretly become your neighbour

In that case, welcome to the neighbourhood where surfing is always cool.

 

[LaraC]

Haha!!
Change all the passwords, Lara

Thanks, I'll put Iceman's account on ice.

 

[Icemanbrfc]

In that case, welcome to the neighbourhood where surfing is always cool.