6% Loss Out issues


#6

Howdy!

You could attempt to run a Pathping at the exact time the loss is occurring instead of a WinMTR.

We know the issue is packet loss but now we need to find it. The WinMTR is nice because it’s more like a movie of your connection over time via a snapshot of a Pathping. Either way if you can run a few pathpings when the issue is occurring and get them back here that may do the trick. You could also try a LookingGlass report. Make sure to run all the tests and post the full results back here.

Thank you.


#7

Thank you! Yes I would be more than happy to do that. I should have the test results sometime finished within the afternoon or early evening. I will begin logging.


Path ping tests

Path Ping test 1: Numbani . Widow player kept hitting me before I even seen them. Player was at CP 1. Top guard rails. Kill cam shows I was leaving Defenders spawn. Player position shows me peaking from the street and hitting me before I even saw them in Cross hairs.

Average observable loss: 3.3-4%

Tracing route to 24.105.62.129 over a maximum of 30 hops

0 DESKTOP-UBJ68GN.Home [192.168.254.64]
1 192.168.254.254
2 * * *
Computing statistics for 25 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-UBJ68GN.Home [192.168.254.64]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.254.254

Trace complete.

Test #2. Route 66.

Average observable loss: 4-7%

Average observable loss:

Tracing route to 24.105.62.129 over a maximum of 30 hops

0 DESKTOP-UBJ68GN.Home [192.168.254.64]
1 192.168.254.254
2 * * *
Computing statistics for 25 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-UBJ68GN.Home [192.168.254.64]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.254.254

Trace complete.

Test #3

Numbani Defense

Average observable loss: 3.3-5%

Tracing route to 24.105.62.129 over a maximum of 30 hops

0 DESKTOP-UBJ68GN.Home [192.168.254.64]
1 192.168.254.254
2 * * *
Computing statistics for 25 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-UBJ68GN.Home [192.168.254.64]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.254.254

Trace complete.


Traceroute:

TRACEROUTE:
traceroute to 71.29.215.37 (71.29.215.37), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.100 ms 1.058 ms 1.052 ms Blizzard(24.105.18.3) 4.793 ms 4.884 ms 5.135 ms
3 137.221.105.16 (137.221.105.16) 1.067 ms 1.066 ms 1.165 ms
4 137.221.66.22 (137.221.66.22) 1.036 ms 1.035 ms 1.034 ms
5 137.221.83.68 (137.221.83.68) 13.347 ms 13.347 ms 13.346 ms
6 137.221.65.68 (137.221.65.68) 17.053 ms 14.341 ms 14.270 ms
7 137.221.65.1 (137.221.65.1) 12.776 ms 12.762 ms 12.996 ms
8 137.221.65.7 (137.221.65.7) 12.995 ms 12.985 ms 12.979 ms
9 137.221.70.32 (137.221.70.32) 12.584 ms 13.107 ms 13.090 ms
10 eqix-sv1.windstream. com (206.223.116.213) 12.436 ms 12.430 ms 12.412 ms
11 ae3-0.cr02.snju01-ca.us.windstream. net (40.138.83.80) 12.401 ms 12.426 ms 12.515 ms
12 ae2-0.cr01.dnvt01-co.us.windstream. net (40.136.117.135) 42.167 ms 42.157 ms 42.151 ms
13 et3-0-0-0.cr02.dnvt01-co.us.windstream. net (40.128.249.169) 42.124 ms 42.129 ms 42.260 ms
14 ae7-0.agr02.lncl01-ne.us.windstream. net (40.138.83.61) 50.371 ms 50.364 ms 51.075 ms
15 * * *


Blizzard Looking Glass. (Idle no gameplay)
MTR:
Start: Fri Feb 22 21:10:49 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 1.7 0.5 11.1 3.3
3.|-- 137.221.105.12 0.0% 10 0.8 0.6 0.5 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.8 0.7 0.5 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 12.9 13.4 12.7 18.0 1.5
6.|-- 137.221.65.68 0.0% 10 12.8 38.2 12.7 115.5 35.6
7.|-- 137.221.65.1 0.0% 10 12.8 20.7 12.7 59.1 15.3
8.|-- 137.221.65.7 0.0% 10 12.7 14.5 12.7 28.5 4.9
9.|-- 137.221.70.32 0.0% 10 12.7 12.6 12.6 12.7 0.0
10.|-- eqix-sv1.windstream. com 0.0% 10 12.5 12.6 12.4 13.3 0.0
11.|-- h80.83.138.40.static.ip.windstream.n et 0.0% 10 12.7 12.6 12.5 12.8 0.0
12.|-- ae2-0.cr01.dnvt01-co.us.windstream. net 0.0% 10 42.4 44.7 42.0 66.7 7.7
13.|-- et3-0-0-0.cr02.dnvt01-co.us.windstream. net 0.0% 10 42.3 42.3 42.1 42.6 0.0
14.|-- ae7-0.agr02.lncl01-ne.us.windstream. net 0.0% 10 50.8 50.6 50.5 50.8 0.0
15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 90.0% 10 13391 13391 13391 13391 0.0
16.|-- h37.215.29.71.dynamic.ip.windstream. net 10.0% 10 60.5 60.3 60.0 60.6 0.0

22/02/2019 21:10:49 UTC


Game in Progress results.

MTR:
Start: Fri Feb 22 21:14:53 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 1.1 0.5 4.8 1.2
3.|-- 137.221.105.12 0.0% 10 0.7 0.6 0.5 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.9 0.7 0.6 1.2 0.0
5.|-- 137.221.83.68 0.0% 10 12.9 13.8 12.8 21.7 2.7
6.|-- 137.221.65.68 0.0% 10 12.9 15.2 12.8 31.8 6.0
7.|-- 137.221.65.1 0.0% 10 13.0 14.5 12.8 29.4 5.2
8.|-- 137.221.65.7 0.0% 10 13.0 16.4 12.7 45.9 10.4
9.|-- 137.221.70.32 0.0% 10 12.6 12.7 12.5 12.8 0.0
10.|-- eqix-sv1.windstream. com 0.0% 10 13.0 12.7 12.4 13.5 0.0
11.|-- ae3-0.cr02.snju01-ca.us.windstream. net 0.0% 10 12.7 12.6 12.5 12.7 0.0
12.|-- ae2-0.cr01.dnvt01-co.us.windstream. net 0.0% 10 42.3 42.2 42.1 42.3 0.0
13.|-- et3-0-0-0.cr02.dnvt01-co.us.windstream. net 0.0% 10 42.4 42.3 42.2 42.4 0.0
14.|-- ae7-0.agr02.lncl01-ne.us.windstream. net 0.0% 10 86.0 54.5 50.5 86.0 11.1
15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 80.0% 10 12713 12706 12698 12713 10.0
16.|-- h37.215.29.71.dynamic.ip.windstream. net 0.0% 10 60.4 60.2 59.7 60.7 0.0

22/02/2019 21:14:53 UTC


Ping Test.

PING:
PING 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=52 time=60.8 ms
64 bytes from: icmp_seq=2 ttl=52 time=60.8 ms
64 bytes from : icmp_seq=3 ttl=52 time=60.5 ms
64 bytes from icmp_seq=4 ttl=52 time=60.4 ms

— ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 60.479/60.676/60.844/0.290 ms


Okay. I guess that pretty much sums up what I can do on my end here. For me, when it is Hitscan vs hitscan fights. And even fast moving targets. I take the shot and it becomes a “non register” shot.I always lose because they are seeing me, before I can see them. I can watch my screen and observe that I am FULLY exposed to them, before They are exposed to me, on my screen.

Thank you very much! :slight_smile:


#8

Oh hey again, Dasaries.

None of that data was usable, unfortunately. It appears that your modem or whatever’s after it is blocking ICMP echo requests which makes the pathping useless in this regard. You can try the winMTRNet clone instead if you’d like but I would wager anything on the winMTR website is a false positive.

Is the packet loss coming and going, or has it been pretty consistent these last few months?


#9

HI again Drakuloth! Happy to hear you are here!

I guess I am still hanging around the forums. . First troubleshooting FPS loss. and then now the Packet loss. Trouble always follows me wherever I go. LOL . I have a lot to say so I’d suggest free time and some coffee or a beverage of your choosing :slight_smile: … And so it begins… again!

Well Yes, I am racking up the leaver penalties in conjunction with the troubleshooting. Maybe someday answers will be here…

Packet issues:. January’s Patch day for the new content gave me this incredible issue with Packet loss from the game’s End. Prior to that date. I probably saw about 0.5%-1% from November, but nothing too bad. Then January came and RIGHT on patch day the game never ran good again. I reinstalled the game, wiped the game from the registry TWICE and I still see the same issue here.

The Winmtr download: What I caught was a file that was initiated at that exact time stamp when the download occurred. Where a Trojan was being saved to the desktop. It was actually a hidden file located on the desktop during the exact time of the download. So it wasn’t “there” but it was “there”. during that download. I mean it could have been a MITM attack at that point in time. My antivirus software showed it was a payload that piggybacked onto the download But I might try it again tomorrow. Today it actually shows the website is down. when going to the official website. So i will see what happens tomorrow and try again :slight_smile:


The long answer…

So here is what I did…

I had the ISP come out to the NID box and swap the DSL POT out and put a new one in. They came out with a new router and even had me try their new router/modem. Same thing. I have really good connection from other games from this point on in and then Overwatch just seams to not like how the Network operates. I’ve got NO other devices on the network. No wireless. Just 12’ of Cat 6 from this computer to the Modem, and when my ISP came out we worked together to run 6’ of telcom wire right into the NID. Yes, I put a hole through my wall with the hammer drill and we pulled exactly 6’ of telcom wire from the NID.

Now to me, I know that we were out there with the hardsided network equipment testing stuff, at the box by the street. That run is about 125’ to the lug terminal box from the NID to the street and their cable itself is ALL buried out this way. Then, Before it hits a repeater station and then goes out to the highway’s fiber run. The old military base out here has buried cables and they leased it to the ISP. So phone poles and weather are NOT a problem! :slight_smile: One of the telcom operators was nice enough to actually check it on his end and didn’t see anything out of the ordinary. I personally know a few people that worked there before decommissioning and the wire under the ground is no laughing matter. It’s VERY robust.

Hardware wise I did a swap to see if it was something on my end. I ordered in an ASRock Z370 SLI, swapped around the RTX2060 and the GTX1060, an i5 hex core cpu and even a pair of dominator platinum ram sticks. FPS issues never went away, packet loss was still there (infact slightly even WORSE) and I just decided at that point to sell everything off but the RAM and the GPU. So I made my money back. :slight_smile: I’d say the input lag was WORSE on the i5 hex cores

For the previous story and it’s outcome:

FPS wise: You know I never did get that fairly perfect. But even on the RTX 2060 and swapping a board with a NEW O.S., windows update, Processor RAM sticks and hardware swaps. Same issues. It wasn’t Until i switched this game into Windows 7 Compatibility mode. Much smoother. February’s Windows update at the start of the month BOGGED this machine down. So I pulled it, locked down windows and it went back to much better behavior. However, whatever it IS that is causing it. is outside of my training.


To me, I don’t like pressing the matter on Blizzard, but if a person NEVER knows what they tested this game on (hardware specs) and the exact environmental perimeters here. I could be troubleshooting endlessly and never see results. First thing that comes to my mind is maybe the BAUD rate is wrong here on my end. Who knows.

yes, I’d love to visit the studio myself and see what they test the games on (dont know what they are allowing or are not on the tours,) but I am not going to be in California this year to pull honeybee hives out of the almond orchards after pollination. Many professional keepers aren’t. Bakersfield was calling us left and right for pollination. and national loss on bees was 65% with the USDA even calling us and asking us what the deal is on bees. So I am kinda stuck here Freezing in the Midwest.


I guess that is pretty much where I am at :slight_smile:


#10

Heya Dasaries,

I vaguely remember you asking that question (re: specs of the machines) back in the day, but we’re not directly privy to that information. What I can tell you is that our QA team does it on a large number of different hardware configurations/combinations. We usually grab a few copies of new hardware too. (Our QA folks are always putting in tickets for new and old toys to test on. :D)

As long as your machine meets requirements and you’re running supported hardware, and there isn’t some kind of bug or hardware/software level issue, you shouldn’t see odd behavior from a performance perspective. That’s the point of the troubleshooting after all. We have been monitoring some reports of the 10x0/20x0 series cards (Mainly the RTX) experiencing Rendering Device Lost crashes lately. Currently we suspect it has something to do with NVidia profiling. More on that here. Maybe the work around here gives you some love with the FPS issues? Beyond that you mentioned basically building a whole new rig from scratch, so we’d be back to square one on that.

Let’s take this one thing at a time though. Right now you’ve got something a bit more easily measurable. Once you’ve got a winMTR which captures the issue, definitely post it so we can take a peek. If you can also get a screenshot of your netgraph when the loss is happening, upload it to imgur, and link it to us, we’ll give that a look too.


#11

Okay Everything is a “Green light” on this download and I have it up and ready to go.

Which address do you want me to examine and how much of a snapshot of this would you like me to take?

-Das


I should ask. Just OUT of curiosity. (which I strongly emphasize) Which hardware config are they finding keeps the game ABOVE 200fps at Medium-high settings. I mean I just put in this RTX 2060 and I think I have a processor or Monitor issue here TBH. Rialto is a stunning map to look at, but when combat is going on. I go from 220fps down to a 96FPS. I tried an i5 hex core on a Z370 board and that dipped hard, too.

Thank you!


#12

Regarding the winMTR - snag the IP address from the network graph in game where you’re having loss. (Ctrl+Shift+N to bring it up.) There’s more information on what to do with it in the WinMTR article itself.

As for the performance spec machines, again, we do not have that information. I am absolutely willing to help troubleshoot the connection issue, but as I have mentioned to you on multiple occasions including this one, we do not create ‘performance spec’ machine lists because we cannot guarantee performance due to a myriad of factors with individual hardware types and manufacturers. These days most hardware works together most of the time, but we’re not going to open the floodgates for “You said this would get a consistent 200 FPS” or something of that nature when it’s not really in our control. In general, our hardware requirements are not set for you to achieve anything above 60 fps most of the time.

Your system exceeds those requirements, and your hardware’s pretty good, but you’re getting over 60 FPS consistently. Anything beyond that is considered enthusiast, and is on you to optimize on your own time which you can use community help for if anybody’s got hints for you. I THINK I already linked you the guide Wyomingmist put together for it, but just in case, check it out if you haven’t yet. It’s good stuff. At this point I can’t address this in any more ways than I already have, so any further inquiries on this are probably going to go unresponded to so that we can focus on one thing at a time - that connection issue.


#13

Okay sounds good.

Which IP address would you like me to route to for the test? I know that it says I have to have a destination address to test for.

When I begin this test. What kind of data spread are you looking for. I can run this thing for x amount of hops or tests here. How many do you need me to run.

Now onto the other one. A big “thank you from me”. Sincerely I cannot believe I over-looked that setting.


…and yes. I will look at their link. I did not see that. Thank you!! :smiley:


Update: on the link suggestion.

I did take a look at that link to the Guide you sent me. I want to thank you again!!!

RANDOM FPS LOSS IS SOLVED!! Thank you :smiley: :smiley: :smiley: It is actually gone!!

I went in, read the guide. Copied it down. Changed the Nvidia scaling mode to aspect ratio and PhysX to the GPU ONLY OPTION. After that. No more frame crashing. Game runs very smooth now :slight_smile:


#14

Haha don’t thank me, thank Wyomingmist and the community, they’re the lovely folks who came up with the methods and put all that information together. Glad this is resolved finally, as I know you’ve had problems for a very long time with it. Also, thank you for letting us know exactly what step handled this! I’m going to keep an eye out for future reports.

Regarding the IP address for your test and how to run it, there is a network graph in game (Ctrl+Shift+N) - when you are having the problems, you’re going to open that and copy down the IP address in the top right. Information on how to edit this address is in the WinMTR guide I sent you earlier. Then, run the winMTR using this address for one game while you are having problems. If you post the results of that single test, we will scope it out.


#15

Good morning.

I did take a look at the test thing here. I should ask. Do i need the numbers after the " : " from the adress or not. It gives me an error message if I do.

If I put in the numbers before the " : " It wont even give me a reading. So I am wondering here how we should go about this.

Thank you!


#16

The will want to omit the colon and the numbers that come after that. That is going to be the port and the test will only require the the IP address.


#17

I just ran it again the following address ranges with No response from the servers.

24.105.46.224
24.105.44.188
24.105.30.129

WinMTR does NOT have a port number entry field on it.


#18

That is correct, there is no port field which is why we only need the IP address. With that said, if we’re only getting No response from the servers then this is likely an indication that the test is being blocked by security either on the computer or the router\modem. This is likely also why the previous pathping tests only showed up with 1 hop.

One thing we did notice with your previous looking glass results are these hops here:

15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 80.0% 10 12713 12706 12698 12713 10.0
15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 90.0% 10 13391 13391 13391 13391 0.0

Its likely that the packet loss here is just going to be shaping on those nodes however we are going to want to try to get something to compare and make sure. If you have a separate router\modem, then we’d like to try bypassing the router altogether and run the WinMTR while connected directly to the modem.

We can also try running a traceroute using the IPs you found and see if we can get any more info from that.


#19

How do you suggest we should go about this? The company I have out here. Comes out of a service office about 30 miles away and they did try this with me when they were out there. It was the same type of packet loss.

If it is on their end. Which it more than likely appears to be, with this information you have provided me. . What would you like me to ask of them to do for me?

Thank you! :slight_smile:


#20

If it turns out to be a routing issue going through those hops then it would be on the ISP to see if they’re able to advertise a different route for the connection or look into those hops specifically to see if there’s an issue that can be resolved.

As far as routing goes, the only way to really go about changing it yourself would be to either test with a VPN or with a different connection altogether. VPNs aren’t something we generally support and so if its something you wanted to try, you’d have to do the research on the options available. Many usually have a free trial (usually with a bandwidth limit) that would let you test for free. As far as a different connection goes, if you or someone you know has a phone and data plan that supports tethering, we could try the mobile connection and see if we notice any difference. Either of these steps could potentially help us narrow down the issue and determine if the problem is the routing.


#21

Around here. 3G, 4G doesn’t usually work since we are in an area that has no stable cell reception. In this area there is Government land and they did not allow towers or communications within X amount of feet from it. Which is also why I cannot do mobile authentication stuff. I haven’t ever done a VPN with this game I would not want to risk if one of these VPNs was dishonest and pulled a MITM attack on me.

I know that the ISP will re-route traffic if there is failures on hardware. I will see what I can do. to pull a new route table from them and maybe see here in the next 24-48 hours if I cannot try and get their system to do something different for me.

Thank you!

I will post later on this.!


#22

Sounds like a plan. We’ll be waiting for your update!


#23

Here is what I am seeing today from them. I am still having problems in this game with packet loss. What do you think we should be requesting they fix, based on all of this?

TRACEROUTE:
traceroute to (REDACTED), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.262 ms 0.249 ms 0.247 ms Blizzard(24.105.18.3) 0.612 ms 0.775 ms 0.877 ms
3 137.221.105.12 (137.221.105.12) 1.139 ms 1.152 ms 1.161 ms
4 137.221.66.20 (137.221.66.20) 1.136 ms 1.140 ms 1.139 ms
5 137.221.83.68 (137.221.83.68) 12.867 ms 12.877 ms 12.877 ms
6 137.221.65.68 (137.221.65.68) 12.741 ms 13.290 ms 13.263 ms
7 137.221.65.1 (137.221.65.1) 13.204 ms 12.805 ms 12.778 ms
8 137.221.65.7 (137.221.65.7) 12.766 ms 12.814 ms 12.793 ms
9 137.221.70.32 (137.221.70.32) 12.984 ms 12.988 ms 12.984 ms
10 eqix-sv1.windstream. com (206.223.116.213) 12.442 ms 12.365 ms 12.546 ms
11 h80.83.138.40.static.ip.windstream. net (40.138.83.80) 12.529 ms 12.482 ms 12.484 ms
12 ae2-0.cr01.dnvt01-co.us.windstream. net (40.136.117.135) 42.171 ms 42.178 ms 42.167 ms
13 et3-0-0-0.cr02.dnvt01-co.us.windstream. net (40.128.249.169) 42.271 ms 42.195 ms 42.181 ms
14 ae7-0.agr02.lncl01-ne.us.windstream. net (40.138.83.61) 50.556 ms 50.478 ms 50.482 ms
15 * * *

04/03/2019 05:57:50 UTC

TRACEROUTE:
traceroute to 98.16.152.91 (98.16.152.91), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.249 ms 0.255 ms 0.262 ms Blizzard(24.105.18.3) 1.467 ms 1.491 ms 1.499 ms
3 137.221.105.12 (137.221.105.12) 0.721 ms 0.794 ms 0.858 ms
4 137.221.66.20 (137.221.66.20) 0.500 ms 0.528 ms 0.590 ms
5 137.221.83.68 (137.221.83.68) 12.879 ms 12.901 ms 12.910 ms
6 137.221.65.68 (137.221.65.68) 12.757 ms 12.758 ms 12.750 ms
7 137.221.65.1 (137.221.65.1) 12.865 ms 12.882 ms 12.881 ms
8 137.221.65.7 (137.221.65.7) 13.223 ms 13.223 ms 13.204 ms
9 137.221.70.32 (137.221.70.32) 12.551 ms 12.667 ms 12.663 ms
10 eqix-sv1.windstream. com (206.223.116.213) 13.000 ms 12.415 ms 12.408 ms
11 h80.83.138.40.static.ip.windstream. net (40.138.83.80) 12.465 ms 12.498 ms 12.426 ms
12 ae2-0.cr01.dnvt01-co.us.windstream. net (40.136.117.135) 42.073 ms 42.120 ms 42.208 ms
13 et3-0-0-0.cr02.dnvt01-co.us.windstream. net (40.128.249.169) 42.305 ms 42.320 ms 42.323 ms
14 ae7-0.agr02.lncl01-ne.us.windstream. net (40.138.83.61) 50.754 ms 50.553 ms 50.552 ms
15 * * *

04/03/2019 05:57:50 UTC

PING:
PING 98.16.152.91 (98.16.152.91) 56(84) bytes of data.
64 bytes from 98.16.152.91: icmp_seq=1 ttl=52 time=59.7 ms
64 bytes from 98.16.152.91: icmp_seq=2 ttl=52 time=60.4 ms
64 bytes from 98.16.152.91: icmp_seq=3 ttl=52 time=60.0 ms
64 bytes from 98.16.152.91: icmp_seq=4 ttl=52 time=59.7 ms

— 98.16.152.91 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 59.740/60.008/60.454/0.282 ms

04/03/2019 05:57:50 UTC

PING:
PING 98.16.152.91 (98.16.152.91) 56(84) bytes of data.
64 bytes from 98.16.152.91: icmp_seq=1 ttl=52 time=60.6 ms
64 bytes from 98.16.152.91: icmp_seq=2 ttl=52 time=60.1 ms
64 bytes from 98.16.152.91: icmp_seq=3 ttl=52 time=60.1 ms
64 bytes from 98.16.152.91: icmp_seq=4 ttl=52 time=60.0 ms

— 98.16.152.91 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 60.079/60.264/60.668/0.340 ms

04/03/2019 05:57:52 UTC

MTR:
Start: Mon Mar 4 05:57:50 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.2 0.2 0.3 0.0 Blizzard 0.0% 10 0.5 1.1 0.5 6.3 1.7
3.|-- 137.221.105.12 0.0% 10 0.5 2.3 0.5 17.5 5.3
4.|-- 137.221.66.20 0.0% 10 0.8 1.0 0.5 2.8 0.5
5.|-- 137.221.83.68 0.0% 10 12.8 16.4 12.8 32.4 7.4
6.|-- 137.221.65.68 0.0% 10 12.7 13.4 12.7 17.9 1.6
7.|-- 137.221.65.1 0.0% 10 12.8 12.9 12.7 13.3 0.0
8.|-- 137.221.65.7 0.0% 10 12.7 13.8 12.7 19.1 2.2
9.|-- 137.221.70.32 0.0% 10 12.5 12.6 12.5 13.3 0.0
10.|-- eqix-sv1.windstream. com 0.0% 10 12.5 12.7 12.5 14.0 0.3
11.|-- h80.83.138.40.static.ip.windstream. net 0.0% 10 12.5 13.9 12.5 24.6 3.7
12.|-- ae2-0.cr01.dnvt01-co.us.windstream. net 0.0% 10 42.2 42.2 42.1 42.4 0.0
13.|-- et3-0-0-0.cr02.dnvt01-co.us.windstream. net 0.0% 10 42.2 42.3 42.1 43.2 0.0
14.|-- ae7-0.agr02.lncl01-ne.us.windstream. net 0.0% 10 50.7 50.6 50.4 51.1 0.0
15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 90.0% 10 13116 13116 13116 13116 0.0
16.|-- h91.152.16.98.static.ip.windstream. net 0.0% 10 60.2 60.2 59.8 60.3 0.0

04/03/2019 05:57:50 UTC

MTR:
Start: Mon Mar 4 05:57:50 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 1.4 0.8 0.5 1.4 0.0
3.|-- 137.221.105.12 0.0% 10 0.8 0.7 0.5 1.6 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 1.0 0.6 4.5 1.1
5.|-- 137.221.83.68 0.0% 10 12.7 15.1 12.6 28.2 5.1
6.|-- 137.221.65.68 0.0% 10 12.9 17.7 12.7 38.0 10.1
7.|-- 137.221.65.1 0.0% 10 12.9 14.6 12.7 28.4 4.9
8.|-- 137.221.65.7 0.0% 10 12.9 16.2 12.6 46.8 10.7
9.|-- 137.221.70.32 0.0% 10 12.7 13.1 12.6 16.2 1.1
10.|-- eqix-sv1.windstream. com 0.0% 10 12.6 14.5 12.5 30.3 5.5
11.|-- ae3-0.cr02.snju01-ca.us.windstream. net 0.0% 10 12.5 12.9 12.5 15.3 0.7
12.|-- ae2-0.cr01.dnvt01-co.us.windstream. net 0.0% 10 42.3 44.2 42.1 50.3 3.2
13.|-- et3-0-0-0.cr02.dnvt01-co.us.windstream . net 0.0% 10 42.3 42.3 42.1 42.5 0.0
14.|-- ae7-0.agr02.lncl01-ne.us.windstream. net 0.0% 10 50.6 50.6 50.4 50.8 0.0
15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 90.0% 10 13140 13140 13140 13140 0.0
16.|-- h91.152.16.98.static.ip.windstream. net 0.0% 10 60.4 60.4 59.9 61.6 0.3

04/03/2019 05:57:50 UTC



#24

There doesn’t look to be much in terms of a change. We’re still seeing the high latency and packet loss on hop 15 going through Windstream:

15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 90.0% 10 13116 13116 13116 13116 0.0
15.|-- port3-2-2.bng01.lncl01-ne.us.windstream. net 90.0% 10 13140 13140 13140 13140 0.0

As I had mentioned in my previous post, its possible this could just be due to something like ICMP filtering and so it could be a non-issue but without more info from the ISP its not something we can say for sure. That is the hop that we’d want them to look into specifically though.


#25

UPDATED.

Okay I did talk to my ISP. it is their end of the network having problems and they admit they are struggling with it. So that part of the ticket is solved.

Thank you very much for the help!

-Das