Lag Spikes, Rubberbanding, and Busan

Technical Support
1

No, it’s not packet loss, no I’m not on WiFi ( I’m on a wired, CAT-6 line ) and no, it’s not my internet, it’s Rogers Gigabit. No, it’s not my network, my roomie is a network professional and fixes this stuff for a living.

The game is rubberbanding like absolute crazy, despite my ping being between 50-80. It’s stopping for upwards of a second and a half multiple times during matches. Yes, I have tried turning it off and back on again, and I’m about to try a clean install to see if that fixes things. Yes, I use DDU when I upgrade drivers, I’ve had AMD Cards since 2012, I know the drill.

My rig’s drivers are up to date, as is the Bios ( yay, Ryzen…), in addition the memory is Samsung B-Die at 3200Mhz and is rock stable, so don’t start. I do suspect that my GPU may be partly to blame for my performance issues, as it’s a snowflake-y R9 Fury, but still, I don’t have issues with literally any other game.

ALL of this happened after the BUSAN update. Whatever you guys changed, it’s turned a mostly smooth game into a microstuttery, laggy, rubberbanding, disaster.

2

Can you post the WinMTR anyway, just for funsies? :wink:

And also a dxdiag, because we like reading. :face_with_monocle:

3

Here’s mine. I’m also rubberbanding like crazy only in the last few days. Brand new top-of-the-line machine, internet has been solid for the past year and my ISP swears up and down that their end is fine.

TRACEROUTE:
traceroute to 148.64.102.54 (148.64.102.54), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.489 ms 0.475 ms 0.472 ms
2 37.244.22.131 (37.244.22.131) 1.584 ms 1.592 ms 1.604 ms
3 24.105.30.148 (24.105.30.148) 1.604 ms 1.603 ms 1.599 ms
4 137.221.66.0 (137.221.66.0) 1.843 ms 3.470 ms 3.478 ms
5 137.221.68.70 (137.221.68.70) 8.828 ms 8.832 ms 8.837 ms
6 137.221.65.7 (137.221.65.7) 8.781 ms 8.679 ms 8.657 ms
7 137.221.70.32 (137.221.70.32) 8.801 ms 8.383 ms 8.349 ms
8 as32329.sfmix .org (206.197.187.13) 9.603 ms 9.582 ms 9.626 ms
9 lime-te-0-0-1-0.lime-kiwi-10GB.core.monkeybrains .net (208.69.43.189) 10.198 ms 10.172 ms 10.264 ms
10 lick10g.lemon-lick10g-10GB.core.monkeybrains .net (208.69.43.169) 11.105 ms 11.979 ms 11.575 ms
11 148-64-102-54.PUBLIC.monkeybrains .net (148.64.102.54) 12.149 ms 12.392 ms 12.586 ms

06/10/2018 01:37:26 UTC

PING:
PING 148.64.102.54 (148.64.102.54) 56(84) bytes of data.
64 bytes from 148.64.102.54: icmp_seq=1 ttl=54 time=12.2 ms
64 bytes from 148.64.102.54: icmp_seq=2 ttl=54 time=13.2 ms
64 bytes from 148.64.102.54: icmp_seq=3 ttl=54 time=11.8 ms
64 bytes from 148.64.102.54: icmp_seq=4 ttl=54 time=12.3 ms

— 148.64.102.54 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 11.860/12.429/13.235/0.500 ms

06/10/2018 01:37:26 UTC

PING:
PING 148.64.102.54 (148.64.102.54) 56(84) bytes of data.

— 148.64.102.54 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms

06/10/2018 01:37:26 UTC

TRACEROUTE:
traceroute to 148.64.102.54 (148.64.102.54), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.227 ms 2.219 ms 2.216 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

06/10/2018 01:37:26 UTC

MTR:
Start: Sat Oct 6 01:37:26 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0
2.|-- 37.244.22.131 0.0% 10 0.8 0.5 0.5 0.8 0.0
3.|-- 24.105.30.148 0.0% 10 1.0 1.0 0.9 1.0 0.0
4.|-- 137.221.66.0 0.0% 10 1.5 1.5 1.4 1.7 0.0
5.|-- 137.221.68.70 0.0% 10 21.1 136.4 8.4 606.1 198.6
6.|-- 137.221.65.7 0.0% 10 8.5 8.5 8.4 9.5 0.0
7.|-- 137.221.70.32 0.0% 10 8.3 8.3 8.2 8.4 0.0
8.|-- as32329.sfmix .org 0.0% 10 9.8 9.6 9.5 9.8 0.0
9.|-- lime-te-0-0-1-0.lime-kiwi-10GB.core.monkeybrains .net 0.0% 10 10.2 10.3 10.1 10.9 0.0
10.|-- lick10g.lemon-lick10g-10GB.core.monkeybrains .net 0.0% 10 11.0 11.2 10.4 12.1 0.3
11.|-- 148-64-102-54.PUBLIC.monkeybrains .net 0.0% 10 11.9 12.5 11.9 14.1 0.5

06/10/2018 01:37:26 UTC

MTR:
Start: Sat Oct 6 01:37:26 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 1.3 0.3 10.2 3.1
2.|-- 37.244.23.2 70.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- 24.105.62.146 70.0% 10 1.1 1.8 1.0 3.2 1.0
4.|-- 137.221.66.12 70.0% 10 2.6 2.5 2.5 2.6 0.0
5.|-- 137.221.69.68 30.0% 10 49.9 50.0 49.9 50.1 0.0
6.|-- 137.221.65.11 30.0% 10 50.0 50.0 50.0 50.1 0.0
7.|-- 137.221.70.32 70.0% 10 49.3 49.4 49.3 49.5 0.0
8.|-- as32329.sfmix .org 30.0% 10 51.1 51.2 51.1 51.4 0.0
9.|-- lime-te-0-0-1-0.lime-kiwi-10GB.core.monkeybrains .net 57.1% 7 51.6 51.9 51.6 52.0 0.0
10.|-- lick10g.lemon-lick10g-10GB.core.monkeybrains .net 42.9% 7 54.7 55.3 53.9 57.9 1.6
11.|-- 148-64-102-54.PUBLIC.monkeybrains .net 42.9% 7 53.9 54.2 53.9 54.5 0.0

06/10/2018 01:37:26 UTC

4

They won’t find anything because they don’t know what the issue is, or they do know the Busan update broke stuff but don’t know WHY.

5

Well, people of the forums definitely won’t find anything if you don’t post the network test results. Busan update is running better than ever for me and others. Correlation doesn’t imply causation.

6

Hi I think I am in the same boat. I have played over 1,000 hours of OW and have never had rubberbanding issues. Two days ago I played a few games and everything was normal, and the very next game I started rubberbanding all over. Quick Play and Comp. It seems to be ok in the practice range. I connect via ethernet powerline adapter. I just looked into WinMTR and if someone can provide any insight, it would be much appreciated. Thanks!

Operating System: Windows 10 Home 64-bit (10.0, Build 17134)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-78LMT-USB3 6.0
BIOS: Award Modular BIOS v6.00PG
Processor: AMD FX™-6300 Six-Core Processor (6 CPUs), ~3.5 GHz
Memory: 24576 MB RAM

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
routerlogin.ne - 0 432 432 4 10 101 9
astound-69-42-0-1.ca.astound.ne - 0 432 432 19 36 148 34
174.127.183.32 - 0 432 432 19 35 143 31
cr1-che-a-te-0-0-0-5.bb.as11404.ne - 0 432 432 16 36 149 27
cr1-200p-a-hu-0-7-0-20-0.bb.as11404.ne - 0 432 432 16 36 142 30
as57976.sfmix.or - 1 428 427 20 40 127 38
ae1-br01-eqsv5.as57976.ne - 0 432 432 23 39 151 26
xe-0-0-1-1-br02-eqla1.as57976.ne - 1 417 415 29 83 4796 45
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
No response from host - 100 87 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

7

In your case, you’re seeing some mild packet loss before reaching Blizzard servers. It would be something your ISP would have to investigate.

8

Here’s a DXDiag with the graphics portion. The network issues have been fixed by my ISP.

System Information

  Time of this report: 10/8/2018, 14:29:38
         Machine name: Nope.
           Machine Id: Nope.
     Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
             Language: English (Regional Setting: English)
  System Manufacturer: System manufacturer
         System Model: System Product Name
                 BIOS: BIOS Date: 08/20/18 13:52:35 Ver: 05.0000D (type: BIOS)
            Processor: AMD Ryzen 5 1600 Six-Core Processor             (12 CPUs), ~3.2GHz
               Memory: 16384MB RAM
  Available OS Memory: 16318MB RAM
            Page File: 12487MB used, 10999MB available
          Windows Dir: C:\WINDOWS
      DirectX Version: DirectX 12
  DX Setup Parameters: Not found
     User DPI Setting: 96 DPI (100 percent)
   System DPI Setting: 144 DPI (150 percent)
      DWM DPI Scaling: Disabled
             Miracast: Available, with HDCP

Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode

DxDiag Notes

  Display Tab 1: No problems found.
    Sound Tab 1: No problems found.
    Sound Tab 2: No problems found.
    Sound Tab 3: No problems found.
    Sound Tab 4: No problems found.
    Sound Tab 5: No problems found.
      Input Tab: No problems found.

DirectX Debug Levels

Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

Display Devices

       Card name: AMD Radeon (TM) R9 Fury Series
    Manufacturer: Advanced Micro Devices, Inc.
       Chip type: AMD Radeon Graphics Processor (0x7300)
        DAC type: Internal DAC(400MHz)
     Device Type: Full Device (POST)
      Device Key: Enum\PCI\VEN_1002&DEV_7300&SUBSYS_E331174B&REV_CB
   Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]

Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 12230 MB
Dedicated Memory: 4071 MB
Shared Memory: 8159 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.637219,0.341320), Green(0.312023,0.625500), Blue(0.154797,0.054211), White Point(0.313977,0.329602)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: ASUS PB287Q
Monitor Id: ACI28A3
Native Mode: 3840 x 2160§ (59.997Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\c0333764.inf_amd64_239226e8c322a98d\B333740\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\c0333764.inf_amd64_239226e8c322a98d\B333740\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\c0333764.inf_amd64_239226e8c322a98d\B333740\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\c0333764.inf_amd64_239226e8c322a98d\B333740\amdxc64.dll
Driver File Version: 24.20.13019.1008 (English)
Driver Version: 24.20.13019.1008
DDI Version: 12
Feature Levels: 12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.4
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:False
Driver Attributes: Final Retail
Driver Date/Size: 2018-09-24 8:00:00 PM, 1953672 bytes
WHQL Logo’d: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71EE2-3040-11CF-0B77-EAF170C2D535}
Vendor ID: 0x1002
Device ID: 0x7300
SubSys ID: 0xE331174B
Revision ID: 0x00CB
Driver Strong Name: oem8.inf:cb0ae414a513ca4f:ati2mtag_R7000DS:24.20.13019.1008:pci\ven_1002&dev_7300&rev_cb
Rank Of Driver: 00D12000
Video Accel: Unknown
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeVC1_VLD DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC
Deinterlace Caps: n/a
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported

9

I am having this exact same issue, uncle built my computer and he’s a professional 20+ years running a computer repair store, top of the line 1080ti and threadripper processor etc…I tried all the trouble shooting…I AM the cable company…I am a spectrum technician and trouble shooted my modem and lines…zero packet loss coming from my meter and I ran a new outlet and drop on the lowest legs of the splitter, eliminated a little bit of RF noise found on a TV line…TG1682 modem has been checked for controllers and occurrences all of which are built and assigned correctly…and yet im rubber banding like a mad man…all other games run just fine.

10

They broke something, the party line is “correlation doesn’t imply causation” but it’s a bunch of bullshizzle, same boat, no other games affected, but OW’s performance imploded after the Busan update.

11

We need the error reporting at the end of the dxdiag to give any meaningful assessment.

You are free to continue blaming Blizzard (this is not a widespread issue), but please call them if you can’t be nice to those volunteering their time to help you.

12

With all possible respect, I’m not here for your help, unless you’re a developer I’m pretty sure you can’t fix optimization issues. I’m here to make sure that the Blues actually know there’s an issue with performance on the AMD Fiji platform that needs to be addressed.

I do Root Cause Analysis/hardware troubleshooting for a living, and performance issues are part of that, I know what I’m looking for and at this point, all the evidence points to either AMD or Blizzard changing something very recently, within the last month or so.

The problem is that like…4…people have R9 Fury/FuryX cards, they didn’t sell very well and aren’t a big part of the installed base for this game, so I really don’t expect anything. At least hopefully someone may see this and have their interest piqued.

The reason this is not a widespread issue is due to the snowflak-y nature of the setup. If they’d broken performance on the 970 or 1060, you, I guarantee, wouldn’t be saying anything about “correlation not implying causation” to the literal thousands of people who’d dogpile this forum. The problem is that someone changed something, AMD or Blizz, don’t know who, but I can tell you that the changes were not validated on my GPU, as if they were the update wouldn’t have been allowed out the door by QA.

13

I’m in the same boat, lagging like crazy and getting dropped from games, and it also happened right after the Busan update. This has never happened to me before, and it’s only happening on Overwatch, everything else is running smoothly.

1 Like
14

Devs don’t monitor this forum.

15

Back again. Since the winter patch update my game has been sporadically unplayable due to massive, seemingly random rubberbanding. Sometimes the game is great and fine and other times, whole games will just be completely unplayable. People will drift into the air, I’ll be shooting at something and then I’ll snap into a different location or I’ll be dead. It’s awful.

Here’s my looking glass report:

PING:
PING 148.64.102.54 (148.64.102.54) 56(84) bytes of data.
64 bytes from 148.64.102.54: icmp_seq=1 ttl=52 time=19.5 ms
64 bytes from 148.64.102.54: icmp_seq=2 ttl=52 time=17.5 ms
64 bytes from 148.64.102.54: icmp_seq=3 ttl=52 time=16.3 ms
64 bytes from 148.64.102.54: icmp_seq=4 ttl=52 time=16.6 ms

— 148.64.102.54 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 16.376/17.527/19.538/1.256 ms

29/12/2018 20:57:16 UTC

PING:
PING 148.64.102.54 (148.64.102.54) 56(84) bytes of data.
64 bytes from 148.64.102.54: icmp_seq=1 ttl=52 time=16.5 ms
64 bytes from 148.64.102.54: icmp_seq=2 ttl=52 time=16.6 ms
64 bytes from 148.64.102.54: icmp_seq=3 ttl=52 time=16.5 ms
64 bytes from 148.64.102.54: icmp_seq=4 ttl=52 time=16.2 ms

— 148.64.102.54 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 16.248/16.494/16.601/0.213 ms

29/12/2018 20:57:18 UTC

TRACEROUTE:
traceroute to 148.64.102.54 (148.64.102.54), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.699 ms 0.692 ms 0.691 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 148-64-102-54.PUBLIC.monkeybrains .net (148.64.102.54) 17.898 ms 18.987 ms 19.433 ms

29/12/2018 20:57:16 UTC

TRACEROUTE:
traceroute to 148.64.102.54 (148.64.102.54), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.222 ms 0.235 ms 0.245 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 148-64-102-54.PUBLIC.monkeybrains .net (148.64.102.54) 18.088 ms 18.105 ms 18.684 ms

29/12/2018 20:57:19 UTC

MTR:
Start: Sat Dec 29 20:57:16 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/12/2018 20:57:16 UTC

MTR:
Start: Sat Dec 29 20:57:16 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.2 0.2 0.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/12/2018 20:57:16 UTC

Here’s my WinMTR:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.7.1 - 0 | 372 | 372 | 0 | 0 | 14 | 0 |

| gw-lick.static.monkeybrains .net - 0 | 372 | 372 | 3 | 16 | 735 | 12 |

|lemon.lemon-lick10g-10GB.core.monkeybrains .net - 0 | 372 | 372 | 2 | 8 | 63 | 3 |

|kiwi-ix1.lime-kiwi-10GB.core.monkeybrains .net - 0 | 372 | 372 | 2 | 7 | 50 | 3 |

| as57976.sfmix .org - 0 | 372 | 372 | 4 | 9 | 72 | 7 |

| ae1-br01-eqsv5.as57976 .net - 22 | 201 | 158 | 4 | 12 | 116 | 9 |

| xe-0-0-1-1-br02-eqla1.as57976 .net - 1 | 359 | 357 | 14 | 53 | 3959 | 25 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

16

Join this conversation: Wave Broadband California Packet Loss - Nov 22 2018 - #108 by DamnVoices-1262

17

Posting on here because I’ve been dealing with this issue for weeks now. My ping would spike up toward 50-70 in random intervals and my ping on Speedtest was at a 9. I ran a WinMTR test, but it’s telling me that I can’t post any links on this forum. The said links are a part of the test results which of course I want to give all the information I’m receiving.