Web Squad ISP

Status
Not open for further replies.
Let me know which servers you are seeing this for. Ran a few tests now from a KZN prefix and not seeing any issues from most peers.
Back to normal pings in Durban, however optimum online New York is
96c2548e8fbaf632a6c498da8165ecbb.jpg
 
The entire week wthe ONT / CPE has been going into error mode 2/3 times a day.
I have logged a call with you (222887) and Vumatel ( Aerial Bryanston) supposedly made the line more stable.
It still has gone into error mode twice after that.
The fix was to drop my line speed down to 100/100! Seriously guys!
I have logged another call (208523) to get my line speed back up.
My son is in the middle of an exam (Tuks Engineering) and the link is so unstable he had to switch to a mobile connection to try and finish his exam.

If it's not the billing issues I have had from day 1, it's the unstable connectivity. The occasional hiccup I can understand, but this is now getting ridiculous. I'm getting gatvol now.
Please get my line and the billing sorted now.

Well it just gets better. Now we have no connectivity at all!!!!!
I guess I should have just shut up and accepted the poor service, since limited / unstable connectivity is better than nothing.
 
Well it just gets better. Now we have no connectivity at all!!!!!
I guess I should have just shut up and accepted the poor service, since limited / unstable connectivity is better than nothing.

You're showing up and running on this end - your current session has been up for 30+ minutes and we are seeing traffic flowing through (an average of 30-40 Mbps). Please check your LAN if you are still down.

Your line had an error (light levels dropped below acceptable levels - this can happen if a fibre gets damaged) this week and Vumatel went out to resolve this -as they should - nothing untoward there. If the levels are poor again, we will need to escalate to Vumatel again as this is their infrastructure. However, I have checked your service status and all seems alright from a levels perspective. Your levels have been consistently the same since the repairs earlier this week.
 
The entire week wthe ONT / CPE has been going into error mode 2/3 times a day.
I have logged a call with you (222887) and Vumatel ( Aerial Bryanston) supposedly made the line more stable.
It still has gone into error mode twice after that.
The fix was to drop my line speed down to 100/100! Seriously guys!
I have logged another call (208523) to get my line speed back up.
My son is in the middle of an exam (Tuks Engineering) and the link is so unstable he had to switch to a mobile connection to try and finish his exam.

If it's not the billing issues I have had from day 1, it's the unstable connectivity. The occasional hiccup I can understand, but this is now getting ridiculous. I'm getting gatvol now.
Please get my line and the billing sorted now.

No service change occurred - I've checked service logs on both our AAA system as well as Vumatel. Did you try connect your PC directly to the ONT, establish a PPPOE and run a test there to eliminate a LAN issue?
 
Back to normal pings in Durban, however optimum online New York is
96c2548e8fbaf632a6c498da8165ecbb.jpg

Waiting for some changes to happen on the new upstream routes as we are unable to steer traffic at present (communities are a bit broken)... Please bear with us on this one until they make their changes.
 
Utter dogshit tonight. Unusable.

Upon further investigation, we see no issues on the network last night. We've looked further into this and picked up DDOS traffic targeted to your IP between 21:15 and 21:50 last night. Our DDOS mitigation service in the UK blackholed your IP 5 times (for 5 minute windows each time) to protect the rest of the network. I just want to confirm more information about the flagged traffic. Were you by any chance running any P2P traffic that may have appeared to look like DDOS (high packet volumes between your IP and another IP)? I don't have these metrics yet and need to request them from upstream, so anything that can help will be good.
 
Upon further investigation, we see no issues on the network last night. We've looked further into this and picked up DDOS traffic targeted to your IP between 21:15 and 21:50 last night. Our DDOS mitigation service in the UK blackholed your IP 5 times (for 5 minute windows each time) to protect the rest of the network. I just want to confirm more information about the flagged traffic. Were you by any chance running any P2P traffic that may have appeared to look like DDOS (high packet volumes between your IP and another IP)? I don't have these metrics yet and need to request them from upstream, so anything that can help will be good.
Hi, at the time I was downloading apex using the origin application.
 
The disconnects are local, intermittent however. I am not sure if it was MTU or the MT router that made the difference since last week. I am still seeing some rubber banding tonight but not sure if these are new issues or the old issues coming back, for all I know it is the battle.net local servers up to k@k. I'm just tired of constant issues to be honest, if it is not one thing it's another almost weekly. If I had to log a ticket for every issue I would be logging 3 tickets a week which I just don't have the energy to do anymore. I know you guys are very responsive and helpful and I appreciate it, I just wish I could have a few weeks straight without problems
Just to add, the disconnects in game happen when Battle.net launches loses connection to it's server which is international and that interrupts the match that I am in, saying you've been disconnected and the client then shows disconnected, if that helps with troubleshooting. I would guess international issue but I'm not the expert. It's not contact, once an hour or so today.

Based on the above, we can confirm that there were no issues on transit last night. I've checked your IP and see no alarms, so you were not affected like the other user.

The fact that the MTU change helped tells us that there is an issue with the FNO again. I've escalated again, but I'm sure you remember how long it took last time. The next thing I'd like to test with you is adjusting the MTU upwards until we find the sweetspot (max) that doesn't result in an error. Dropping to 1400 is a little extreme and more of a band aid than anything else. If you can, when you have time, test 1480 and 1460, we will then adjust our Evotel VLANs to a permanent, lower value to compensate for their ongoing issues.
 
You're showing up and running on this end - your current session has been up for 30+ minutes and we are seeing traffic flowing through (an average of 30-40 Mbps). Please check your LAN if you are still down.

Your line had an error (light levels dropped below acceptable levels - this can happen if a fibre gets damaged) this week and Vumatel went out to resolve this -as they should - nothing untoward there. If the levels are poor again, we will need to escalate to Vumatel again as this is their infrastructure. However, I have checked your service status and all seems alright from a levels perspective. Your levels have been consistently the same since the repairs earlier this week.

Thanks for the response.
The line did come back and go down again. When it came back the second time suddenly the line speed was at 200Mb/s again.

I do not have LAN issues. I have explained in detail in my response to the support email about my infrastructure and what I did to troubleshoot. I have 20+ years IT experience so it's pretty rare for me to misdiagnose a LAN vs. WAN issue.
My simplified troubleshooting process tells me that when there is a red fault light on the CPE it is NOT a LAN issue.
If my devices on my internal network can communicate to the devices on my external network it's not a LAN issue. The only area where the problem can be is the WAN router or external infrastructure and those two devices in my control were rebooted before I logged the calls.

That screenshot of activity that you sent was for a period of 2 minutes. Send me a screenshot of the period starting 30 minutes before I logged the calls, for at least an hour long please. Then we can try and do some proper analysis.

I have previously logged calls for the CPE hanging / losing connectivity, and was told Vumatel have 'resolved' the issues but not exactly what they did to resolve them.

I do appreciate the response. It's just frustrating when my son is stressing because he is in the middle of an exam and the internet connectivity is unreliable.
 
Based on the above, we can confirm that there were no issues on transit last night. I've checked your IP and see no alarms, so you were not affected like the other user.

The fact that the MTU change helped tells us that there is an issue with the FNO again. I've escalated again, but I'm sure you remember how long it took last time. The next thing I'd like to test with you is adjusting the MTU upwards until we find the sweetspot (max) that doesn't result in an error. Dropping to 1400 is a little extreme and more of a band aid than anything else. If you can, when you have time, test 1480 and 1460, we will then adjust our Evotel VLANs to a permanent, lower value to compensate for their ongoing issues.

@Zodiak I had a spotty VPN conenction to the office so used this little tool to get the sweetspot for my MTU. Zero issues since changing it 1472 .

1599374946055.png
 
I wish it were that simple. Our network is finely tuned to steer inbound traffic as opposed to a CDN who do the opposite. Remember, inbound traffic isn't chosen by us as an ISP, we can only choose outbound routes. Rather is nudged in the right direction through a complex selection of filters on our side to influence an upstreams router to favour one path over another. We need to do this carefully to a) manage performance (shortest and most optimal route) and b) manage resiliency (just because a route is bad, doesn't mean it must be removed altogether, because in a catastrophic failure, that route may be the only thing keeping a certain service up). Bringing up new upstreams, and upstreams bringing up new upstreams can interfere by causing route leaks in directions we prefer traffic not to flow. So it's a painstaking task getting it just right.
Make sense, i am not as clued up with the IT side, what is cool is that your ISP is assisting with gaming issues well done to you
 
@websquadza something very wrong this side:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   27 |   27 |    0 |    0 |    0 |    0 |
|                         160.119.238.105 -   25 |   12 |    9 |    0 |    0 |    2 |    0 |
|             core.cr-01.cp1.za.ws.net.za -   20 |   15 |   12 |    0 |    0 |    3 |    0 |
|           165-69-148-197.as37497.za.net -   20 |   15 |   12 |    0 |    1 |    3 |    0 |
|           162-68-148-197.as37497.za.net -   25 |   12 |    9 |    0 |  143 |  151 |  142 |
|            54-71-148-197.as37497.za.net -   20 |   15 |   12 |    0 |  168 |  234 |  228 |
|            41-66-148-197.as37497.za.net -   25 |   12 |    9 |    0 |  142 |  143 |  142 |
|ge-0-1-0-68.peering1.the.lon1.coreix.net -   25 |   12 |    9 |    0 |  142 |  145 |  142 |
|        xe-6-1.edge4.enf.lon5.coreix.net -   25 |   12 |    9 |    0 |  143 |  146 |  144 |
|        85.13.221.178.reverse.coreix.net -   20 |   15 |   12 |    0 |  143 |  145 |  142 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   22 |   22 |    0 |    0 |    0 |    0 |
|                         160.119.238.105 -    6 |   18 |   17 |    0 |    0 |    1 |    0 |
|             core.cr-01.cp1.za.ws.net.za -    6 |   18 |   17 |    0 |    0 |    1 |    0 |
|        core.pe-xe-ix01.cp1.za.ws.net.za -   34 |    9 |    6 |    2 |    2 |    3 |    2 |
|                 cloudflare.ixp.capetown -   30 |   10 |    7 |    0 |    4 |    5 |    5 |
|                         one.one.one.one -   67 |    6 |    2 |    0 |    4 |    5 |    5 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
@websquadza something very wrong this side:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   27 |   27 |    0 |    0 |    0 |    0 |
|                         160.119.238.105 -   25 |   12 |    9 |    0 |    0 |    2 |    0 |
|             core.cr-01.cp1.za.ws.net.za -   20 |   15 |   12 |    0 |    0 |    3 |    0 |
|           165-69-148-197.as37497.za.net -   20 |   15 |   12 |    0 |    1 |    3 |    0 |
|           162-68-148-197.as37497.za.net -   25 |   12 |    9 |    0 |  143 |  151 |  142 |
|            54-71-148-197.as37497.za.net -   20 |   15 |   12 |    0 |  168 |  234 |  228 |
|            41-66-148-197.as37497.za.net -   25 |   12 |    9 |    0 |  142 |  143 |  142 |
|ge-0-1-0-68.peering1.the.lon1.coreix.net -   25 |   12 |    9 |    0 |  142 |  145 |  142 |
|        xe-6-1.edge4.enf.lon5.coreix.net -   25 |   12 |    9 |    0 |  143 |  146 |  144 |
|        85.13.221.178.reverse.coreix.net -   20 |   15 |   12 |    0 |  143 |  145 |  142 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   22 |   22 |    0 |    0 |    0 |    0 |
|                         160.119.238.105 -    6 |   18 |   17 |    0 |    0 |    1 |    0 |
|             core.cr-01.cp1.za.ws.net.za -    6 |   18 |   17 |    0 |    0 |    1 |    0 |
|        core.pe-xe-ix01.cp1.za.ws.net.za -   34 |    9 |    6 |    2 |    2 |    3 |    2 |
|                 cloudflare.ixp.capetown -   30 |   10 |    7 |    0 |    4 |    5 |    5 |
|                         one.one.one.one -   67 |    6 |    2 |    0 |    4 |    5 |    5 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

All on the first hop from your router - looks like Octotel again. Will log a ticket.
 
All on the first hop from your router - looks like Octotel again. Will log a ticket.

Pretty much cleared up now. Was at 50% packet loss at one stage - would love to know what's going on their side when this happens.
 
Pretty much cleared up now. Was at 50% packet loss at one stage - would love to know what's going on their side when this happens.

Looks like some sort of spanning tree to be honest. Monitoring a few other endpoints on the Rondebosch POP at the moment to see if it's isolated to you or the entire area.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X