Afrihost - Pure Fibre Feedback Thread

Status
Not open for further replies.
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 102 ms 98 ms 100 ms 165-73-14-17.ip.afrihost.co.za [165.73.14.17]
4 95 ms * 95 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
5 104 ms 103 ms 100 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
6 * 94 ms 97 ms cloudflare.ixp.joburg [196.60.8.198]
7 * 105 ms * one.one.one.one [1.1.1.1]
8 93 ms 92 ms 93 ms one.one.one.one [1.1.1.1]
 
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 102 ms 98 ms 100 ms 165-73-14-17.ip.afrihost.co.za [165.73.14.17]
4 95 ms * 95 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
5 104 ms 103 ms 100 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
6 * 94 ms 97 ms cloudflare.ixp.joburg [196.60.8.198]
7 * 105 ms * one.one.one.one [1.1.1.1]
8 93 ms 92 ms 93 ms one.one.one.one [1.1.1.1]

Looks like some sort of outage on Openserve.

Please drop me a pm with your email address let me ask Openserve if there is any issues.
 
Definitely something up with Openserve. Also in Centurion, getting around 1mbps on my 500mbps line, I've got a Cool Ideas account too with the same issue.
 
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 102 ms 98 ms 100 ms 165-73-14-17.ip.afrihost.co.za [165.73.14.17]
4 95 ms * 95 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
5 104 ms 103 ms 100 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
6 * 94 ms 97 ms cloudflare.ixp.joburg [196.60.8.198]
7 * 105 ms * one.one.one.one [1.1.1.1]
8 93 ms 92 ms 93 ms one.one.one.one [1.1.1.1]

I'm also running 3mbps on my 100mbps line on Openserve, in Centurion.
There is definitely a larger issue here.

Hi,

Openserve said there isn't any issue they are aware of and we should log these as normal.

Please can you drop me a pm with your email address so I can provide an Openserve test account and log the faults.
 
Same-ish area. I think there may be a larger outage.

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 102 ms 98 ms 100 ms 165-73-14-17.ip.afrihost.co.za [165.73.14.17]
4 95 ms * 95 ms 169-1-21-232.ip.afrihost.co.za [169.1.21.232]
5 104 ms 103 ms 100 ms 169-1-21-233.ip.afrihost.co.za [169.1.21.233]
6 * 94 ms 97 ms cloudflare.ixp.joburg [196.60.8.198]
7 * 105 ms * one.one.one.one [1.1.1.1]
8 93 ms 92 ms 93 ms one.one.one.one [1.1.1.1]

I'm also running 3mbps on my 100mbps line on Openserve, in Centurion.
There is definitely a larger issue here.


Please note the fault logged for Openserve Centurion.

Network Fault: 115BTK020622

Screenshot 2022-06-02 111954.png
 
My speed seems to be back to normal. Here's hoping everyone else got sorted too. :)

Thanks for all the help, AfriNatic, and for your quick response.
 
Strand FF still down, no connectivity all day.

Hi,

Unfortunately the outage is still ongoing.

Outage Update

Outage title: Outage | Western and Eastern Cape | EVPN Change Rollback | Change Overrun
Service Type: FTTB/FTTH
Outage ref (solid): FRG2780578
Impact start time: 2022-06-02 07:30
Impact: Down

Outage Update
2022-06-02
-- Our core team is currently in communication with the vendor to get the issues resolved as soon as possible.
-- Core and vendor teams still working towards resolution.
-- Frogfoot Core and vendor escalation points are actively troubleshooting the fault via a conference call to isolate the root cause.
-- Frogfoot Core and vendor escalation points are working on isolating the root cause for the clients that are still impacted.
-- No ETTR available yet.
-- Core and vendor teams discovered a possible software related fault.
-- Core team is collecting all relevant data requested by vendor teams.
-- This data will be sent to the vendor to analyze and in order to provide a permanent remedy.
-- Core team is investigating a possible workaround to restore the remaining impacted clients.
-- Core team is implementing a workaround to restore the remaining impacted clients.
-- Samples should start restoring shortly.
-- Update to follow once completed to request confirmation.
-- The workaround that the Core team implemented is not working as expected.
-- The Core team continues to work on alternatives to restore impacted clients.
-- Follow-up session with hardware vendor is scheduled for 15:00 to give feedback on the information provided earlier.
-- Update to follow once the session has been initiated and feedback received.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X