Web Squad ISP

Status
Not open for further replies.
Yikes!


Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              router.lan -    0 |  141 |  141 |    1 |    3 |   16 |    2 |
|       as-vuma.jb-is-bry-01.za.ws.net.za -    0 |  141 |  141 |    2 |    6 |   67 |    4 |
|           core.vuma-l3.jb1.za.ws.net.za -    7 |  113 |  106 |    4 |    9 |  227 |    5 |
|          core.as-xe-02.jb1.za.ws.net.za -    0 |  141 |  141 |    2 |    4 |   22 |    3 |
|          core.cr-xe-01.jb1.za.ws.net.za -    0 |  141 |  141 |    2 |    4 |   20 |    3 |
|        core.pe-xe-ix01.jb1.za.ws.net.za -    0 |  141 |  141 |    2 |    5 |  144 |    3 |
|                 196-60-9-105.ixp.joburg -    0 |  141 |  141 |    2 |    7 |  153 |    3 |
|                             52.93.56.24 -    0 |  141 |  141 |   22 |   89 |  185 |  175 |
|                             52.93.56.35 -    0 |  141 |  141 |   22 |   88 |  209 |  172 |
|                           52.93.134.184 -    0 |  141 |  141 |  161 |  231 |  325 |  312 |
|                           52.93.133.189 -   21 |   78 |   62 |    0 |  313 |  350 |  314 |
|                           52.93.134.158 -   21 |   78 |   62 |    0 |  312 |  333 |  314 |
|                           52.93.134.189 -   15 |   92 |   79 |  162 |  168 |  314 |  163 |
|                   No response from host -  100 |   29 |    0 |    0 |    0 |    0 |    0 |
|                          54.239.101.146 -    0 |  141 |  141 |  162 |  231 |  320 |  311 |
|                             52.94.35.49 -   15 |   92 |   79 |  162 |  168 |  314 |  162 |
|                             52.94.35.16 -   15 |   92 |   79 |  163 |  170 |  311 |  163 |
|                            52.94.33.119 -   15 |   92 |   79 |  162 |  168 |  307 |  164 |
|                              52.94.33.4 -   15 |   92 |   79 |  162 |  169 |  312 |  163 |
|                           52.93.134.189 -   21 |   78 |   62 |    0 |  313 |  321 |  313 |
|                   No response from host -  100 |   29 |    0 |    0 |    0 |    0 |    0 |
|                          54.239.101.146 -   21 |   78 |   62 |    0 |  312 |  319 |  316 |
|                             52.94.35.49 -   21 |   78 |   62 |    0 |  312 |  385 |  310 |
|                             52.94.35.16 -   21 |   78 |   62 |    0 |  314 |  332 |  312 |
|ec2-18-130-179-195.eu-west-2.compute.amazonaws.com -    1 |  137 |  136 |  163 |  229 |  321 |  314 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Not going to happen anytime soon. Simply too much risk for the FNOs that these services are used for non-home requirements.
yeah, well.... the problems are the contention ratios etc. and that would be skewed, but yeah, won't mind paying a tad more for that type of "Service" from home, but yeah... the moment the words "business" comes up, then the pictures $$$$$$$$ lights up, and then also the clients then expects 120% bandwidth used 150% of the time... and that I expects the FNOs tries to prevent, else they can't provide the service at the cost they currently do
 
Yikes!


Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              router.lan -    0 |  141 |  141 |    1 |    3 |   16 |    2 |
|       as-vuma.jb-is-bry-01.za.ws.net.za -    0 |  141 |  141 |    2 |    6 |   67 |    4 |
|           core.vuma-l3.jb1.za.ws.net.za -    7 |  113 |  106 |    4 |    9 |  227 |    5 |
|          core.as-xe-02.jb1.za.ws.net.za -    0 |  141 |  141 |    2 |    4 |   22 |    3 |
|          core.cr-xe-01.jb1.za.ws.net.za -    0 |  141 |  141 |    2 |    4 |   20 |    3 |
|        core.pe-xe-ix01.jb1.za.ws.net.za -    0 |  141 |  141 |    2 |    5 |  144 |    3 |
|                 196-60-9-105.ixp.joburg -    0 |  141 |  141 |    2 |    7 |  153 |    3 |
|                             52.93.56.24 -    0 |  141 |  141 |   22 |   89 |  185 |  175 |
|                             52.93.56.35 -    0 |  141 |  141 |   22 |   88 |  209 |  172 |
|                           52.93.134.184 -    0 |  141 |  141 |  161 |  231 |  325 |  312 |
|                           52.93.133.189 -   21 |   78 |   62 |    0 |  313 |  350 |  314 |
|                           52.93.134.158 -   21 |   78 |   62 |    0 |  312 |  333 |  314 |
|                           52.93.134.189 -   15 |   92 |   79 |  162 |  168 |  314 |  163 |
|                   No response from host -  100 |   29 |    0 |    0 |    0 |    0 |    0 |
|                          54.239.101.146 -    0 |  141 |  141 |  162 |  231 |  320 |  311 |
|                             52.94.35.49 -   15 |   92 |   79 |  162 |  168 |  314 |  162 |
|                             52.94.35.16 -   15 |   92 |   79 |  163 |  170 |  311 |  163 |
|                            52.94.33.119 -   15 |   92 |   79 |  162 |  168 |  307 |  164 |
|                              52.94.33.4 -   15 |   92 |   79 |  162 |  169 |  312 |  163 |
|                           52.93.134.189 -   21 |   78 |   62 |    0 |  313 |  321 |  313 |
|                   No response from host -  100 |   29 |    0 |    0 |    0 |    0 |    0 |
|                          54.239.101.146 -   21 |   78 |   62 |    0 |  312 |  319 |  316 |
|                             52.94.35.49 -   21 |   78 |   62 |    0 |  312 |  385 |  310 |
|                             52.94.35.16 -   21 |   78 |   62 |    0 |  314 |  332 |  312 |
|ec2-18-130-179-195.eu-west-2.compute.amazonaws.com -    1 |  137 |  136 |  163 |  229 |  321 |  314 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Bold is where we handover to AWS. I can try de-peer JHB and CPT and direct connect, but we'll pick up in the EU and as you can see, Europe stopped replying to ICMP a while into the test. Important figure here is the final hop. Final hop shows 1 lost packet in 2 mins. Testing from my side this seems to be showing 0 loss over same time.

Edit: Seeing 98% loss to that last hop. Probably host (server) related.
 
Last edited:
yeah, well.... the problems are the contention ratios etc. and that would be skewed, but yeah, won't mind paying a tad more for that type of "Service" from home, but yeah... the moment the words "business" comes up, then the pictures $$$$$$$$ lights up, and then also the clients then expects 120% bandwidth used 150% of the time... and that I expects the FNOs tries to prevent, else they can't provide the service at the cost they currently do

Exactly, FTTH price points come down to economies of scale and certain expectations of service levels. Business fibre isn't always $$$$. FTTH price points come from the idea that a single install will live on for years, so ROI is slower. The moment a business build is required - build costs, SLA and maintenance all need to be factored in. Recouping a R 50 - 100k build in 24 months, specifically, dictates pricing. Add 4 HR MTTR SLAs, 24 Hr NOCs and more and you start seeing the cost spiral. There's a difference between expecting quick maintenance as a FTTH user and actual punitive SLAs that business services carry. Finally, continuous bandwidth usage (that usually comes with businesses) means more resources are consumed in the DC (Ports, cross connects, switches), requiring stricter management of resources, to deliver bandwidth (the only constant - per mbps used).

I can't speak for the FNOs and their decision to not provide symmetrical 1G services, and moreover, 1G+ services. Within the major metros, the business case will probably arrive soon enough (take into account that the IP transit and NLD requirements on ISPs for these are still very very expensive). The next issue comes in secondary metros; backhaul to major POPs is still very expensive and very slow to grow (we've all seen the issues in these smaller metros on this forum).
 
I'm also seeing strange lag with YouTube videos loading, loads for a while before playing. I remember there was a similar issue a few months ago with Google Services. Not sure if the issue is back
 
Seeing packet loss to eu server?

View attachment 822617
server: 64.46.105.166
Massive packet loss again, and none of my mates in the raid are having issues.
View attachment 822619
View attachment 822621


Apologies here. Picked up issues on a specific JHB-CPT route again. Escalated to the vendor. Made some small changes in the meanwhile.

I'm also seeing strange lag with YouTube videos loading, loads for a while before playing. I remember there was a similar issue a few months ago with Google Services. Not sure if the issue is back

Google's been problematic in SA for the past week and a bit. Their NAP caches in JHB are down, so traffic is coming in from a few different places (so a little heavier latency there).
 
Apologies here. Picked up issues on a specific JHB-CPT route again. Escalated to the vendor. Made some small changes in the meanwhile.

Google's been problematic in SA for the past week and a bit. Their NAP caches in JHB are down, so traffic is coming in from a few different places (so a little heavier latency there).

JHB-CPT issue has been isolated. A fix is being sorted out (won't be service affecting). Apologies for the inconvenience here.
 
@websquadza something going on with you guys or Octotel?


Code:
--- 8.8.8.8 ping statistics ---
159 packets transmitted, 96 packets received, 39.6% packet loss
round-trip min/avg/max/stddev = 23.804/40.189/145.476/12.953 ms

Definitely not my local network I don't think:

Code:
--- 192.168.0.1 ping statistics ---
178 packets transmitted, 178 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.811/1.289/3.322/0.531 ms

Octotel Southern Subs, CPT.

EDIT: Results directly from gateway attached

EDIT 2: not able to get to your website either
 

Attachments

  • Screenshot 2020-04-17 at 09.12.27.png
    Screenshot 2020-04-17 at 09.12.27.png
    90.9 KB · Views: 18
Last edited:
Something is borked. Getting frequent disconnects and girlfiend is unable to stream her zoom class.
 
Doesn't seem to be related to Octotel, also having this on Vumatel:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             dlinkrouter -    0 |   83 |   83 |    0 |    1 |    3 |    1 |
|          as-vuma.cp-gwf-03.za.ws.net.za -    0 |   83 |   83 |    2 |    4 |   24 |    2 |
|             core.as-01.cp1.za.ws.net.za -    0 |   83 |   83 |    1 |    1 |    3 |    1 |
|                         160.119.233.189 -    0 |   83 |   83 |    1 |    1 |    3 |    2 |
|         core.pe-ge-inx.jnb.za.ws.net.za -   63 |   24 |    9 |   35 |   36 |   41 |   36 |
|                      google.jinx.net.za -   66 |   23 |    8 |   36 |   38 |   54 |   36 |
|                          74.125.245.209 -   63 |   24 |    9 |    0 |   36 |   39 |   27 |
|                            172.253.66.3 -   56 |   25 |   11 |    0 |   35 |   37 |   37 |
|                                 8.8.8.8 -   66 |   23 |    8 |   36 |   37 |   38 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Also having trouble with loading local sites: mybroadband.co.za

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             dlinkrouter -    0 |  176 |  176 |    0 |    1 |    4 |    1 |
|          as-vuma.cp-gwf-03.za.ws.net.za -    1 |  172 |  171 |    2 |    4 |   44 |    5 |
|             core.as-01.cp1.za.ws.net.za -    0 |  176 |  176 |    1 |    1 |    8 |    3 |
|             core.cr-01.cp1.za.ws.net.za -    0 |  176 |  176 |    1 |    1 |    7 |    3 |
|        Destination network unreachable. -    6 |  168 |  158 |    1 |   18 |   33 |   31 |
|        Destination network unreachable. -   10 |  148 |  134 |    1 |   23 |   58 |   32 |
|        Destination network unreachable. -   10 |  149 |  135 |    1 |   21 |   38 |   32 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Spoke to one of the support agents, apparently they're aware of it.
Looks like it may have recovered though, not seeing any more loss as of right now, (don't want to speak too soon though)
 
Morning All. Apologies for my silence this morning. Picked up on a distributed DDOS attack against an IP range that started around 08:55. The volume of the attack across our edge and seemingly random routes chosen put some strain on NLD routes until it was mitigated . I can't share a lot more information for obvious reasons. Interesting though is that traffic found its way to us at exchanges, with a large portion of it from a Microsoft peering port (we believe this might be a rogue botnet on Azure). We've mitigated this and we're working with upstreams to ensure the attack remains contained. We're carefully monitoring our edge for any spikes or further issues.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X