Web Squad ISP

Status
Not open for further replies.
websquadza said:
Still down? No outages our side. Seeing a minor NWI for Glenhazel on Vuma status board which is still active since yesterday. You can also email [email protected]. What mobile network you on? Not seeing any issues on the site from Vodacom and MTN? Can’t test the other two unfortunately.
Click to expand...

Clearly you guys are not getting correct info:

*Vumatel Update - Glenhazel/Sandringham and Surrounds*

Technicians have Started repair on Fibre Uplink at 39 Long Avenue, having to repair 566 individual Fibre cables, cut by City Parks and Recreation whilst trimming trees.

Estimated completion time 22h00.

Generator and Halogen lights being brought in to ensure work continues during Loadsheding.

When Uplink is repaired they will move to Lyndhurst Road to repair Fibre Downkink, also damaged by City Parks and Recreation, which will bring up Lyndhurst Road and the balance of Sandringham and surrounding areas.

ETA on total repair around 00h00

Hope this helps and I will keep you updated on progress.

CAP have been asked to do extra Patrols to safeguard the Technicians particularly during Loadsheding from 18h00 to 20h30

Any residents who are able to assist with Coffee/Soup and Sandwiches for the Technicians would be greatly appreciated.

There are 10 Technicians on site.
 
Looney said:
Clearly you guys are not getting correct info:

*Vumatel Update - Glenhazel/Sandringham and Surrounds*

Technicians have Started repair on Fibre Uplink at 39 Long Avenue, having to repair 566 individual Fibre cables, cut by City Parks and Recreation whilst trimming trees.

Estimated completion time 22h00.

Generator and Halogen lights being brought in to ensure work continues during Loadsheding.

When Uplink is repaired they will move to Lyndhurst Road to repair Fibre Downkink, also damaged by City Parks and Recreation, which will bring up Lyndhurst Road and the balance of Sandringham and surrounding areas.

ETA on total repair around 00h00

Hope this helps and I will keep you updated on progress.

CAP have been asked to do extra Patrols to safeguard the Technicians particularly during Loadsheding from 18h00 to 20h30

Any residents who are able to assist with Coffee/Soup and Sandwiches for the Technicians would be greatly appreciated.

There are 10 Technicians on site.
Click to expand...
We see the update - there were two separate NWIs linked to this outage - they have recently been merged.
 
darrencon said:
Hi. Anyone else's internet in Northriding down?
Click to expand...
Evotel Network Maintenance - 10 June 2023 23:00 to 11 June 2023 02:00. Please be aware of the maintenance times. Minimal disruptions can be expected.

Guessing it’s related
 
semaphore said:
Evotel Network Maintenance - 10 June 2023 23:00 to 11 June 2023 02:00. Please be aware of the maintenance times. Minimal disruptions can be expected.

Guessing it’s related
Click to expand...
up and running again when I woke up this morning
 
It could have been my router giving issues. Have rebooted and things are working again. Youtube was buffering, MyBB was taking over 30 seconds to load.

Very strange things this afternoon.

Will monitor and log a ticket if I pick anything up

:)
 
It looks like your Durban NAPAfrica router does not know how to route IPv6 back to at least some of your network.

Here is a traceroute6 from outside:
traceroute6 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 traceroute6 to 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 (2c0f:f030:20a:3fc1:230:18ff:fecd:7343) from 2001:4200:7000:ffff:ffff:ffff:ffff:f001, 64 hops max, 28 byte packets 1 pta1-pe1.sanren.ac.za 0.325 ms 0.288 ms 0.388 ms 2 et-1-1-0-0-mtz1-ir1.net.tenet.ac.za 7.800 ms 7.761 ms 7.832 ms 3 et-0-1-0-0-dur3-pe1.net.tenet.ac.za 11.721 ms 9.404 ms 9.592 ms 4 lt-0-1-0-1-dur3-pe1.net.tenet.ac.za 9.448 ms lt-1-1-0-1-dur3-pe1.net.tenet.ac.za 27.109 ms lt-0-1-0-1-dur3-pe1.net.tenet.ac.za 9.439 ms 5 2001:43f8:6d2::37 9.285 ms 9.328 ms * 6 2001:43f8:6d2::37 1258.140 ms !A 3119.384 ms !A 3119.993 ms !A

A ping from the last TENET router, also fails:

ping logical-system DUR3-PR1 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 PING6(56=40+8+8 bytes) 2001:43f8:6d2::216 --> 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 64 bytes from 2001:43f8:6d2::37: Destination Host Unreachable Vr TC Flow Plen Nxt Hlim 6 00 00000 0010 3a 3f 2001:43f8:6d2::216->2c0f:f030:20a:3fc1:230:18ff:fecd:7343 ICMP6: type = 128, code = 0
 
JohnHay said:
It looks like your Durban NAPAfrica router does not know how to route IPv6 back to at least some of your network.

Here is a traceroute6 from outside:
traceroute6 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 traceroute6 to 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 (2c0f:f030:20a:3fc1:230:18ff:fecd:7343) from 2001:4200:7000:ffff:ffff:ffff:ffff:f001, 64 hops max, 28 byte packets 1 pta1-pe1.sanren.ac.za 0.325 ms 0.288 ms 0.388 ms 2 et-1-1-0-0-mtz1-ir1.net.tenet.ac.za 7.800 ms 7.761 ms 7.832 ms 3 et-0-1-0-0-dur3-pe1.net.tenet.ac.za 11.721 ms 9.404 ms 9.592 ms 4 lt-0-1-0-1-dur3-pe1.net.tenet.ac.za 9.448 ms lt-1-1-0-1-dur3-pe1.net.tenet.ac.za 27.109 ms lt-0-1-0-1-dur3-pe1.net.tenet.ac.za 9.439 ms 5 2001:43f8:6d2::37 9.285 ms 9.328 ms * 6 2001:43f8:6d2::37 1258.140 ms !A 3119.384 ms !A 3119.993 ms !A

A ping from the last TENET router, also fails:

ping logical-system DUR3-PR1 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 PING6(56=40+8+8 bytes) 2001:43f8:6d2::216 --> 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 64 bytes from 2001:43f8:6d2::37: Destination Host Unreachable Vr TC Flow Plen Nxt Hlim 6 00 00000 0010 3a 3f 2001:43f8:6d2::216->2c0f:f030:20a:3fc1:230:18ff:fecd:7343 ICMP6: type = 128, code = 0
Click to expand...
Thanks, will get the guys to look at this quickly
 
been having issues regarding connection between my work (Websquad) and home (Telkom) account that will result in latency of about 200ms. Looks like a peering issue between telkom and WebSquad. I've tested at home with another account from a different isp and it works them my ping is max 20ms.
 
nelis said:
been having issues regarding connection between my work (Websquad) and home (Telkom) account that will result in latency of about 200ms. Looks like a peering issue between telkom and WebSquad. I've tested at home with another account from a different isp and it works them my ping is max 20ms.
Click to expand...
Telkom don't peer openly locally (like seacom), putting them firmly in the 90s in terms of network policy. That said, we have two upstream paths to telkom locally. As per your PM; the issue is telkom trying to offload traffic to HE locally (ironic given that they don't want ISPs reaching them freely, that they prefer free local routes to HE over their own clients and peers).
 
websquadza said:
Telkom don't peer openly locally (like seacom), putting them firmly in the 90s in terms of network policy. That said, we have two upstream paths to telkom locally. As per your PM; the issue is telkom trying to offload traffic to HE locally (ironic given that they don't want ISPs reaching them freely, that they prefer free local routes to HE over their own clients and peers).
Click to expand...

Telkom: we don't peer freely with ISPs in SA because of abuse.

HE: here is a bunch of routes to all our international customers in 3 free locations in CPT, DUR and JHB and we will even use our own transit between these locations so you don't have to pay.

Telkom: yes we accept this kind of free peering....
 
websquadza said:
Telkom don't peer openly locally (like seacom), putting them firmly in the 90s in terms of network policy. That said, we have two upstream paths to telkom locally. As per your PM; the issue is telkom trying to offload traffic to HE locally (ironic given that they don't want ISPs reaching them freely, that they prefer free local routes to HE over their own clients and peers).
Click to expand...
Gives me one more reason to ditch Telkom and then they wonder why they are failing
 
JohnHay said:
It looks like your Durban NAPAfrica router does not know how to route IPv6 back to at least some of your network.

Here is a traceroute6 from outside:
traceroute6 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 traceroute6 to 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 (2c0f:f030:20a:3fc1:230:18ff:fecd:7343) from 2001:4200:7000:ffff:ffff:ffff:ffff:f001, 64 hops max, 28 byte packets 1 pta1-pe1.sanren.ac.za 0.325 ms 0.288 ms 0.388 ms 2 et-1-1-0-0-mtz1-ir1.net.tenet.ac.za 7.800 ms 7.761 ms 7.832 ms 3 et-0-1-0-0-dur3-pe1.net.tenet.ac.za 11.721 ms 9.404 ms 9.592 ms 4 lt-0-1-0-1-dur3-pe1.net.tenet.ac.za 9.448 ms lt-1-1-0-1-dur3-pe1.net.tenet.ac.za 27.109 ms lt-0-1-0-1-dur3-pe1.net.tenet.ac.za 9.439 ms 5 2001:43f8:6d2::37 9.285 ms 9.328 ms * 6 2001:43f8:6d2::37 1258.140 ms !A 3119.384 ms !A 3119.993 ms !A

A ping from the last TENET router, also fails:

ping logical-system DUR3-PR1 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 PING6(56=40+8+8 bytes) 2001:43f8:6d2::216 --> 2c0f:f030:20a:3fc1:230:18ff:fecd:7343 64 bytes from 2001:43f8:6d2::37: Destination Host Unreachable Vr TC Flow Plen Nxt Hlim 6 00 00000 0010 3a 3f 2001:43f8:6d2::216->2c0f:f030:20a:3fc1:230:18ff:fecd:7343 ICMP6: type = 128, code = 0
Click to expand...
Dropped you a PM
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X