Web sQuad ISP - Feedback Thread #2

websquadza said:
Route looks fairly clean. Looks like the Equiano route is in play (+- 134ms from CPT to marseilles) and on via Paris. Will take a look and see if we can steer this in a different direction this side.




Any kind of IP or trace would really help narrow this down. Transit paths are congestion free, plenty of spare capacity with WACS back in the mix. Wondering if it's not a funky return path issue. @Zodiak weird you mention Youtube, nothing being offloaded to transit and no issues peering side. Will dig a little deeper.
Click to expand...

It’s weird , it’s worse in the evenings, but random international drops , barring the supplied mtr , anything else I can try running to help troubleshoot?
 
ijacobs3 said:
It’s weird , it’s worse in the evenings, but random international drops , barring the supplied mtr , anything else I can try running to help troubleshoot?
Click to expand...
We made some small changes last night. Let me know if you notice any improvement today?
 
websquadza said:
Thanks for your patience here, please check on this and let me know if your changes worked.
Click to expand...
It works for me, thanks!

# traceroute6 -Il websquad.co.za
traceroute6 to websquad.co.za (2c0f:f030:6040:2::75) from 2c0f:f030:201:401:dd:e7ff:fef7:850a, 64 hops max, 20 byte packets
1 2c0f:f030::1000:402 (2c0f:f030::1000:402) 3.895 ms 3.827 ms 4.575 ms
2 core.cr-01.jb1.za.ws.net.za (2c0f:f030::1000:101) 4.392 ms 3.961 ms 3.779 ms
3 core.cr-xe-01.jnb.za.ws.net.za (2c0f:f030:6000::301) 5.257 ms 4.967 ms 4.790 ms
4 core.as-01.jnb.za.ws.net.za (2c0f:f030:6000::151) 5.159 ms 5.093 ms 4.926 ms
5 2c0f:f030:6040:2::75 (2c0f:f030:6040:2::75) 7.051 ms 5.309 ms 5.158 ms
 
JohnHay said:
It works for me, thanks!

# traceroute6 -Il websquad.co.za
traceroute6 to websquad.co.za (2c0f:f030:6040:2::75) from 2c0f:f030:201:401:dd:e7ff:fef7:850a, 64 hops max, 20 byte packets
1 2c0f:f030::1000:402 (2c0f:f030::1000:402) 3.895 ms 3.827 ms 4.575 ms
2 core.cr-01.jb1.za.ws.net.za (2c0f:f030::1000:101) 4.392 ms 3.961 ms 3.779 ms
3 core.cr-xe-01.jnb.za.ws.net.za (2c0f:f030:6000::301) 5.257 ms 4.967 ms 4.790 ms
4 core.as-01.jnb.za.ws.net.za (2c0f:f030:6000::151) 5.159 ms 5.093 ms 4.926 ms
5 2c0f:f030:6040:2::75 (2c0f:f030:6040:2::75) 7.051 ms 5.309 ms 5.158 ms
Click to expand...
As an extra plus, my previous complaint that certain IPv6 traffic to the SANReN/TENET network that were routed from Gauteng via Cape Town and then back to Gauteng, has also been fixed after these changes. :-)
 
Hi any idea whats going on with Vuma connectivity in Durban?

Code: 
Tracing route to 1.1.1.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    <1 ms    <1 ms    <1 ms  160.119.237.245
  4  160.119.237.245  reports: Destination host unreachable.
 
Anyone else on FF in PTA got a network hard down? I have an IP address but no connectivity
 
ijacobs3 said:
Evening

Every evening now, we keep getting disconnected from random game servers in the EU, multiple ones, tonight i managed to grab a mtr, but this happens every evening, not just to one

View attachment 1704607
Click to expand...
Zodiak said:
I've also noticed terrible packet loss and rubber banding when gaming on EU servers lately, funny enough US East servers are more stable with higher ping, something hasn't been right with international connectivity for over a week now. Also noticed degraded YouTube performance today, buffering earlier
Click to expand...
How's this been looking of late?
 
@websquadza - are there any changes in the pipeline around fixing the picking up of FF in CPT vs JHB?
 
Octotel Network Notice | Service Disruption: Melkbos, Blouberg, Kensington | 22 May 2024
Investigating
May 22, 2024 at 7:34 AM
Dear ISP Partner,
We are observing an issue affecting services at the following aggregation nodes:
Melkbos
Blouberg
Kensington
Engineers are currently investigating.
Kindly await further updates.
Regards,
Octotel NOC
 
ctriaan said:
Octotel Network Notice | Service Disruption: Melkbos, Blouberg, Kensington | 22 May 2024
Investigating
May 22, 2024 at 7:34 AM
Dear ISP Partner,
We are observing an issue affecting services at the following aggregation nodes:
Melkbos
Blouberg
Kensington
Engineers are currently investigating.
Kindly await further updates.
Regards,
Octotel NOC
Click to expand...
It looks like it was self-inflicted.

Octotel Network Notice | Routine Software Maintenance: Blouberg, Melkbos, Kensington, Seapoin, Vredehoek, Mutual, Ruyterwacht, GreenPoint, Bree | 22 May 2024
Completed
May 22, 2024 at 5:00 AM
Maintenance has completed successfully
In progress
May 22, 2024 at 2:00 AM
Maintenance is now in progress
Planned
May 22, 2024 at 2:00 AM
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X