Afrihost - Pure Fibre Feedback Thread

yebocan · Apr 1, 2021

AfriNatic said:
Please map your new IP to your account via this link.

clientzone.afrihost.com/fibre-activate

Vumatel attach IP addresses to an order. Each service change is an order and that triggers a new IP to be allocated. Our system should trigger the afrihost fibre activate page but sometimes it does not.

Done ...still no joy...ips still not matching

vavyn · Apr 1, 2021

more results to uk.hosted.co.za
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter.Dlink - 77 | 51 | 12 | 0 | 0 | 0 | 0 |
| 165-73-56-1.ip.afrihost.joburg - 2 | 196 | 193 | 0 | 0 | 2 | 1 |
| 169-1-21-91.ip.afrihost.co.za - 1 | 203 | 202 | 0 | 0 | 6 | 1 |
| rtdcj-os-cer-1-wan.osnet.co.za - 2 | 195 | 192 | 2 | 3 | 13 | 4 |
| 10.189.30.2 - 3 | 193 | 189 | 167 | 167 | 173 | 167 |
| 195.66.226.25 - 3 | 189 | 184 | 203 | 251 | 270 | 262 |
| 138.197.251.141 - 4 | 185 | 179 | 195 | 248 | 270 | 260 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| eu.hosted.co.za - 5 | 175 | 167 | 203 | 250 | 265 | 207 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

AfriNatic · Apr 1, 2021

yebocan said:
Done ...still no joy...ips still not matching

Okay give it a few minutes and then restart both Vuma CPE and Router.

If you are still struggling you can try the new https://login.afrihost.com/activate.php which should map you instantly.

Mr Scratch · Apr 1, 2021

AfriNatic said:
Let me speak to our Network engineer. Looks like traffic is currently routed via France over EASSy.

ty, it's impacting all traffic going to UK/FR

AfriNatic · Apr 1, 2021

vavyn said:
more results to uk.hosted.co.za
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter.Dlink - 77 | 51 | 12 | 0 | 0 | 0 | 0 |
| 165-73-56-1.ip.afrihost.joburg - 2 | 196 | 193 | 0 | 0 | 2 | 1 |
| 169-1-21-91.ip.afrihost.co.za - 1 | 203 | 202 | 0 | 0 | 6 | 1 |
| rtdcj-os-cer-1-wan.osnet.co.za - 2 | 195 | 192 | 2 | 3 | 13 | 4 |
| 10.189.30.2 - 3 | 193 | 189 | 167 | 167 | 173 | 167 |
| 195.66.226.25 - 3 | 189 | 184 | 203 | 251 | 270 | 262 |
| 138.197.251.141 - 4 | 185 | 179 | 195 | 248 | 270 | 260 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| eu.hosted.co.za - 5 | 175 | 167 | 203 | 250 | 265 | 207 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

There is an issue confirmed with our transit to the UK.

We are investigating and have logged it with our upstream provider.

AfriNatic · Apr 1, 2021

Mr Scratch said:
ty, it's impacting all traffic going to UK/FR

There is an issue confirmed with our transit to the UK.

We are investigating and have logged it with our upstream provider.

Mr Scratch · Apr 1, 2021

AfriNatic said:
There is an issue confirmed with our transit to the UK.

We are investigating and have logged it with our upstream provider.

If it at all helps this started at 07:01am Wednesday morning

Mr Scratch · Apr 1, 2021

(downtime was the probe not the connection)

Mr Scratch · Apr 1, 2021

Looking good

Seems to have returned to baseline

Mr Scratch · Apr 1, 2021

Deckert · Apr 1, 2021

Anybody else that went from the old 20Mbit to the new 25Mbit packages not actually getting 25Mbit?

I used to be on the 20Mbit package, got 20Mbit/s with speed tests.
Now I have "downgraded" to the new 25Mbit package, still getting exactly 20Mbit/s.

--deckert

Rickster · Apr 1, 2021

@AfriNatic was having major drop outs then realised the package downgraded is done at midnight.

Code:

Pinging 1.1.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=7ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=4ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=3ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=3ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=5ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=3ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=5ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=370ms TTL=57
Reply from 1.1.1.1: bytes=32 time=17ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=57
Reply from 1.1.1.1: bytes=32 time=2ms TTL=58

Ping statistics for 1.1.1.1:
    Packets: Sent = 232, Received = 197, Lost = 35 (15% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 370ms, Average = 4ms

Rebooted router and ONT, seems fine now, is this normal?

Rickster · Apr 1, 2021

Im now getting that Afrihost login page on my wireless devices.

Rickster · Apr 1, 2021

AfriNatic said:
Please map your new IP to your account via this link.

clientzone.afrihost.com/fibre-activate

Vumatel attach IP addresses to an order. Each service change is an order and that triggers a new IP to be allocated. Our system should trigger the afrihost fibre activate page but sometimes it does not.

This sorted it thanks, you really should have a notice on your website about this, lol.

AfriNatic · Apr 1, 2021

Deckert said:
Anybody else that went from the old 20Mbit to the new 25Mbit packages not actually getting 25Mbit?

I used to be on the 20Mbit package, got 20Mbit/s with speed tests.
Now I have "downgraded" to the new 25Mbit package, still getting exactly 20Mbit/s.

--deckert

Can you send me your clientzone email address so I can have a look for you?

Deckert · Apr 1, 2021

AfriNatic said:
Can you send me your clientzone email address so I can have a look for you?

Thank you for checking and resolving. Now working perfectly at the expected speeds.
Satisfied customer.

--deckert

yebocan · Apr 1, 2021

Big thanks to @AfriNatic for sorting me out. Your support is top notch, thanks again!!

Mr Scratch · Apr 1, 2021

I'm certainly not the only one experiencing such?

Mr Scratch · Apr 1, 2021

the Netflix time pattern tells me theres issues, am I wrong?

Mr Scratch · Apr 1, 2021

AWS over what looks to be their direct connect is fine

Join the MyBroadband community

Get started

Afrihost - Pure Fibre Feedback Thread

Honorary Master

Senior Member

Afrihost Rep

Expert Member

Afrihost Rep

Afrihost Rep

Expert Member

Expert Member

Expert Member

Expert Member

Well-Known Member

EVGA Fanatic

EVGA Fanatic

EVGA Fanatic

Afrihost Rep

Well-Known Member

Honorary Master

Expert Member

Expert Member

Expert Member