Web Squad ISP

Status
Not open for further replies.
I wonder how I could get a BGP feed from WebSquad containing only their "local" peering networks... would help me in doing SD-WAN routing from my Fortigate.... time for a 2nd ISP uing different upstreams ;(
 
Most of my local websites also not loading. Struggling massivly.. retrying upto 3 or 4 at times
 
Probably early morning maintenance from a transit provider

PS. Surprised at how many people are awake at this time of the morning hahah
PPS. I say transit because my Telkom LTE is struggling just as badly

Edit: Things seem back to normal again...
 
Last edited:
DarkSt0rm said:
Probably early morning maintenance from a transit provider

PS. Surprised at how many people are awake at this time of the morning hahah
PPS. I say transit because my Telkom LTE is struggling just as badly

Edit: Things seem back to normal again...
Click to expand...
Dunno, things still seem broken here... Looks like the same problem as last time? Dropping at 197.157.79.33

Edit: Seems like we're back.
 
Meester said:
I wonder how I could get a BGP feed from WebSquad containing only their "local" peering networks... would help me in doing SD-WAN routing from my Fortigate.... time for a 2nd ISP uing different upstreams ;(
Click to expand...

Looks like the problematic carrier being problematic again. Our new carrier asked for a week to send LOAs onwards to their transit partners (to ensure everyone accepts ours and client prefixes). Fingers crossed this is finalised and we can spin them up and drop the problematic guys altogether this week.

As much as I wish things would speed up, carriers move at a glacial pace.
 
Zodiak said:
After you guys turned on China Telecoms again, my PUBG ping is back to 215ms, so I don't think it is AWS but rather China Telecoms that are causing these peering issues.
Click to expand...

We're not sure how CT managed to affect AWS to this extent yet. Our Direct Connect and Peering make us the shortest AS path to and from AWS's network. However, draining CT did indeed do the trick. I suspect is has something to do with how CT announce us to AWS in Asia. However, all the traceroutes/MTRs supplied by you and other helpful people here showed paths going as they should (AWS > Peering > Web sQuad).
 
Meester said:
Needed to get something finished that been haggling me the past month and and and and


Not quite yet based on my FortiGate's SLA monitoring
Click to expand...

Last incident seems to have been at 06:43 +- a few mins for reconvergence. Please let me know if this continues.
 
Tokolosk said:
Hi Websquadza, here's the MTR. I have submitted tickets and Carl has been very helpful in the past but he must be on leave as haven't gotten a response since 16/08/2019. Ticket number is 465448.

Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             dlinkrouter -    1 |  380 |  379 |    0 |   16 |  108 |    0 |
|          as-vuma.cp-gwf-03.za.ws.net.za -    0 |  380 |  380 |    0 |   15 |  109 |    0 |
|             core.as-01.cp1.za.ws.net.za -    0 |  380 |  380 |    0 |   15 |  101 |   28 |
|             core.cr-01.cp1.za.ws.net.za -    0 |  380 |  380 |    0 |   17 |   99 |    0 |
|        core.pe-xe-ip01.cp1.za.ws.net.za -    0 |  380 |  380 |    0 |    7 |   80 |   15 |
|                           197.157.79.33 -    0 |  380 |  380 |    0 |   25 |  194 |    0 |
|                   No response from host -  100 |  380 |    0 |    0 |    0 |    0 |    0 |
|        agr1-gwf-cr2-gi0-0-1.wolcomm.net -    1 |  380 |  379 |    0 |   10 |  111 |    0 |
|                   No response from host -  100 |  380 |    0 |    0 |    0 |    0 |    0 |
|                           41.78.188.225 -   24 |  380 |  292 | 47038 | 4918 | 50705 | 49292 |
|        agr1-lhx-cr1-te0-1-0.wolcomm.net -    0 |  380 |  380 |  134 |  156 |  240 |  156 |
|gi0-6-1-7.rcr21.b015533-1.lon01.atlas.cogentco.com -    4 |  380 |  368 |  140 |  186 |  334 |  156 |
|   be2867.ccr22.lon01.atlas.cogentco.com -    3 |  380 |  372 |  147 |  189 |  467 |  156 |
|   be2869.ccr42.lon13.atlas.cogentco.com -    4 |  380 |  368 |  148 |  186 |  243 |  172 |
|   be2101.ccr32.bos01.atlas.cogentco.com -    3 |  380 |  369 |  201 |  246 |  350 |  278 |
|   be3600.ccr22.alb02.atlas.cogentco.com -    4 |  380 |  366 |  205 |  253 | 1278 | 1278 |
|   be2879.ccr22.cle04.atlas.cogentco.com -    4 |  380 |  367 |  219 |  269 |  362 |  282 |
|   be2718.ccr42.ord01.atlas.cogentco.com -    3 |  380 |  372 |  234 |  276 |  338 |  297 |
|   be2248.ccr22.ord03.atlas.cogentco.com -    3 |  380 |  372 |  228 |  270 |  349 |  281 |
|be2616.rcr21.b002281-5.ord03.atlas.cogentco.com -    2 |  380 |  374 |  226 |  272 |  373 |  295 |
|                             169.254.0.0 -    2 |  379 |  373 |  229 |  258 |  363 |  276 |
|                           10.255.18.171 -    2 |  379 |  372 |  222 |  252 |  319 |  255 |
|              wotna3.login.wargaming.net -    4 |  379 |  367 |  228 |  257 |  313 |  255 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir  ( [email protected] )
Click to expand...

It's Carl here. Apologies, looks like your ticket was assigned to someone else and didn't show up on my dashboard. Will follow up on this today.
 
ISP cash cow said:
My vumatel aerial in Constanta kloof has just died? Anybody got any issues @websquadsa
Click to expand...

Seems to have been related to all the power issues in the region yesterday. Are you back up? If not, please send us a ticket so our team can escalate to Vumatel.
 
DarkSt0rm said:
Apex was fine earlier (was seeing 157 in JHB), but LoL has been painful tonight. Seeing between 200 and 300ms (also seen 400ms spikes) on EU west (usually around 160).

Downloads from the EU are still coming down around 60MB/s though (online.net server), and if I ping the same server I'm seeing the usual 160s. Tried doing a tracert to the LoL server but just got a bunch of no responses after the WS node.
Click to expand...

Was this to the main servers (104...)? Any Improvements since?
 
Cape Town Update: Carrier experienced a DDOS attack on one of their clients (another CPT based ISP) which overwhelmed an aggregation switch. DDOS has been blackholed and things should be back to normal.
 
Meester said:
Perhaps I should post that CT report here too??? :(



Seems green again :)
Click to expand...

Read through that report, pretty interesting stuff... For now CT remains drained until we can figure out what they are doing and if it was anything that the report mentions. Problem is, they're peering and swapping transit with SA transit providers as a crazy pace. After we showed that <150ms Asia was possible, some ISPs leaned on Liquid to complete peering with CT. ISPs using WIOCC did the same.. It's whack-a-mole with these guys and I'm starting to understand why most SA providers have simply ignored the benefit of shorter Asiatic routes until now.

That being said, our plan with CT was always just to get the best out of Asia from them. We've now requested specifically that from them.
 
Perhaps get *just* ASIA from them.... but then... the moment you advertise your routes via them, they can advertise it elsewhere "shorter".... like in Europe (with what happened with Worldstream.nl and us earlier this month ;( )
 
websquadza said:
We're not sure how CT managed to affect AWS to this extent yet. Our Direct Connect and Peering make us the shortest AS path to and from AWS's network. However, draining CT did indeed do the trick. I suspect is has something to do with how CT announce us to AWS in Asia. However, all the traceroutes/MTRs supplied by you and other helpful people here showed paths going as they should (AWS > Peering > Web sQuad).
Click to expand...

Well tonight all seems to still be ok, fingers crossed it will stay that way
 
Looks like Cloudflare ZA is ****ed again - routing via East Africa to MyBroadband.
 
waylander said:
Looks like Cloudflare ZA is ****ed again - routing via East Africa to MyBroadband.
Click to expand...

Wondering why I'm going through Durban though (edit: assuming dur1.he.net is Durban)

Code: 
Tracing route to mybroadband.co.za [104.20.10.169]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Gateway [192.168.1.1]
  2     2 ms     1 ms     2 ms  as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
  3     1 ms     1 ms     1 ms  core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
  4     1 ms     1 ms     1 ms  core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
  5     1 ms     4 ms     1 ms  core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
  6     *        2 ms     1 ms  v101.core2.bcn1.he.net [216.66.90.117]
  7     9 ms     9 ms    10 ms  e0-24.core1.dur1.he.net [184.105.222.62]
  8    56 ms    55 ms    55 ms  10ge0-48.core1.mba1.he.net [184.104.192.85]
  9   133 ms   133 ms   133 ms  10ge14-6.core1.jib1.he.net [184.105.81.142]
10   212 ms   212 ms   212 ms  cloudflare.v4.peers.djix.dj [196.223.38.207]
11   212 ms   212 ms   213 ms  104.20.10.169
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X