Web Squad ISP

Status
Not open for further replies.
Twitter, YouTube, etc not streaming video. Your side? Theirs? Something else?
 
So it looks like Tarkov uses Datapacket (CDN77) to host their London servers, a reverse trace from these servers shows the following:
Code:
HOST: 10g-lon-kvm-1-185-59-221-51 Loss%   Snt   Last   Avg  Best  Wrst StDev

  1. AS60068  185.59.221.61        0.0%    10    0.1   0.3   0.1   2.4   0.7

  2. AS???    138.199.0.76         0.0%    10    0.3   0.2   0.1   0.3   0.0

  3. AS201011 81.95.2.141          0.0%    10    0.7   1.0   0.3   4.7   1.2

  4. AS201011 5.56.18.94           0.0%    10   68.8  68.8  68.6  69.4   0.0

  5. AS???    198.32.160.243       0.0%    10  198.8 198.9 198.8 198.9   0.0

  6. AS37497  197.148.71.81        0.0%    10  215.5 215.4 215.4 215.6   0.0

  7. AS174    206.249.0.202        0.0%    10  237.5 233.9 233.4 237.5   1.2

  8. AS328137 160.119.224.21       0.0%    10  214.9 215.0 214.9 215.6   0.0

  9. AS328137 160.119.230.1       10.0%    10  234.2 235.1 233.6 239.7   2.0

The 4th hop (AS201011) seems to be an issue here, adding +- 70ms. I've seen on other threads this is a common issue across transit paths. We have mailed CDN77 to look into this route, as we have other, shorter paths they can reach us at.



This will generally be because of server host selection. If the host doesn't peer with PCCW or at Singapore IX, then the path will be longer, even though we have shorter paths. I know one of the hosts uses HE, who only have the long path from Singapore to SA.

Will update you on the CDN77 issue ASAP

Thank you, it seems to be deteriorating to be honest, tonight it's an extra 30ms ping on top of what I showed, in the 200s for EU.
 
Thank you, it seems to be deteriorating to be honest, tonight it's an extra 30ms ping on top of what I showed, in the 200s for EU.
Definitely a server/game side issue, we haven't made any changes that can affect routing there (all our paths (4 upstreams) showed similar results) - if anything, make Valorant aware of this. We've tested across multiple networks (looking glasses, and direct MTRs from some networks) and seeing over 200ms to 185.59.221.61 consistently. That AS201011 seems to be the culprit. Possibly some sort of temp DDOS route they've implemented to protect their network against an attack.
 
Definitely a server/game side issue, we haven't made any changes that can affect routing there (all our paths (4 upstreams) showed similar results) - if anything, make Valorant aware of this. We've tested across multiple networks (looking glasses, and direct MTRs from some networks) and seeing over 200ms to 185.59.221.61 consistently. That AS201011 seems to be the culprit. Possibly some sort of temp DDOS route they've implemented to protect their network against an attack.
I was playing with some buddies on who are running on Vox and cool ideas and they were getting 144-146ms to Valorant London region. I'll try and get you another IP when I hop on again
 
Fyi - Cool Ideas CPT

Code:
xxxxxxxx -> 185.59.221.61 2022-07-25T04:55:56+0200
Keys: Help Display mode Restart statistics Order of fields
quit Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.xx.xx 0.0% 50 0.5 0.5 0.3 0.7 0.1
2. 154.0.0.245 0.0% 50 1.1 1.1 0.9 1.6 0.1
3. 100.98.0.3 0.0% 50 1.3 1.2 0.9 2.6 0.2
100.98.0.1
100.98.0.2
4. 100.99.0.126 0.0% 50 140.8 140.9 140.7 141.2 0.1
5. (waiting for reply)
6. 154.54.57.153 0.0% 50 141.8 141.7 141.4 142.3 0.2
7. 154.54.61.254 0.0% 50 141.6 141.9 141.5 145.7 0.6
8. 149.6.149.234 0.0% 50 148.3 148.2 148.0 148.7 0.1
9. 138.199.0.75 0.0% 50 148.2 148.2 148.0 148.5 0.1
10. 185.59.221.61 0.0% 49 148.3 148.2 148.1 148.8 0.1
 
I was playing with some buddies on who are running on Vox and cool ideas and they were getting 144-146ms to Valorant London region. I'll try and get you another IP when I hop on again
If you can get me some more IPs to look at.

Fyi - Cool Ideas CPT

Code:
xxxxxxxx -> 185.59.221.61 2022-07-25T04:55:56+0200
Keys: Help Display mode Restart statistics Order of fields
quit Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.xx.xx 0.0% 50 0.5 0.5 0.3 0.7 0.1
2. 154.0.0.245 0.0% 50 1.1 1.1 0.9 1.6 0.1
3. 100.98.0.3 0.0% 50 1.3 1.2 0.9 2.6 0.2
100.98.0.1
100.98.0.2
4. 100.99.0.126 0.0% 50 140.8 140.9 140.7 141.2 0.1
5. (waiting for reply)
6. 154.54.57.153 0.0% 50 141.8 141.7 141.4 142.3 0.2
7. 154.54.61.254 0.0% 50 141.6 141.9 141.5 145.7 0.6
8. 149.6.149.234 0.0% 50 148.3 148.2 148.0 148.7 0.1
9. 138.199.0.75 0.0% 50 148.2 148.2 148.0 148.5 0.1
10. 185.59.221.61 0.0% 49 148.3 148.2 148.1 148.8 0.1
Thanks, seeing the same out of our CPT core this morning:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            172.16.106.1 -    0 |    5 |    5 |    0 |    0 |    0 |    0 |
|          core.as-01-xe.cp1.za.ws.net.za -    0 |    5 |    5 |    0 |    0 |    3 |    0 |
|                           100.99.197.61 -    0 |    5 |    5 |    1 |    1 |    3 |    1 |
|        core.pe-xe-ip01.cp1.za.ws.net.za -    0 |    5 |    5 |    1 |    1 |    3 |    1 |
|           249-68-148-197.as37497.za.net -    0 |    5 |    5 |    1 |    1 |    3 |    1 |
|            54-71-148-197.as37497.za.net -    0 |    5 |    5 |  141 |  141 |  143 |  141 |
|                           197.148.66.41 -    0 |    5 |    5 |  141 |  141 |  143 |  141 |
|te0-3-0-0-4.rcr21.b015533-1.lon13.atlas.cogentco.com -    0 |    5 |    5 |  176 |  176 |  178 |  176 |
|   be2375.ccr41.lon13.atlas.cogentco.com -    0 |    5 |    5 |  176 |  176 |  177 |  176 |
|   be2572.ccr21.lon02.atlas.cogentco.com -    0 |    5 |    5 |  176 |  176 |  178 |  176 |
|                           149.6.148.194 -    0 |    5 |    5 |  148 |  148 |  149 |  148 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|             unn-185-59-221-61.cdn77.com -    0 |    5 |    5 |  148 |  148 |  149 |  148 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

JHB still high, which leads me to think that there's an issue on reverse path advertisements with an upstream, and why CDN77 is favouring this longer route for those prefixes. Saw similar issues with transit networks like Seacom and Liquid on their looking glasses- Will investigate further.
 
You can't make this stuff up: "As per latest update from our service provider team, the manhole and route fell in the river." - most recent update on a NLD outage on JHB<>KZN path (Don't worry, we have redundancy, but just thought I would share).
 
Drop me a pm or ticket with the DST IP/AS and I’ll get this sorted out for you
hmm... DoS triggering again ;(

Ticket #458231updated, same Src/Dst IPs

also, it seems to be "stuck" (with threads) at 200Mbit/sec, not the 500Mb/s I get from speedtests
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X