Hello,
So to give you some background, I live in Boise Idaho and I usually experience ~40ms latency to the west coast NA server for BF1, and ~80ms latency to the east coast NA server for BF1.
It would seem that, for unknown reasons, my latency to both servers has more than doubled. I usually get around 175ms now, and i've seen it in game go all the way up to 5,448ms.
below is a mtr report and pathping.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 319 | 319 | 0 | 0 | 1 | 0 |
| boid-dsl-gw14.boid.qwest.net - 0 | 319 | 319 | 14 | 15 | 72 | 14 |
| boid-agw1.inet.qwest.net - 0 | 319 | 319 | 14 | 17 | 77 | 14 |
| sea-brdr-02.inet.qwest.net - 0 | 319 | 319 | 24 | 26 | 93 | 25 |
| lag-10.ear2.Seattle1.Level3.net - 20 | 183 | 148 | 25 | 26 | 121 | 25 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| 4.79.23.202 - 0 | 319 | 319 | 83 | 84 | 104 | 84 |
| 159.153.92.10 - 1 | 311 | 309 | 132 | 170 | 189 | 166 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 65 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
C:\Users\BACKF>pathping easo.ea.com
Tracing route to easo.ea.com [159.153.234.54]
over a maximum of 30 hops:
0 DESKTOP-IRCR3LL.Home [192.168.0.3]
1 192.168.0.1
2 boid-dsl-gw14.boid.qwest.net [184.99.64.14]
3 boid-agw1.inet.qwest.net [184.99.65.105]
4 sea-brdr-02.inet.qwest.net [67.14.41.194]
5 ae-20.a00.sttlwa01.us.bb.gin.ntt.net [129.250.9.133]
6 ae-14.r05.sttlwa01.us.bb.gin.ntt.net [129.250.5.133]
7 ae-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.88]
8 ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
9 ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
10 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
11 ae-7.r11.snjsca04.us.ce.gin.ntt.net [165.254.191.158]
12 a209-200-184-194.deploy.static.akamaitechnologies.com [209.200.184.194]
13 a209-200-184-199.deploy.static.akamaitechnologies.com [209.200.184.199]
14 a72-52-44-218.deploy.static.akamaitechnologies.com [72.52.44.218]
15 159.153.92.10
16 159.153.93.6
17 159.153.225.67
18 fert01.abn-iad.ea.com [159.153.226.65]
19 easo.ea.com [159.153.234.54]
Computing statistics for 475 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-IRCR3LL.Home [192.168.0.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% boid-dsl-gw14.boid.qwest.net [184.99.64.14]
0/ 100 = 0% |
3 18ms 0/ 100 = 0% 0/ 100 = 0% boid-agw1.inet.qwest.net [184.99.65.105]
0/ 100 = 0% |
4 25ms 0/ 100 = 0% 0/ 100 = 0% sea-brdr-02.inet.qwest.net [67.14.41.194]
0/ 100 = 0% |
5 27ms 0/ 100 = 0% 0/ 100 = 0% ae-20.a00.sttlwa01.us.bb.gin.ntt.net [129.250.9.133]
0/ 100 = 0% |
6 25ms 0/ 100 = 0% 0/ 100 = 0% ae-14.r05.sttlwa01.us.bb.gin.ntt.net [129.250.5.133]
0/ 100 = 0% |
7 27ms 0/ 100 = 0% 0/ 100 = 0% ae-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.88]
0/ 100 = 0% |
8 41ms 0/ 100 = 0% 0/ 100 = 0% ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
0/ 100 = 0% |
9 40ms 0/ 100 = 0% 0/ 100 = 0% ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
0/ 100 = 0% |
10 44ms 0/ 100 = 0% 0/ 100 = 0% ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
0/ 100 = 0% |
11 41ms 0/ 100 = 0% 0/ 100 = 0% ae-7.r11.snjsca04.us.ce.gin.ntt.net [165.254.191.158]
0/ 100 = 0% |
12 40ms 0/ 100 = 0% 0/ 100 = 0% a209-200-184-194.deploy.static.akamaitechnologies.com [209.200.184.194]
0/ 100 = 0% |
13 40ms 0/ 100 = 0% 0/ 100 = 0% a209-200-184-199.deploy.static.akamaitechnologies.com [209.200.184.199]
0/ 100 = 0% |
14 93ms 0/ 100 = 0% 0/ 100 = 0% a72-52-44-218.deploy.static.akamaitechnologies.com [72.52.44.218]
0/ 100 = 0% |
15 161ms 0/ 100 = 0% 0/ 100 = 0% 159.153.92.10
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% 159.153.93.6
0/ 100 = 0% |
17 162ms 1/ 100 = 1% 1/ 100 = 1% 159.153.225.67
0/ 100 = 0% |
18 --- 100/ 100 =100% 100/ 100 =100% fert01-eqx-iad.ea.com [159.153.226.65]
0/ 100 = 0% |
19 179ms 0/ 100 = 0% 0/ 100 = 0% easo.ea.com [159.153.234.54]
Trace complete.
seems to show that once it reaches the ea servers, it's way up there.
here is another UOtrace showing just how volatile it is. i ran this about an hour after the first one, and it seems to have gone down to the 80's for east coast again, which is at least playable.
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
* Unknown Host * 192.168.0.1 1 1ms 0ms 0% 101 / 101 0ms / 1ms
boid-dsl-gw14.boid.qwest.net 184.99.64.14 2 19ms 18ms 0% 101 / 101 17ms / 29ms
boid-agw1.inet.qwest.net 184.99.65.105 3 18ms 18ms 0% 101 / 101 17ms / 75ms
sea-brdr-02.inet.qwest.net 67.14.41.194 4 28ms 28ms 0% 101 / 101 28ms / 39ms
ae-20.a00.sttlwa01.us.bb.gin.ntt.net 129.250.9.133 5 28ms 30ms 0% 101 / 101 28ms / 52ms
ae-9.r04.sttlwa01.us.bb.gin.ntt.net 129.250.5.117 6 28ms 28ms 0% 101 / 101 28ms / 40ms
ae-5.r21.sttlwa01.us.bb.gin.ntt.net 129.250.2.7 7 28ms 29ms 0% 101 / 101 28ms / 62ms
ae-3.r23.snjsca04.us.bb.gin.ntt.net 129.250.3.124 8 44ms 43ms 0% 101 / 101 42ms / 45ms
ae-45.r01.snjsca04.us.bb.gin.ntt.net 129.250.3.175 9 43ms 43ms 0% 100 / 101 43ms / 48ms
ae-1.a00.snjsca04.us.bb.gin.ntt.net 129.250.2.228 10 44ms 44ms 0% 101 / 101 42ms / 56ms
ae-7.r11.snjsca04.us.ce.gin.ntt.net 165.254.191.158 11 43ms 43ms 0% 101 / 101 43ms / 52ms
a209-200-184-202.deploy.static.akamaitechnologies.com 209.200.184.202 12 42ms 42ms 0% 100 / 100 42ms / 48ms
a209-200-184-207.deploy.static.akamaitechnologies.com 209.200.184.207 13 45ms 43ms 0% 100 / 100 43ms / 48ms
a72-52-44-218.deploy.static.akamaitechnologies.com 72.52.44.218 14 96ms 96ms 0% 100 / 100 96ms / 104ms
* Unknown Host * 159.153.92.10 15 89ms 85ms 0% 100 / 100 84ms / 94ms
* Unknown Host * 159.153.93.6 16 98ms 100% 0 / 100
ea-prod-sg-01.xbl-pub.ea.com 159.153.225.71 17 85ms 84ms 0% 100 / 100 84ms / 98ms
* Unknown Host * 159.153.226.67 18 95ms 100% 0 / 100
Any help? i've already had a tech out and theres nothing wrong with modem/router or the line; firmware is up to date, line is clear, bandwidths are fantastic, ports are open.
