Connection issues "somewhere"

I don't see anything abnormal about the tracert. Were they taken with the game running and while the problem is occurring? By looking at;

9 27 ms 26 ms 27 ms cr2.la2ca.ip.att.net [12.122.129.106]

Your hitting Blizzard's network in 27ms. Thats pretty good for going from Las Vegas to CA(speculating). If your seeing your latency higher then that, then it's occurring inside their network. Are you having any overall problems with your internet connection?

Also, did you start having this problem around the time of a patch? Maybe around 8/10 to 8/12? It almost seems like several weeks ago Blizzard released a patch that allowed the blending or overlay of players from different servers, and something went wrong. Some people have had luck uninstalling and reinstalling the battle.net launcher. See here for more info.

Health Edge;

Thank you very much for looking at the info!  Yes, I have been having overall problems with my connection but it will ALWAYS pop up when I jump on WoW.  When I log on, it jumps all the way to around 10k ms (world) and then gradually works it's way down to a very manageable 64 ms, or so.  I will include a link of some of the comments I had received from Tech Support at Blizzard -->http://us.battle.net/wow/en/forum/topic/18704972820

I ran the test at PC boot up and ran WoW; was having many problems the entire time the test was running so the tests showing all is well is very odd to me.  Blizzard says it's Cox and/or Level3.net (whatever they are).  Still stumped...

JRich74 said:
Yes, I have been having overall problems with my connection

What other kind of problems? It would help to understand the scope of the situation.

JRich74 said:
When I log on, it jumps all the way to around 10k ms (world) and then gradually works it's way down to a very manageable 64 ms, or so.

This alone tells me it's something wrong with the client or launcher. Do you see your latency change that much while launching the game? If not, then the latency is either occurring in their network, or is a false negative. Do you actually experience lag or do you just see the counter go up? Do you get disconnects?

JRich74 said:
I will include a link of some of the comments I had received from Tech Support at Blizzard --

 

"You would need to get the problem escalated to a tier 3 support person so they can open a ticket with level 3 . The first response you will most likely get from your ISP is that its out of their network and not their issue. How its suppose to work is since level 3 is their peering partner they open a ticket with them to fix any issues."

Yea, no. I wonder how many people he has sent to their ISP to talk with their "Tier 3" and it has actually lead to the problem getting fixed. I have posted on your thread with my thoughts and opinions on his "conclusion". 

Health Edge said:
What other kind of problems? It would help to understand the scope of the situation.

During the day when my wife is on-line, she says occasionally it will just try and open a specific website and it will just load and load and not actually bring up the website.  Happens a few times through-out the day but since I am not really here to see it or gauge how bad it really is, I cannot say for sure how bad those issues are.

Health Edge said:
Do you see your latency change that much while launching the game? If not, then the latency is either occurring in their network, or is a false negative. Do you actually experience lag or do you just see the counter go up? Do you get disconnects?

10 times out of 10, it will start up at zero MS, takes a minute to start, and then BOOM - it goes up to between 8k and 10k ms or so, and then winds it's way down.  And you are correct, it normally happens when I gt from one area or the other.  And yes, I experience a TON of lag, people running in place, I can move but not do anything, etc.  It will go from perfectly fine to a dead stop then everything will just "catch up" in a blur of motion; almost like it had stabalized itself.  Then a few minutes later, does it again.

Just 30 minutes ago, I was in a raid.  1/2 way through a boss, it happened, but it never caught up, it D/C'd me.  Logged back in after a few and the exact same thing happened.

This time I set my laptop next to me and logged into a seperate instance of WoW and had Netflix running a random movie just to test.  When I lagged out and DC'd, my laptop WoW instance was fine, but ms started climbing slowly.  Netflix never had a hitch.

I am going to take your advice and uninstall WoW and the launcher and remove any associated folders.  Will re-install and let you know what happens.

JRich74 said:
 Happens a few times through-out the day but since I am not really here to see it or gauge how bad it really is, I cannot say for sure how bad those issues are.

It may help to download and install Pingplotter or some other latency tester. That way you can let it run while your away and use time stamps to compare reported problems with data. A easier version of this would be to let "ping -t <IP>" run in a command prompt while your gone. It won't record the entire day, since a command prompt only holds so much on a screen at once, but it will atleast tell you if packet loss or latency occurred at all.

JRich74 said:
it will start up at zero MS, takes a minute to start, and then BOOM - it goes up to between 8k and 10k ms or so, and then winds it's way down.

Sounds like the latency tool is taking a while to start and test, and when it does, it's measuring latency as the game downloads data off the server for the environment and things in the environment. Do you notice lag when there is other increase in activity, like a big battle? Or is it just when entering and exit? If so, this really sounds like the multiplayer system that connects you to other players. Is there a way to go to a area with few to no players? Does the problem happen there?

JRich74 said:
Just 30 minutes ago, I was in a raid.  1/2 way through a boss, it happened, but it never caught up, it D/C'd me.  Logged back in after a few and the exact same thing happened.

Did it happen while moving area in the raid? Or was the boss standing in one place? Was there any increase of people joining the raid? Do you know if others in the raid experienced latency? These are the kind of questions their technical support should be asking, and they are not. They are looking for problems in your connection, so thats why they are seeing them. They won't find other problems if they aren't bothering to look.

JRich74 said:
This time I set my laptop next to me and logged into a seperate instance of WoW and had Netflix running a random movie just to test.  When I lagged out and DC'd, my laptop WoW instance was fine, but ms started climbing slowly.

Smart troubleshooting. Not sure what the data means though. Where the two characters on the same server? Same area? Forgive me if this isn't even possible. Haven't played WoW for like a decade. 

JRich74 said:
Netflix never had a hitch.

Well then that rules a general internet problem, atleast with the download. Netflix doesn't use much upload though, so it's not conclusive. A better test would be to run Pingplotter or a basic ping to their server while playing. If the game client ping goes up, but does not change in CMD, then that tells you alot about the problem.

JRich74 said:
I am going to take your advice and uninstall WoW and the launcher and remove any associated folders.  Will re-install and let you know what happens.

Yea, looking at the new data I can't say for sure thats the issue, but since it worked for others, it can't hurt. Just be sure to backup anything you need. Specially if you have mods or add-ons.

And PS, to give you a idea of how your WoW technical support person function, take a look at this post. Notice he is more concerned with moderating posts then the fact that their is a pretty obvious trend. Hopefully he turns around now that there is someone who won't put up with his BS.

Health Edge said:
It may help to download and install Pingplotter or some other latency tester.

Will certainly do.  I will set it up and have it running on two PC's most of tomorrow, mine and my wife's.  I can ask her to periodically do some "work" stuff and I will jump on WoW from time to time and see what happens.

Health Edge said:
Do you notice lag when there is other increase in activity, like a big battle? Or is it just when entering and exit? If so, this really sounds like the multiplayer system that connects you to other players. Is there a way to go to a area with few to no players? Does the problem happen there?

Actually, no, it does not matter if people come or go. Nor does it matter if there is a lot of boss movement or player movement, it's completely random.  Here is a for instance in regards to your last question.  I ran to kill an old raid boss for a mount today, I was all alone.  Zoned in and all was fine but about 45 seconds into running to the boss area, it lagged up and jumped to around 4k ms.  No rhyme or reason and as I said, the instance was empty except for me and I hadn't even started any events yet.

Health Edge said:
Did it happen while moving area in the raid? Or was the boss standing in one place? Was there any increase of people joining the raid? Do you know if others in the raid experienced latency?

This raid boss was similar to many others, a lot of movement and things.  The boss was around 45% health and I had been running "ok" up until that point (a bit laggy but it was more graphical lag).  Then it spiked and shot WAY up, like 25k ms up, and I got DC'd.  Finally was able to log back in and within 10 seconds, it happened a second time.

Health Edge said:
Where the two characters on the same server? Same area?

I have two accounts on two PC's.  I renewed my second old account just for testing sake.  That character was in a totally seperate area with not many other players.  Same server.

Health Edge said:
A better test would be to run Pingplotter or a basic ping to their server while playing. If the game client ping goes up, but does not change in CMD, then that tells you alot about the problem.

Right now I am downloading and re-installing WoW from scratch without any add-on's or anything, all vanilla.  I will fire that up once it's complete and I have Pingblotter running and give you the results.

Health Edge said:
And PS, to give you a idea of how your WoW technical support person function, take a look at this post. Notice he is more concerned with moderating posts then the fact that their is a pretty obvious trend. Hopefully he turns around now that there is someone who won't put up with his BS.

I was going to do exactly what they suggested and call Cox and ask to "Escalate a ticket to level 3" but since I had no clue what that even meant and I wanted to somewhat educate myself, I came here instead.  I have learned so much about the internet these last couple of weeks!  I can also give the guys on the Blizzard forums a bit of a pass since most of the questions they get are the "stuff don't work" variety.  That being said, they certainly do need to be called out giving bad or uneducated guesses answers.

Thanks a million, Health Edge!

JRich74 said:
I have two accounts on two PC's.  I renewed my second old account just for testing sake.  That character was in a totally seperate area with not many other players.  Same server.

Seperate area, same server. For the moment, lets assume the server is in the same geographical location, because if they have things virtualized then that's going to make it alot harder to troubleshoot. That means at the same time, one computer on your network had severe problems connecting to that server while another computer did not. That tells me it's unlikly to be a Cox issue, since both computers are using Cox. Also rules out the server in general was having problems. However you did say her latency started to climb, so the data isn't absolute. Pingplotter will probably tell more of the story since then you will be able to see your exact route and latency when the problem is occuring. The main reason I disagree with WoW's technical person's opinions is why would a 10-15ms problem cause the game to lag 25,000ms+? Also, 25,000 is 25 seconds, right? Did you lag for 25 seconds? Something doesn't add up. Could be I don't understand what the ingame latency tool is reporting.

JRich74 said:
That being said, they certainly do need to be called out giving bad or uneducated guesses answers.

And If I turn out to be the one giving out bad advice then I will be sure to post on your thread and eat crow. I am man enough to admit when I am wrong. It's quite possibly we both mean well, we just have different perspective of the problems. Feel kind of bad in retrospect. I thought he was a moderator, but now I see he is just a user like us trying to help out. Guess it will come down to what fixes the problem. Good luck and keep in touch.

I ran PingPlotter for a couple of hours before bed.  Jumped on WoW and did all kinds of different things trying to trigger my connection issues.  Even with a clean install and no add-on's, I still had issues.  Still, there was not one thing in particular that triggers it.  It can happen standing still, so strange.  Most of the time it was at a steady 61 ms world and home, but towards the end of my test, it jumped up to 1500 ms and slowly worked it's way back down.  My PingPlotter results are as follows.  Is this the information we need from it, or is there something else I should provide?

Target Name: N/A
IP: 12.129.222.10
Date/Time: 8/29/2015 10:43:38 PM to 8/29/2015 11:52:55 PM

Hop Sent Err PL% Min Max Avg Host Name /
1 1664 0 0.0 0 39 0 XXXXX [XXX]
2 1664 0 0.0 6 27 8 [10.75.128.1]
3 1664 0 0.0 7 25 9 [100.127.2.56]
4 1664 0 0.0 14 129 25 24-234-6-28.ptp.lvcm.net [24.234.6.28]
5 1664 0 0.0 7 105 13 ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
6 1664 1 0.1 14 94 18 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
7 1664 1 0.1 14 330 20 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
8 1664 0 0.0 22 48 26 [192.205.37.145]
9 1664 0 0.0 23 73 26 cr2.la2ca.ip.att.net [12.122.129.106]
10 1664 0 0.0 17 60 19 [12.123.249.77]
11 1663 1663 100.0 0 0 0 [-]
12 1663 1663 100.0 0 0 0 [-]
13 1663 1663 100.0 0 0 0 [-]
14 1663 1663 100.0 0 0 0 [-]
15 1663 1663 100.0 0 0 0 [-]
16 1663 1663 100.0 0 0 0 [-]
17 1663 1663 100.0 0 0 0 [-]
18 1663 1663 100.0 0 0 0 [-]
19 1663 1663 100.0 0 0 0 [-]
20 1663 1663 100.0 0 0 0 [-]
21 1663 1663 100.0 0 0 0 [-]
22 1663 1663 100.0 0 0 0 [-]
23 1663 1663 100.0 0 0 0 [-]
24 1663 1663 100.0 0 0 0 [-]
25 1663 1663 100.0 0 0 0 [-]
26 1663 1663 100.0 0 0 0 [-]
27 1663 1663 100.0 0 0 0 [-]
28 1663 1663 100.0 0 0 0 [-]
29 1663 1663 100.0 0 0 0 [-]
30 1663 1663 100.0 0 0 0 [-]
31 1663 1663 100.0 0 0 0 [-]
32 1663 1663 100.0 0 0 0 [-]
33 1663 1663 100.0 0 0 0 [-]
34 1663 1663 100.0 0 0 0 [-]
35 1663 1663 100.0 0 0 0 [-]

Destination not reached in 35 hops

I also did Blizzards Looking Glass thing which provided this information:

PING 98.167.112.39 (98.167.112.39) 56(84) bytes of data.


traceroute to 98.167.112.39 (98.167.112.39), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.720 ms  0.753 ms  0.858 ms
 2  * * *
 3  12.129.244.189 (12.129.244.189)  0.330 ms * *
 4  206.16.68.49 (206.16.68.49)  0.392 ms  0.421 ms  0.504 ms
 5  12.122.251.185 (12.122.251.185)  10.600 ms  10.616 ms  10.619 ms
 6  cr2.la2ca.ip.att.net (12.123.132.210)  3.529 ms  3.199 ms  3.112 ms
 7  ggr2.la2ca.ip.att.net (12.122.129.105)  5.078 ms  5.072 ms  3.851 ms
 8  192.205.37.146 (192.205.37.146)  2.340 ms  2.358 ms  2.496 ms
 9  ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79)  6.059 ms  6.066 ms  6.072 ms
10  ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79)  6.064 ms  6.024 ms  6.013 ms
11  COX-COMMUNI.edge2.LosAngeles9.Level3.net (4.53.230.70)  20.299 ms  19.871 ms  26.703 ms
12  nwstdsrj01-ae1.0.rd.lv.cox.net (68.1.0.85)  14.985 ms  14.678 ms  14.669 ms

HOST: Blizzard              Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard               0.0%    10    0.6   0.6   0.4   0.8   0.1
  2. ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 12.129.244.189                            0.0%    10    0.3   0.4   0.3   0.5   0.1
  4. 206.16.68.49                              0.0%    10    0.4  35.2   0.3 190.0  63.8
  5. 12.122.251.185                            0.0%    10    1.1   6.4   1.1  38.2  11.8
  6. cr2.la2ca.ip.att.net                      0.0%    10    3.7   3.0   1.5   4.6   1.1
  7. ggr2.la2ca.ip.att.net                     0.0%    10    2.0   3.2   1.5   5.3   1.3

Ok, I managed to get some times and issues this morning.  Been running PingPlotter all morning and keeping a close eye on several devices running internet programs and WoW on my primary PC.

This was at 8:41 AM (all times PST)  Everything was running ok up until this point.  Got the familiar lag with people running in place and nothing responding.  It eventually caught up but lag was noticeable.  At the same time, other devices were showing signs of connection issues.  Downloading a file on PC for testing and my D/L dropped considerably.  Other devices showing similar issues.

This was at 8:50 AM.  Was in a raid for testing and were boss battling.  About 1 minute in (or 8% health) this happened.  After a few seconds, I was D/C'd.

This was at 8:53 AM.  I was able to log back in and things were "better".  Not great, but I was able to do things in game.

My other devices have begun to show signs of a stronger connection as well.

8:56 AM - things have settled down.  Other devices definately showing much better connectivity.

9:00 AM.  Things have all calmed down, gone back to perfect connections on all devices.

9:28 AM - End of raid in game, things have been smooth sailing from my DC until now.

9:37 AM.  Sitting still in an empty area and it happens again.  Again, showing slowdown and connectivity issues on other devices.

9:42 AM.  Still at it and other devices still showing slowdown.

10:10 AM - All is well and other devices showing considerable improvements.

**Now, when I am talking about my other devices:  I have a separate PC downloading a 10 gig file and normal D/L speed is around 1MB /sec.  When my WoW connectivity had "bad" issues, I had a hawk eye on my other PC.  It went from 1 MB /sec to around 40kb /sec.  When I was having moderate issues, it was around 450kb /sec.  With that last picture I posted, my file was back to 1MB /sec.

**Also note, I have had PingPlotter running the entire time so if there is any data that would be beneficial from that, I will be happy to post it as well!  

JRich74,

The best way to determine where the issues are when playing the game is to run a trace route to the game server IP (if you have it).  This will let us know where the slow down happens.  It would also be good to run a trace route to 2 different websites to compare those results as well.  Are these wired or wireless connections?  Have you tried a direct connection using ethernet?

Just to add my perspective:

If I look at who owns 12.129.193.253 and 192.205.37.146, it is AT&T. I can't ping anything in their network, but 12.129.193.253 shows as the worst of the MTR test, but things don't really fall apart until AT&T hands things over to Level 3.

This one is a tough call as to who owns the issue. Yes, pings can be deprioritized, which is what I was trying to tell the League of Legends folks, but this one is very distinct as to where it goes off the rails.

In my opinion, Blizzard needs to contact AT&T.  Now, I suppose Blizzard could in turn say that Cox should be the one to call Level 3, who would then need to contact AT&T.

At any rate, from just this quick look, it certainly seems like AT&T and/or Level 3 are who will need to work it out, but who makes the first call? I don't know...

traceroute to x (x), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.999 ms  1.068 ms  1.223 ms
 2  * * *
 3  12.129.199.181 (12.129.199.181)  0.351 ms * *
 4  12.129.193.253 (12.129.193.253)  9.767 ms  10.061 ms  10.238 ms
 5  cr1.la2ca.ip.att.net (12.122.128.182)  4.004 ms cr2.la2ca.ip.att.net (12.122.129.242)  2.995 ms cr1.la2ca.ip.att.net (12.122.128.182)  4.014 ms
 6  cr2.la2ca.ip.att.net (12.122.129.242)  3.005 ms cr1.la2ca.ip.att.net (12.122.128.182)  3.653 ms cr2.la2ca.ip.att.net (12.122.129.242)  5.193 ms
 7  ggr2.la2ca.ip.att.net (12.122.129.105)  4.410 ms  4.417 ms ggr2.la2ca.ip.att.net (12.122.128.101)  3.404 ms
 8  192.205.37.146 (192.205.37.146)  14.382 ms  13.399 ms  13.477 ms
 9  ae-2-70.edge2.Washington4.Level3.net (4.69.149.80)  82.912 ms  80.677 ms  80.668 ms
10  ae-2-70.edge2.Washington4.Level3.net (4.69.149.80)  80.540 ms  79.999 ms  77.280 ms
11  COX-COMMUNI.edge2.Washington4.Level3.net (4.53.115.134)  70.854 ms  70.887 ms  70.913 ms
12  rnkehdrj01-ae3.0.rd.rn.cox.net (68.1.0.219)  81.600 ms  81.605 ms  81.634 ms
13  98.172.172.201 (98.172.172.201)  79.639 ms  79.644 ms  79.633 ms
14  * * *
15  * * *

HOST: Blizzard              Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard               0.0%    10    0.4   0.6   0.3   1.2   0.3
  2. ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 12.129.199.181                            0.0%    10    0.4   0.4   0.3   0.5   0.1
  4. 12.129.193.253                            0.0%    10    0.3   4.9   0.3  45.5  14.3
  5. cr1.la2ca.ip.att.net                      0.0%    10    1.9   3.0   1.3   4.7   1.3
  6. cr1.la2ca.ip.att.net                      0.0%    10    3.4   3.5   1.8   5.4   1.1
  7. ggr2.la2ca.ip.att.net                     0.0%    10    3.9   3.9   2.0   5.2   1.1

DerrickW said:
run a trace route to the game server IP (if you have it).

Derrick, every trace I have run was directly to the Blizzard game server.  You can go back to my original post and see that the same IP below is the same one I ran my trace tests on.

 

DerrickW said:
 It would also be good to run a trace route to 2 different websites to compare those results as well.  Are these wired or wireless connections?  Have you tried a direct connection using ethernet?

Ok, I will run a test to a different website.  Will use Google for my next test.

The are both WIRED connections.  Hard wired directly to my router.

Direct connection straight from my modem to my PC?  Yes, I have tried that, same results. 

Going from my side to them:

Tracing route to us.battle.net [24.105.29.40] over a maximum of 30 hops:

  1     4 ms     7 ms     2 ms  192.168.1.1
  2    14 ms    19 ms    19 ms  10.64.80.1
  3    15 ms    18 ms    18 ms  98.172.172.202
  4    18 ms    22 ms    31 ms  ashbbprj01-ae3.0.rd.as.cox.net [68.1.0.214]
  5    24 ms    29 ms    29 ms  xe-10-0-1.edge2.Washington4.Level3.net [4.53.115
.133]
  6     *        *        *     Request timed out.
  7    28 ms    24 ms    28 ms  att-level3-te.washingtondc12.Level3.net [4.68.62
.30]
  8    94 ms    89 ms    99 ms  cr2.wswdc.ip.att.net [12.122.134.186]
  9    96 ms    96 ms    99 ms  cr1.cgcil.ip.att.net [12.122.18.21]
 10    94 ms    98 ms   168 ms  cr2.dvmco.ip.att.net [12.122.31.85]
 11    92 ms    91 ms    98 ms  12.122.28.46
 12   104 ms    98 ms    98 ms  cr1.la2ca.ip.att.net [12.122.30.30]
 13    94 ms    98 ms    88 ms  gar20.la2ca.ip.att.net [12.122.128.181]
 14    95 ms    98 ms    99 ms  12-122-254-238.attens.net [12.122.254.238]
 15    94 ms    95 ms    92 ms  206.16.68.46
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19  ^C

Hop 6 can be ignored.  There's something not responding to pings there.

Hop 7 still with Level3.

Hop 8 is AT&T.

I'd need to come back to this in the morning perhaps and see if this is better.

 

BrianS said:
but things don't really fall apart until AT&T hands things over to Level 3.

Brian, thank you for looking at this, as well!  I am really getting frustrated with this whole situation and not sure where else to go.

Anyway, Sunday, 8/30, I ran my PingPlotter almost all day long.  It ran the entire time while I was making my most recent post where I had time stamps of the WarCraft game menu showing my latency.  This information is below.  Unfortunately, I am not 100% sure on how to read this information I am providing.  Here is my data from most of the day yesterday:

Target Name: N/A
IP: 12.129.222.10
Date/Time: 8/30/2015 6:47:33 AM to 8/30/2015 9:02:27 PM

Hop Sent Err PL% Min Max Avg Host Name /
1 15935 2 0.0 0 360 0 XXXXXXX [XXXXXXX]
2 15935 4 0.0 6 116 9 [10.75.128.1]
3 15935 4 0.0 6 120 10 [100.127.2.56]
4 15935 2 0.0 7 747 23 24-234-6-28.ptp.lvcm.net [24.234.6.28]
5 15935 6 0.0 7 233 13 ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
6 15935 9 0.1 13 185 18 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
7 15935 5 0.0 13 147 18 ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
8 15935 3 0.0 22 152 27 [192.205.37.145]
9 15935 4 0.0 23 87 27 cr2.la2ca.ip.att.net [12.122.129.106]
10 15935 3 0.0 17 1104 20 [12.123.249.77]
11 15934 15934 100.0 0 0 0 [-]
12 15934 15934 100.0 0 0 0 [-]
13 15934 15934 100.0 0 0 0 [-]
14 15934 15934 100.0 0 0 0 [-]
15 15934 15934 100.0 0 0 0 [-]
16 15934 15934 100.0 0 0 0 [-]
17 15934 15934 100.0 0 0 0 [-]
18 15934 15934 100.0 0 0 0 [-]
19 15934 15934 100.0 0 0 0 [-]
20 15934 15934 100.0 0 0 0 [-]
21 15934 15934 100.0 0 0 0 [-]
22 15934 15934 100.0 0 0 0 [-]
23 15934 15934 100.0 0 0 0 [-]
24 15934 15934 100.0 0 0 0 [-]
25 15934 15934 100.0 0 0 0 [-]
26 15934 15934 100.0 0 0 0 [-]
27 15934 15934 100.0 0 0 0 [-]
28 15934 15934 100.0 0 0 0 [-]
29 15934 15934 100.0 0 0 0 [-]
30 15934 15934 100.0 0 0 0 [-]
31 15934 15934 100.0 0 0 0 [-]
32 15934 15934 100.0 0 0 0 [-]
33 15934 15934 100.0 0 0 0 [-]
34 15934 15934 100.0 0 0 0 [-]
35 15934 15934 100.0 0 0 0 [-]

Destination not reached in 35 hops

-or-

If there is any details from this data that might help and that I could provide, please let me know.

I am looking for just about anything at this point!

:)

That is now suggesting a possible congestion problem with Level3.  Need to recheck at a different time of day.

Tracing route to ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102] over a maximum of 30 hops:

  1     7 ms     6 ms     2 ms  192.168.1.1
  2    17 ms    21 ms    19 ms  10.64.80.1
  3    18 ms    18 ms    18 ms  98.172.172.200
  4    26 ms    28 ms    28 ms  ashbbprj01-ae5.0.rd.as.cox.net [68.1.0.252]
  5    26 ms    28 ms    28 ms  xe-11-1-2.edge2.Washington4.Level3.net [4.53.115
.117]
  6    25 ms    28 ms    38 ms  vlan70.csw2.Washington1.Level3.net [4.69.149.126
]
  7    35 ms    29 ms    31 ms  ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
33]
  8    94 ms   100 ms    98 ms  ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]

  9    96 ms    95 ms   100 ms  ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
 10    96 ms    99 ms    99 ms  ae-1-100.ebr1.Tustin1.Level3.net [4.69.153.217]

 11   103 ms    94 ms    86 ms  ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.10
2]

Trace complete.