Maintenance for the week of September 8:
• PC/Mac: No maintenance – September 8
• PC/Mac: EU megaserver for maintenance – September 9, 22:00 UTC (6:00PM EDT) - September 10, 16:00 UTC (12:00PM EDT) https://forums.elderscrollsonline.com/en/discussion/682784
• PC/Mac: No maintenance – September 8
• PC/Mac: EU megaserver for maintenance – September 9, 22:00 UTC (6:00PM EDT) - September 10, 16:00 UTC (12:00PM EDT) https://forums.elderscrollsonline.com/en/discussion/682784
ESO Latency Spikes - Possible Cause
Zys7321
Soul Shriven
Like many others here (and many more who haven't posted) I too have been experiencing very bad pings while playing. With that being said there are also a lot of players who don't appear to be having an issue. Based on this scenario it sounded like it might be an issue with a networking hop to me. As a quick primer when you connect to something on the Internet your data packets pass through a number of network devices. Each time this occurs it is called a hop. The hops that your data packets go through are different depending on your location as well as other factors.
The first test I ran was to use an http ping (since regular pings are blocked) to launcher.bethesda.net to see if I could replicate the bad ping issue. As you can see below this did occur in a 4 packet ping:
Pinging "http://launcher.bethesda.net":
1> Reply: [200/OK] bytes=189 time=148ms
2> Reply: [200/OK] bytes=189 time=143ms
3> Reply: [200/OK] bytes=189 time=3160ms
4> Reply: [200/OK] bytes=189 time=3162ms
Ping statistics for "http://launcher.bethesda.net":
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 3162ms, Average = 1653ms
From there I used a network trace route program called WinMTR to perform a more verbose test of all the hops involved. This essentially walks through the hops starting at my location and then moving towards launcher.bethesda.net. WinMTR tracks a few extra statistics such as packet loss:
What I see from the above is that there is an issue going from be2764.ccr41.dfw03.atlas.cogentco.com (Cogent Edge) to 192.205.36.221 (Listed as an AT&T address). Specifically during this test there was 43% packet loss when moving between those hops. It would therefore appear that the issue is likely not directly with ESO but rather somewhere along that hop. Unfortunately if this is the root cause I'm not sure where that leaves us with getting the issue resolved. Is this something ZOS could look in to since so many of their customers are affected?
It would probably also help if others experiencing the issue could run the same test and confirm or not confirm that they are seeing the issue at the same spot.
Update: A workaround as per below is to use a VPN connection to a location in the US to avoid the bad hop. If you don't have a VPN provider there are plenty of free ones out there that will provide varying degrees of free monthly data (I found one that offered 10gb/month for free).
Edited by Zys7321 on July 4, 2017 9:37PM The first test I ran was to use an http ping (since regular pings are blocked) to launcher.bethesda.net to see if I could replicate the bad ping issue. As you can see below this did occur in a 4 packet ping:
Pinging "http://launcher.bethesda.net":
1> Reply: [200/OK] bytes=189 time=148ms
2> Reply: [200/OK] bytes=189 time=143ms
3> Reply: [200/OK] bytes=189 time=3160ms
4> Reply: [200/OK] bytes=189 time=3162ms
Ping statistics for "http://launcher.bethesda.net":
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 3162ms, Average = 1653ms
From there I used a network trace route program called WinMTR to perform a more verbose test of all the hops involved. This essentially walks through the hops starting at my location and then moving towards launcher.bethesda.net. WinMTR tracks a few extra statistics such as packet loss:
What I see from the above is that there is an issue going from be2764.ccr41.dfw03.atlas.cogentco.com (Cogent Edge) to 192.205.36.221 (Listed as an AT&T address). Specifically during this test there was 43% packet loss when moving between those hops. It would therefore appear that the issue is likely not directly with ESO but rather somewhere along that hop. Unfortunately if this is the root cause I'm not sure where that leaves us with getting the issue resolved. Is this something ZOS could look in to since so many of their customers are affected?
It would probably also help if others experiencing the issue could run the same test and confirm or not confirm that they are seeing the issue at the same spot.
Update: A workaround as per below is to use a VPN connection to a location in the US to avoid the bad hop. If you don't have a VPN provider there are plenty of free ones out there that will provide varying degrees of free monthly data (I found one that offered 10gb/month for free).
1
-
Pnyx✭✭I did my own checking and I've reached the same conclusion. I am in Western Canada, by the way. So, I started my VPN and set the server in the Eastern U.S. 100% of my packets went through. I loaded the game and I'm getting 200ms latency.
No issues in 15 minutes of playing.0 -
Zys7321Soul ShrivenAs Pnyx mentioned using a VPN from the right location can work around the bad hops. I tunneled to Chicago and had no issues for 30 minutes of running around in Cyrodiil. There will be lots of other US locations that would work as well until the root issue is resolved.0
-
Lirkin✭✭✭✭What did you tunnel too? It there a available location.
Just so you know I am on the east coast in New England and have been getting really bad lag for about a week. I get 999+ pings and even when the ping says 100 I get slow responses to every thing I try to do.0 -
Lirkin✭✭✭✭I ran the test and this is what I get:
|
|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|
|
|
|
|
|
|
|
| HATHAWAY-S - 0 | 33 | 33 | 0 | 0 | 0 | 0 |
| vtelinet-216-66-106-1.vermontel.net - 0 | 33 | 33 | 1 | 51 | 853 | 1 |
| vtelinet-216-66-105-21.vermontel.net - 4 | 29 | 28 | 0 | 1 | 1 | 1 |
| vtelinet-216-66-105-22.vermontel.net - 0 | 33 | 33 | 5 | 5 | 12 | 5 |
|te0-7-0-3-7.ccr31.bos01.atlas.cogentco.com - 0 | 33 | 33 | 5 | 5 | 5 | 5 |
| be2299.ccr21.alb02.atlas.cogentco.com - 0 | 33 | 33 | 9 | 9 | 10 | 9 |
| be2878.ccr21.cle04.atlas.cogentco.com - 0 | 33 | 33 | 19 | 19 | 20 | 20 |
| be2717.ccr41.ord01.atlas.cogentco.com - 0 | 33 | 33 | 27 | 27 | 28 | 28 |
| be2831.ccr21.mci01.atlas.cogentco.com - 0 | 33 | 33 | 39 | 39 | 40 | 39 |
| be2432.ccr31.dfw01.atlas.cogentco.com - 0 | 33 | 33 | 49 | 49 | 50 | 49 |
| be2763.ccr41.dfw03.atlas.cogentco.com - 0 | 33 | 33 | 49 | 49 | 50 | 49 |
| 192.205.36.221 - 14 | 23 | 20 | 52 | 53 | 55 | 52 |
| cr2.dlstx.ip.att.net - 23 | 18 | 14 | 54 | 55 | 58 | 55 |
| gar24.dlstx.ip.att.net - 24 | 17 | 13 | 51 | 77 | 160 | 160 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Dies at ATT0 -
crowbartoolSoul ShrivenI have EXACTLY the same problem from the same geographical location (Western Canada - Langley BC) using a fibre connection from Telus. The issue disappears ONLY when running through a US VPN. This issue has been ongoing for the good part of a week now.
0 -
Vapirko✭✭✭✭✭
✭✭✭✭✭Anyone know how to do this on Mac? Tried the http ping via net work utility and terminal command but I just get request timeouts. Not savvy enough to know what's up and google hasn't helped much. I did however just notice that Mudfish had rerouted my traffic from Thailand through to Japan and normal it goes through Singapore. I'm now getting stable latency and abilities are working. Still getting some abnormal spikes to 3000 but generally it's sitting around 270-320 which is normal for me. Tried some different paths seems to be working better.0 -
rendolpheb16_ESO✭✭✭Just renewed my subs today and got that garbage lag spike.
Can't PvP
Can't run pledge
Can't run skyshard
Fix this I just lost a precious free time night of ESO and my wife won't understand this.For Templar PvP video check my youtube channel
https://www.youtube.com/RendolpheGamer0 -
Ethoir✭✭✭These issues indeed don't lie with ZoS but with the internet itself. As ZoS lays somewhere near the eastern US Seaboard (Maryland, more specifically), it sat in one of the hot zones of service disruptions across multiple ISP's over the last several days (according to downdetector.com). The disruptions led to higher pings, higher packet loss, and even loss of connection to some services.
While I cannot say or prove if ZoS was affected by the disruptions itself, the areas around it certainly were and that could impact ping times and packet integrity to the server. And we can't forget that solar weather conditions may have also played a part.
In short, it was just a bad weekend to be online if you live on or use services based in the eastern US. Frustrating, even.Participant in the Sanguine's Tester beta group since November 2013.0 -
DaveMoeDee✭✭✭✭✭
✭✭✭I almost got killed on a final battle for a particular Morrowind quest line due to crazy lag. Been a long time since I have experienced lag like that in PvE. I'm not sure I've ever experienced that solo. As soon as she died, lag seemed to stop, but I didn't check ping after the fact.0 -
Hookgrin✭✭✭I don't know if this is true or not but I have always heard that the servers are located in Dallas Texas.0 -
Lirkin✭✭✭✭I just found a site that allows you to traceroute and it shows the locations on a map:
http://www.monitis.com/traceroute/
It shows the location of their servers in the middle of the country but I think it may just be where the communication error is located. Check it out.
When I check it the end location is in Nebraska.
Edited by Lirkin on July 5, 2017 3:52AM0 -
Hookgrin✭✭✭
Yeah what I meant was is why. It is starting right at the router. I did have a problem the other night, took restarting all the devices several times to get things working again, but something hasn't been right since.
This morning I bypassed the home network and plugged directly into the modem and got the below response which is similar to the OP's. I then did a factory reset on my router and installed a firmware upgrade, but still get packet loss on everything when going through the router. Maybe time for a new one.
Edited by Hookgrin on July 5, 2017 8:45PM0 -
Lirkin✭✭✭✭The Visual traceroute site shows the ping goes west to Kansas and then up to Nebraska and then fails. So if their servers are in Maryland there is a major routing issue on the internet.0
-
Lirkin✭✭✭✭I just found a site that allows you to traceroute and it shows the locations on a map:
http://www.monitis.com/traceroute/
It shows the location of their servers in the middle of the country but I think it may just be where the communication error is located. Check it out.
When I check it the end location is in Nebraska.
Like I said before use that site and see where it shows your traceroute goes.0 -
olivesforge✭✭✭✭Servers are at the Level 3 farm in Dallas which also supports GW2, BDO, B&S and a bunch of others. Note the pathing makes it pretty easy to read hops without a map. For example,Soooo... um, what is this trying to tell me?
This route goes from Hookgrin's location, joins the backbone at the Phoenix (phx) node, transits the El Paso (elp) and Houston (iah) nodes and gets off at the Dallas-Ft. Worth node (DFW). From there it hit's AT&T's network, where it's shunted to the Dallas side of the metro (dlstx) transiting from Carrollton (cr2) to Garland (gar24) before going local again. Note that this doesn't mean the servers themselves are in Garland, they're actually in Dallas proper, but at a location I won't type because it's prolly not a good idea.crowbartool wrote: »I have EXACTLY the same problem from the same geographical location (Western Canada - Langley BC) using a fibre connection from Telus. The issue disappears ONLY when running through a US VPN. This issue has been ongoing for the good part of a week now.
In this case, the route goes Seattle (sea) - Salt Lake City (slc) - Denver (den) - Kansas City (mci) - Dallas-Ft. Worth (dfw) and then off into the Carrollton (cr1) center.
What I notice is that there seems to be a problem for Hookgrin locally, because his packet loss hits 72% before it even gets out of his subdivision/rural area, whereas crowbartool's is clean all the way into the local servers in Dallas - so two different and unrelated causes here.
PCNA | Aldmeri Dominion
OlivesForge / Swiss Army Templar | Twink of Insanity / Gankblade | Olivesisnotonfire / Annoying Sorc | E. Angus / Magicka Pigeon-Thrower | K. Angus / Stamina Pigeon-Thrower
Personage of note in:
Dominant Dominion | Ethereal Traders Union | Knights of the Istari | CoC | Cyrodiil FG1 -
smacx250✭✭✭✭✭Anyone know how to do this on Mac? Tried the http ping via net work utility and terminal command but I just get request timeouts. Not savvy enough to know what's up and google hasn't helped much. I did however just notice that Mudfish had rerouted my traffic from Thailand through to Japan and normal it goes through Singapore. I'm now getting stable latency and abilities are working. Still getting some abnormal spikes to 3000 but generally it's sitting around 270-320 which is normal for me. Tried some different paths seems to be working better.
@Vapirko - open up "Terminal.app", and type:
ping <server>
or
traceroute <server>
Where <server> is the server name or IP address you are trying to test.
Edit: Timeouts aren't uncommon, as ICMP packets are routinely discarded by many nodes (often as DDOS protection)Edited by smacx250 on July 6, 2017 12:59AM0 -
Lirkin✭✭✭✭Well my visual ping shows it going from New York ( where the website is located ) to Kansas then they stop. The last address that works is for ATTEdited by Lirkin on July 6, 2017 1:00AM0
-
nine9six✭✭✭✭✭
✭Very interesting information in this forum. Thanks for the reading material!Wake up, we're here. Why are you shaking? Are you ok? Wake up...0 -
Thogard✭✭✭✭✭
✭✭✭✭✭Could it be possible that it is just ESO data that is getting dropped? Or would these nodes be misbehaving on all data? My guess would be all data because you can see packet loss on just the pings...
It just seems strange that a node could be malfunctioning like this for so long, and I believe it's multiple ATT nodes which makes me think it's something systemic in ATT's treatment of ESO.Edited by Thogard on July 6, 2017 8:24PMPC NA - @dazkt - Dazk Ardoonkt / Sir Thogalot / Dask Dragoh’t / Dazk Dragoh’t / El Thogardo
Stream: twitch.tv/THOGARDvsThePeasants
YouTube: http://youtube.com/c/thogardpvp0 -
Sigtric✭✭✭✭✭
✭✭✭✭✭Something definitely strange going on with routing here. I am not affected, my connection to the game has been fine. Yet... Full loss after Garland
| router.asus.com - 0 | 43 | 43 | 0 | 0 | 2 | 0 |
| x.x.x.x - 0 | 43 | 43 | 7 | 10 | 20 | 13 |
|te-0-4-0-13-sur01.pimaco.az.pima.comcast.net - 0 | 43 | 43 | 8 | 14 | 25 | 14 |
| be-10-sur02.pimaco.az.pima.comcast.net - 0 | 43 | 43 | 8 | 13 | 25 | 9 |
| be-1-ar02.pimaco.az.pima.comcast.net - 0 | 43 | 43 | 10 | 13 | 25 | 12 |
|be-33653-cr02.losangeles.ca.ibone.comcast.net - 0 | 43 | 43 | 21 | 25 | 33 | 25 |
|hu-0-0-0-1-pe02.600wseventh.ca.ibone.comcast.net - 0 | 43 | 43 | 19 | 24 | 32 | 24 |
| 192.205.37.25 - 0 | 43 | 43 | 21 | 28 | 38 | 34 |
| cr2.la2ca.ip.att.net - 0 | 43 | 43 | 45 | 54 | 64 | 58 |
| cr2.dlstx.ip.att.net - 0 | 43 | 43 | 47 | 55 | 67 | 62 |
| gar24.dlstx.ip.att.net - 0 | 43 | 43 | 48 | 82 | 379 | 68 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderEdited by Sigtric on July 6, 2017 8:40PM
Stormproof: Vibeke - 50 EP mDragonknight | Savi Dreloth - 50 EP Magsorc | Sadi Dreloth - 50 EP Magblade | Sigtric Stormaxe - 50 EP Stamsorc | Valora Dreloth - 50 EP Magplar | Sigtric the Unbearable 50 EP Stam Warden
Scrub: Chews-on-Beavers - 50 EP DK Tank | Vera the Wild - 50 EP magicka Warden | Sigtric the Axe - 50 EP Dragonknight Crafter | Sigtric the Blade - 50 EP Lost Nightblade | Sigtric the Savage - 50 EP magicka Templar | Vibeka Shadowblade - 50 Ep Stealthy Ganky Nightblade |
Show Me Your Dunmer
[/center]0 -
QuebraRegra✭✭✭✭✭
✭Like many others here (and many more who haven't posted) I too have been experiencing very bad pings while playing. With that being said there are also a lot of players who don't appear to be having an issue. Based on this scenario it sounded like it might be an issue with a networking hop to me. As a quick primer when you connect to something on the Internet your data packets pass through a number of network devices. Each time this occurs it is called a hop. The hops that your data packets go through are different depending on your location as well as other factors.
The first test I ran was to use an http ping (since regular pings are blocked) to launcher.bethesda.net to see if I could replicate the bad ping issue. As you can see below this did occur in a 4 packet ping:
Pinging "http://launcher.bethesda.net":
1> Reply: [200/OK] bytes=189 time=148ms
2> Reply: [200/OK] bytes=189 time=143ms
3> Reply: [200/OK] bytes=189 time=3160ms
4> Reply: [200/OK] bytes=189 time=3162ms
Ping statistics for "http://launcher.bethesda.net":
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 3162ms, Average = 1653ms
From there I used a network trace route program called WinMTR to perform a more verbose test of all the hops involved. This essentially walks through the hops starting at my location and then moving towards launcher.bethesda.net. WinMTR tracks a few extra statistics such as packet loss:
What I see from the above is that there is an issue going from be2764.ccr41.dfw03.atlas.cogentco.com (Cogent Edge) to 192.205.36.221 (Listed as an AT&T address). Specifically during this test there was 43% packet loss when moving between those hops. It would therefore appear that the issue is likely not directly with ESO but rather somewhere along that hop. Unfortunately if this is the root cause I'm not sure where that leaves us with getting the issue resolved. Is this something ZOS could look in to since so many of their customers are affected?
It would probably also help if others experiencing the issue could run the same test and confirm or not confirm that they are seeing the issue at the same spot.
Update: A workaround as per below is to use a VPN connection to a location in the US to avoid the bad hop. If you don't have a VPN provider there are plenty of free ones out there that will provide varying degrees of free monthly data (I found one that offered 10gb/month for free).
ideally you should ping on the same ports the game uses, but that's not shabby. You get "pro" points for using "Matt's Traceroute" (MTR). Something to note... There's a lot of network infrastructure out there that simply does not respond to ICMP/PING, or to packets directed to it on various ports, for security reasons (firewalls, etc.). 100% packet loss at a hop can be from the router/firewall just not responding to the ping, etc. Sometimes you'll see this in the middle of an MTR, but the destination host will have 0% packet loss. There's a lot of "red herrings" if you don't test correctly.Edited by QuebraRegra on July 6, 2017 8:46PM1 -
QuebraRegra✭✭✭✭✭
✭Something definitely strange going on with routing here. I am not affected, my connection to the game has been fine. Yet... Full loss after Garland
| router.asus.com - 0 | 43 | 43 | 0 | 0 | 2 | 0 |
| x.x.x.x - 0 | 43 | 43 | 7 | 10 | 20 | 13 |
|te-0-4-0-13-sur01.pimaco.az.pima.comcast.net - 0 | 43 | 43 | 8 | 14 | 25 | 14 |
| be-10-sur02.pimaco.az.pima.comcast.net - 0 | 43 | 43 | 8 | 13 | 25 | 9 |
| be-1-ar02.pimaco.az.pima.comcast.net - 0 | 43 | 43 | 10 | 13 | 25 | 12 |
|be-33653-cr02.losangeles.ca.ibone.comcast.net - 0 | 43 | 43 | 21 | 25 | 33 | 25 |
|hu-0-0-0-1-pe02.600wseventh.ca.ibone.comcast.net - 0 | 43 | 43 | 19 | 24 | 32 | 24 |
| 192.205.37.25 - 0 | 43 | 43 | 21 | 28 | 38 | 34 |
| cr2.la2ca.ip.att.net - 0 | 43 | 43 | 45 | 54 | 64 | 58 |
| cr2.dlstx.ip.att.net - 0 | 43 | 43 | 47 | 55 | 67 | 62 |
| gar24.dlstx.ip.att.net - 0 | 43 | 43 | 48 | 82 | 379 | 68 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 8 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
see my post just previous to this reply for why this happens. As you say, you have no in game problems yet the MTR shows 100% packet loss on AT&T... what it really means is that the AT&T equipment is configured to not respond to ICMP, etc. from your source host.
You really have to understand how the tools work, and have experience in using them, but this is a good start... albeit a false positive/negative.0 -
beetleklee✭✭✭✭I'm in Connecticut and it's been bad for almost a week. Get high ping spikes of 999+, seen one at 11,000 once. I'll rubberband sometimes and sometimes I can't activate anything. I'll also get kicked to the login screen. I had to quit some vet dungeons because I was just causing more problems with my laggy self. Skills and bar switching sometimes won't activate at all or it'll activate seconds later. It's making the game almost unplayable and I feel it's gotten worse the past two days.PC NA
CP 690
EP Dunmer MagDK Level 50, Stormproof
EP Dunmer MagSorc Level 50, Stormproof
EP Argonian DK Tank Level 50, Boethiah's Scythe
EP Breton Templar Healer Level 50
EP Khajiit StamDK Level 50, Stormproof
EP Dunmer Magblade Level 50, Assistant Alienist
EP Argonian Stamden Level 50, Lady of Misrule (pvp)
EP Dunmer Stamblade Level 50
DC Redguard Stamplar
AD Altmer Magwarden Healer
vMA, vDSA, vSO HM, vHRC HM, vAA, vAS+1, vMoL0
