Web Squad ISP

Status
Not open for further replies.
Apologies for the delayed follow up here. We observed a path failure on our NLD between CPT and JHB- for some reason, reconvergence of routes took longer than expected, with a few stale advertisements between CPT and JHB remaining stubbornly in place for longer than they should've.

Speaking of which, any updates on the very low speeds between Cape Town and JHB:

Funny thing is, when I do 2 speedtests to JHB at the same time, the throughput gets close to doubling:

Screenshot 2021-03-17 202613.jpg
 
Update: We have picked up on an upstream international transit issue affecting one of our vendors, we are moving traffic over to an alternate path until this is resolved. Cape Town clients may experience increased latency during this period.

Any news on those additional/alternate routes for CPT?
 
Any news on those additional/alternate routes for CPT?

Hopefully in by the end of next week. Thanks for your patience on this one.

We also managed to pick up seacom and saix routes this week- so those should feel a little snappier.
 
Hopefully in by the end of next week. Thanks for your patience on this one.

We also managed to pick up seacom and saix routes this week- so those should feel a little snappier.

Sounds great, looking forward to it!
 
Are the routes to Europe via CT? I've noticed my CT mates have a ~20ms advantage when we play on EU servers...
 
For my education, is that the shortest path for all locations in SA?
I’d say Joburg is the most central with direct and protected paths to both Cape Town (16-22ms) and Durban (7-11ms).

Most other regions land up traversing one of these ‘core’ regions to reach content and servers everywhere else. There isn’t a reliable Durban to Cape Town route in play yet - which will even out the playing field a little more when it’s finally live.

South Africa’s internet is mostly centred around these three ‘core’ regions- Joburg, Cape Town and Durban. There are two peering exchanges in each of these regions which help to concentrate this. Most local Datacentres either house these exchanges (eg NAP at Teraco or JINX in the didata and liquid and also Teraco DCs) or want to be as close to these exchanges as possible, so most local servers/CDNs are in Joburg with some growing Cape Town and Durban presence of late.

The international players have also set up shop in Joburg mostly, with some in Cape Town. Some have expanded their presence into all 3 regions- which makes sense as data consumption continues to grow.
 
I’d say Joburg is the most central with direct and protected paths to both Cape Town (16-22ms) and Durban (7-11ms).

Most other regions land up traversing one of these ‘core’ regions to reach content and servers everywhere else. There isn’t a reliable Durban to Cape Town route in play yet - which will even out the playing field a little more when it’s finally live.

South Africa’s internet is mostly centred around these three ‘core’ regions- Joburg, Cape Town and Durban. There are two peering exchanges in each of these regions which help to concentrate this. Most local Datacentres either house these exchanges (eg NAP at Teraco or JINX in the didata and liquid and also Teraco DCs) or want to be as close to these exchanges as possible, so most local servers/CDNs are in Joburg with some growing Cape Town and Durban presence of late.

The international players have also set up shop in Joburg mostly, with some in Cape Town. Some have expanded their presence into all 3 regions- which makes sense as data consumption continues to grow.
Thanks for this. So then WACS is still the fastest for JINX?
 
Hopefully in by the end of next week. Thanks for your patience on this one.

We also managed to pick up seacom and saix routes this week- so those should feel a little snappier.
That's good news.

Once this issue is resolved it should improve things significantly for Cape Town users (on gigabit) seeing as most local stuff is hosted in JHB still.
 
Odd, this used to return 144ms:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   26 |   26 |    0 |    0 |    0 |    0 |
|             core.as-01.cp1.za.ws.net.za -    0 |   26 |   26 |    0 |    0 |    2 |    0 |
|             core.cr-01.cp1.za.ws.net.za -    0 |   26 |   26 |    0 |    0 |    1 |    0 |
|           165-69-148-197.as37497.za.net -    0 |   26 |   26 |    0 |    0 |    2 |    0 |
|             1-71-148-197.as37497.za.net -    0 |   26 |   26 |   17 |   17 |   22 |   17 |
|     41-79-249-245.static.pccwglobal.net -    0 |   26 |   26 |   18 |   18 |   19 |   18 |
|                            63.218.151.2 -    0 |   26 |   26 |   17 |   17 |   21 |   17 |
|   be2389.ccr22.lon01.atlas.cogentco.com -    0 |   26 |   26 |  210 |  210 |  211 |  210 |
|               be5.asr01.thn.as20860.net -    0 |   26 |   26 |  210 |  210 |  217 |  210 |
|              be10.asr01.dc5.as20860.net -    0 |   26 |   26 |  211 |  211 |  212 |  211 |
|             1717.g1.1ug.dc5.as20860.net -    0 |   26 |   26 |  196 |  198 |  205 |  200 |
|                          217.147.89.101 -    0 |   26 |   26 |  210 |  210 |  213 |  211 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Hi guys. I keep getting disconnected from the Blizzard/COD servers mid match. Not sure if this is a problem on their side or with my connection.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X