Web Squad ISP

Status
Not open for further replies.
@websquadza Happening again..
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 45 | 45 | 0 | 0 | 0 | 0 |
| as-vuma.jb-gv.za.ws.net.za - 0 | 45 | 45 | 1 | 2 | 28 | 2 |
| core.vuma-l3.jb1.za.ws.net.za - 0 | 45 | 45 | 2 | 11 | 142 | 3 |
| core.as-xe-02.jb1.za.ws.net.za - 0 | 45 | 45 | 1 | 1 | 2 | 1 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 45 | 45 | 1 | 1 | 3 | 1 |
| core.pe-xe-ip01.jb1.za.ws.net.za - 0 | 45 | 45 | 1 | 1 | 2 | 1 |
| 165-65-148-197.as37497.za.net - 0 | 45 | 45 | 1 | 1 | 3 | 1 |
| 161-64-148-197.as37497.za.net - 6 | 37 | 35 | 1 | 3 | 52 | 1 |
| 41-79-249-245.static.pccwglobal.net - 6 | 37 | 35 | 2 | 2 | 19 | 2 |
| HundredGE0-3-0-0.br01.ldn04.pccwbtn.net - 6 | 37 | 35 | 54 | 155 | 162 | 159 |
| 63.218.243.58 - 10 | 33 | 30 | 159 | 159 | 163 | 163 |
| ae-11.r21.londen12.uk.bb.gin.ntt.net - 10 | 30 | 27 | 159 | 161 | 169 | 161 |
| ae-1.r03.londen05.uk.bb.gin.ntt.net - 10 | 30 | 27 | 159 | 159 | 161 | 159 |
| 81.25.207.86 - 50 | 14 | 7 | 160 | 168 | 187 | 170 |
| 104.20.9.169 - 10 | 30 | 27 | 158 | 159 | 162 | 159 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

@websquadza

Something wrong with my interwebs.

Also international looks to be dead?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 11 | 11 | 0 | 0 | 0 | 0 |
| as-vuma.jb-gv.za.ws.net.za - 0 | 11 | 11 | 1 | 5 | 25 | 2 |
| core.vuma-l3.jb1.za.ws.net.za - 15 | 7 | 6 | 0 | 5 | 17 | 2 |
| core.as-xe-02.jb1.za.ws.net.za - 0 | 11 | 11 | 1 | 1 | 2 | 1 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 11 | 11 | 1 | 1 | 4 | 3 |
| core.pe-xe-ip01.jb1.za.ws.net.za - 0 | 8 | 8 | 1 | 1 | 6 | 6 |
| 165-65-148-197.as37497.za.net - 0 | 11 | 11 | 1 | 5 | 15 | 12 |
| 6-71-148-197.as37497.za.net - 0 | 9 | 9 | 19 | 22 | 33 | 28 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Looks like the WACS route is flapping - upstreams are on it, I think they're going to dampen until resolved.
 
Is this resolved?
Still seeing strange routing, mybroadband for instance is fine 20ms, but carbonite is 165ms.
Also international feeling a little slow.

I think Cloudflare turned down some prefixes and services in SA today. Saw reports of 1.1.1.1 jumping to JHB at some point. Carbonite traces through cloudflare's transit via CPT. Can't really comment on Cloudflare's routing decisions - but two flaps on WACS (their primary route) in one day, would maybe make them turn down some services until they're sure things are stable

With regards to transit, upstreams are monitoring the WACS circuit and there is some work going on in the background. Will chat to them now to get a better feel for their progress.
 
Is this kind of speedtest "ok" on a 1Gbps line?

View attachment 914265

Try a server we don't pick up through peering (IE, SA ISPs' own servers in the UK) - this is more a sign of the peer's transit than ours (the peer carries this traffic to and from London and hands over to us on NAP). Our London speedtest server is hosted on Digital Ocean (a reputable cloud provider with a pretty good network). You can use our test (speedtest.lon.websquad.co.za) -we use this to monitor if our upstreams are having peering issues in London. Or Speedtest.net coreix is pretty reliable.

Edit: Could also be packet loss on your line - i see you are on GPON, so we can't test to the Vuma handover and a low ms test won't make much of a difference anyway. Test a Cape Town and a Durban server (download the speedtest.net app) and see if there's any significant degradation in performance there.

Edit 2: Picking up on some upstream issues - will confirm further. But above for other ISPs international servers still applies.
 
Last edited:
Definitely something wrong with international. I’m actually starting to get sick and tired of this. I’m paying for a 1gb line and I never get 1gb speeds.

3e401c2170708aa22ea8385e87ffd167.jpg
 
Is this kind of speedtest "ok" on a 1Gbps line?

View attachment 914265


Definitely something wrong with international. I’m actually starting to get sick and tired of this. I’m paying for a 1gb line and I never get 1gb speeds.

3e401c2170708aa22ea8385e87ffd167.jpg

We're escalating to our upstreams - also seeing a drop over the last few mins. Some test destinations are good, but others not so much.
 
speedtest server is hosted on Digital Ocean (a reputable cloud provider with a pretty good network). You can use our test (speedtest.lon.websquad.co.za) -we use this to monitor if our upstreams are having peering issues in London. Or Speedtest.net coreix is pretty reliable.

@websquadza
What is the id for speedtest.lon.websquad.co.za as it is not listed on `speedtest-cli --list`
 
International Transit Notification:
One of our upstream providers has picked up on an issue and will be conducting Emergency maintenance on their WACS path tomorrow:
Date: 17 September 2020
Time: SAST 09:00 - 12:00

We will steer traffic via our other transit providers during this time - there remains a risk of elevated latency as some traffic may route via the East Coast.
 
Transit Update: WACS have started maintenance on the affected ports. Please expect elevated latencies as some routes are moved around.
 
Transit Update: WACS have started maintenance on the affected ports. Please expect elevated latencies as some routes are moved around.

Damn you're not kidding. I didn't realise "elevated" meant +100ms :)
 
Damn you're not kidding. I didn't realise "elevated" meant +100ms :)

Yeah, we've brought on some additional routes to compensate for the downtime - however, the East coast paths are a) longer routes (Both physically and that they land in Marseilles, then onwards to London), and b) you're in CPT and there still aren't any direct routes to Mtunzini from CPT, so that adds a fair bit of latency while traffic crosses to JHB > DBN then onwards.
 
@websquadza Over the past couple weeks i have been having my net drop every now and then I couldnt pin point it though as things like my work resources and voip phone would drop but by the time I got MTR up it was back, caught it now while doing some MTRs for your support desk -

1600332594204.png
 
@websquadza Over the past couple weeks i have been having my net drop every now and then I couldnt pin point it though as things like my work resources and voip phone would drop but by the time I got MTR up it was back, caught it now while doing some MTRs for your support desk -

View attachment 914765

Will look into this. Apologies, confused you for having GPON yesterday, you are on the Vuma trenched network. That highlighted hop is a Vumatel router that doesn't always respond to ICMP - it's not causing packet loss. What's interesting is that you have some PL carrying through. We're running tests to the above IPs from our side to isolate a cause.
 
Will look into this. Apologies, confused you for having GPON yesterday, you are on the Vuma trenched network. That highlighted hop is a Vumatel router that doesn't always respond to ICMP - it's not causing packet loss. What's interesting is that you have some PL carrying through. We're running tests to the above IPs from our side to isolate a cause.
Just curious how does a device not always respond to ICMP? Its either open or not right?
 
Just curious how does a device not always respond to ICMP? Its either open or not right?

Generally ICMP is a pretty low priority protocol, and some core devices have rate limiters on them for ICMP - so only x number of requests per second are allowed and the rest are dropped. A core device on Vumatel's network is more likely to receive a flood of ICMP requests and as such, a rate limiter is pretty good idea - you want this router forwarding traffic, not spending most of it time replying to pings. A MTR tests is basically a tool that sets individual ICMP sessions to each router it sees along the way, so it doesn't actually track the packet as it moves through each router and report on the full path - if that makes sense. So think of it as more of a overview of what is happening and not an actual reflection. But it's pretty useful for troubleshooting obvious issues.
 
Generally ICMP is a pretty low priority protocol, and some core devices have rate limiters on them for ICMP - so only x number of requests per second are allowed and the rest are dropped. A core device on Vumatel's network is more likely to receive a flood of ICMP requests and as such, a rate limiter is pretty good idea - you want this router forwarding traffic, not spending most of it time replying to pings. A MTR tests is basically a tool that sets individual ICMP sessions to each router it sees along the way, so it doesn't actually track the packet as it moves through each router and report on the full path - if that makes sense. So think of it as more of a overview of what is happening and not an actual reflection. But it's pretty useful for troubleshooting obvious issues.
Awesome, thanks for that explanation :)
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X