Web Squad ISP

[websquadza]

Hi Web Squad

Could I confirm that IPv6 is available on Openserve lines (the website says dual stack just would like to confirm)

Also when I click on order under the 100/50 tab it seems to try order a 10/5 service

Cheers

Evening, yes it is available with Dual Stack. I've asked our devs to sort out the order page. PM me your details and I'll ask the client team to reach out and sort you out.

 

[GoneWithTheWindows]

My line is completely dead?
JHB South.
Vuma Trenched.

 

[websquadza]

Joburg Clients: We are aware of an issue affecting the region. We are investigating

 

[DarkSt0rm]

Yeah totally dead, Randburg

 

[Zodiak]

Joburg Clients: We are aware of an issue affecting the region. We are investigating

Thank you, was wondering why my connection completely dead

 

[cobusv]

My internet is completely down whats going on?

 

[PsyWulf]

Joburg Clients: We are aware of an issue affecting the region. We are investigating

Thanks

 

[daelm]

My line is completely dead?
JHB South.
Vuma Trenched.

Me too

 

[daelm]

Joburg Clients: We are aware of an issue affecting the region. We are investigating

 

[websquadza]

Joburg update: our sincere apologies, we have localised the issue and we are working to resolve it asap.

 

[22Vanquish22]

Hi @websquadza,

Fibre is down in kempton park area (vumatel trenched).

I have raised a support ticket as well.

 

[BouncyNinja]

Our briefly went down, but back on again, springs , trenched

 

[SpiderGear]

Back online!

 

[abudabi]

4 mins to fix it.. not bad at all

 

[cobusv]

Joburg update: our sincere apologies, we have localised the issue and we are working to resolve it asap.

What is the issue?

 

[SNaidoo]

Came up for a few seconds then went down again

 

[BouncyNinja]

Down again too

 

[Looney]

Down again

 

[Zodiak]

Down again

 

[websquadza]

Joburg Update: Our apologies for that coffee break. We isolated the issue to a BGP error that was induced while configuring some new kit. Unfortunately a small internal route leak led to one of our core routers learning incorrect routes. While this was quickly resolved and the routes removed, this router took a little while to clear this information from its forwarding table. We'll escalate to the vendor to see why it took time to clear these routes and how we can avoid this happening in the future.