Severe Packet Loss (NA)

[Psythe]

Was kind of okay for a bit. Has picked back up real bad. 12% loss at a NTT hop then 69% at glaring issue.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Removed for privacy - 0 | 1193 | 1193 | 0 | 2 | 58 | 1 |
| Removed for privacy - 0 | 1193 | 1193 | 8 | 14 | 100 | 10 |
| hrdyar-core1-bnd1.fidnet.com - 0 | 1193 | 1193 | 8 | 16 | 126 | 19 |
| thyrmo-core1-bnd11.fidnet.com - 0 | 1193 | 1193 | 10 | 17 | 99 | 12 |
| wplnmo-core1-bnd10.fidnet.com - 1 | 1189 | 1188 | 11 | 17 | 106 | 12 |
| salmmo-core1-bnd4.fidnet.com - 0 | 1193 | 1193 | 12 | 21 | 125 | 23 |
| sllvmo-lcore2-bnd10.fidnet.com - 0 | 1193 | 1193 | 13 | 21 | 335 | 18 |
| 216-229-73-159.fidnet.com - 0 | 1193 | 1193 | 13 | 21 | 124 | 15 |
| 216-229-74-116.fidnet.com - 1 | 1189 | 1188 | 13 | 19 | 149 | 20 |
| 216-229-73-111.fidnet.com - 0 | 1193 | 1193 | 15 | 23 | 144 | 20 |
| stl-asr9010-bnd15.fidnet.com - 1 | 1186 | 1184 | 16 | 22 | 132 | 21 |
| 67-60-16-121.cpe.sparklight.net - 0 | 1193 | 1193 | 26 | 33 | 173 | 29 |
| 10.224.253.233 - 0 | 1193 | 1193 | 33 | 41 | 153 | 43 |
| chi-b23-link.ip.twelve99.net - 0 | 1193 | 1193 | 27 | 36 | 170 | 30 |
| ae-25.r08.chcgil09.us.bb.gin.ntt.net - 0 | 1193 | 1193 | 28 | 36 | 170 | 36 |
| ae-4.r23.chcgil09.us.bb.gin.ntt.net - 0 | 1193 | 1193 | 27 | 35 | 213 | 50 |
| ae-1.r24.snjsca04.us.bb.gin.ntt.net - 12 | 836 | 743 | 0 | 89 | 360 | 92 |
| ae-4.r00.scrmca02.us.bb.gin.ntt.net - 3 | 1077 | 1047 | 84 | 91 | 277 | 89 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 3 | 1080 | 1051 | 83 | 91 | 246 | 87 |
| 204.2.229.230 - 69 | 322 | 100 | 0 | 92 | 143 | 86 |
| 204.2.229.9 - 3 | 1084 | 1056 | 83 | 91 | 186 | 91 |

[Annabellechu]

@Psythe Are you playing on wi-fi? 100/58 on first 2 hops (worst) for ping doesn't sound normal

[ApeKing]

I have pretty much accepted that until they they do something about NTT, I won't able to play the game. And seeing as NTT has been an issue for this game for quite some time and nothing has ever been done about it, I think that's gonna be a pretty big IF instead of when.

[Psythe]

@Annabellechu That's from the first hop from the gateway(modem) to the node. I have full access to my gateway and run business level gear. An occasional drop or delay in response can happen anywhere and not be abnormal. That is nearly 1200 ICMP requests. A random hi frequency radio signal could have bumped the line or the universe decided to queue up a packet at the node. An average of 2ms and 14ms with 0 loss is not bad. Nor would a 100ms delay anywhere on that entire path cause the end resulting issue. But if you would like to know I run wired connections to each of my multiple gaming pc's. Gigabit ports on both ends running CAT 6 cables for my internal network.

[Catwho]

The node giving me the most issues right now is NTT's San Jose hop. Unfortunately, the VPN WTFast is unable to route past this, since it's the second to last hop. VPN isn't going to fix this one, unfortunately.