So.. do we get like reimbursed for this issue? Like 2 weeks of just sitting around and can't do anything issue.
Edit: Make that 3 weeks?
-
01-10-2018, 01:12 PMXenoCranel
-
01-10-2018, 01:23 PMMidnightWonkoWe should just unsubscribe en masse if the issue is not fixed. I see no reason to pay for services not received.Quote:
Originally Posted by XenoCranel
-
01-10-2018, 02:51 PMNega_Nomicon
The packet loss is still in full force for me.
Tracing route to 204.2.229.82 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 7 ms 10.74.208.1
3 7 ms 7 ms 7 ms ip68-4-14-96.oc.oc.cox.net [68.4.14.96]
4 7 ms 8 ms 8 ms ip68-4-11-102.oc.oc.cox.net [68.4.11.102]
5 9 ms 10 ms 11 ms 68.1.1.167
6 9 ms 9 ms 9 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 36 ms 36 ms 35 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 28 ms * 28 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 35 ms 35 ms * ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 35 ms 35 ms 42 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 * 35 ms 39 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 25 ms 24 ms 25 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 * 39 ms 38 ms 204.2.229.242
14 39 ms 39 ms 40 ms 204.2.229.82
This issue has been on-going for almost a month, which is a subscription fee, and has disabled us from participating in the majority of the content that we pay monthly to experience. The issue has NOT subsided and I think this should be treated more seriously. This is completely unacceptable. -
01-10-2018, 03:31 PMNega_Nomicon
https://www.youtube.com/watch?v=lP949_Rzs8g
I filmed this clip tonight with one of my characters to show how severe the packet loss is. -
01-10-2018, 04:38 PMMidnightWonkoCan confirm that light party dungeons are that bad, and that 24-man raids like Rabanastre are UNPLAYABLE! Freezes from packet loss can stretch for OVER TEN SECONDS (some FAR worse), and any vet of Rabanastre here knows how lethal not being able to move for that long is.Quote:
Originally Posted by Nega_Nomicon
-
01-10-2018, 04:40 PMKoos
I am running into the same mentioned issues of near unplayable latency. I had consistent 2+ second spikes (the worse being 6 seconds) all over the past few weeks. Cox is also my cable provider:
Tracing route to 204.2.229.9 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms router.asus.com [192.168.1.1]
2 9 ms 8 ms 8 ms 10.74.0.1
3 8 ms 13 ms 8 ms ip68-4-13-78.oc.oc.cox.net [68.4.13.78]
4 10 ms 8 ms 6 ms ip68-4-11-8.oc.oc.cox.net [68.4.11.8]
5 10 ms 12 ms 17 ms 68.1.1.63
6 17 ms 13 ms 12 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 39 ms 44 ms 43 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 27 ms 25 ms 28 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 16 ms 18 ms 18 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 58 ms * 37 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 38 ms 35 ms 36 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 48 ms 48 ms 46 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 * 54 ms 52 ms 204.2.229.242
14 42 ms 44 ms 39 ms 204.2.229.9 -
01-10-2018, 05:21 PMElasmoFan
I would just look to put in that I've been having the same issue with Cox in CA. I do ok earlier in the day on my days off then during prime time, it becomes borderline unplayable. It's been going on for quite a while now and it's frustrating because that's the only time I can play consistently. With the new patch around the corner and me trying to prepare for it, it's frustrating that this is just up in the air and nothing can be done about it because everyone's just pointing fingers at each other. I don't want to have to unsubscribe but I'm almost going on a full sub with this issue and I may not have a choice. I don't like the idea of missing out on things, especially with a patch coming that my friends and other players will be able to participate in. It completely kills my drive for wanting to play the game and makes it hard for me to even want to come back if I unsubscribe.
Edit: Seems like it's been shown several times that the issue isn't with Cox and there isn't anything they can even do about it, so at this point it's SE's responsibility. I would hope this is a high priority and not just a small handful of people who can't play but since it's small, who cares about them situation. Would hate to think we're low priority or getting snubbed just because it's not a major number of people having this happen to them.
Edit2: There's also a reddit full of people now that are talking about having this problem. I honestly worry this isn't something that'll even get fixed and we'll just be stuck with them saying there's nothing to do about it or continuing to point fingers or going unresponsive. I would hate to end up having to use a VPN when apparent that doesn't even work well with this problem. I really enjoy this game and love the people and friends I've made but I just can't deal with how bad it gets on a long term. I understand there are people who have to deal with it who are over seas are far from the node or something but being where we are and seeing what's causing the problem, I don't feel like it's worth going through if they're unresponsive or don't attempt to fix the issue. I don't want to be negative about this, honestly. I just am disappointed and frustrated. -
01-11-2018, 01:09 AMscreamercy
I would like to chime in as another victim of the lag/rubber banding as of early December. I really thought it was a problem with my router or modem at first. I replaced the router and still had the same issue. Then I called Cox and had a tech come out who told me all the connections were good, no issues on their end. Bought another new brand modem/router combo and had the lag again. Finally found this thread. I really hope Square Enix can help us out here, the game really sucks to play with this lag and its really unfair to all the people I play with as well. Cox user in Arizona.
-
01-11-2018, 02:37 AMLadon
Will try and be civil here, but this issue really needs to be handled and communicated better by SE.
Many of us have already tried contacting our ISPs. Has this ever and will it ever actually do anything to solve these issues? 1, 10 or even 1000 customers calling to complain about this issue is not going to force an ISP with millions of customers to act to address a single service on their network. Also quite fairly, they often will state it is not an issue with their network, but with a peering network. In this case, NTT is being reported as the source of the issue. Just as with an ISP, NTT is not going to address issues opened by a few hundred consumers to address one service on their network. SE needs to start recognizing these issues and leverage their business to get these issues sorted out. If you are unable to do this, it should also be communicated so at least the players being impacted by the issue understand their options rather than continue to sit around for months hoping for the issue to be addressed. I understand this is impacting a relatively small portion of your userbase, but it continues to be a consistent issue that should be formally addressed just as every other obscure issue typically is by the development or management teams.
Edit, just to add more to the statistics, fresh today at prime time:
http://i67.tinypic.com/es857c.jpg
The issue with NTT is pretty clear. -
01-11-2018, 02:45 AMRahh
hello,
I do not see/post on the forums very often so I'm just now seeing this but the issue has not gotten any better. In fact, I think it's actually gotten worse. I am also in Arizona and have Cox as my ISP. They have confirmed several times that the issue is not with them. The can see it's through NTT and I can as well when doing a tracer route. I've tried a VPN but that doesn't seem to be much of a help either. -
01-11-2018, 03:19 AMKayos_Bismark
Same here. Also an Arizona Cox Communications user.
-
01-11-2018, 03:31 AMlundjames
90k during duties almost exclusively, same time of day as reported initially, and I'm a Cox customer in Nebraska, USA. Tracerts support a problem with NTT's throughput as described above. I can usually get back in after 3 very fast attempts to log back in, but this is tedious.
Happening since around 4.15. -
01-11-2018, 03:50 AMPrincessPeaNuT
I'm having the same problem too. I have Cox. My friend also has similar problem and he has Cox. Like lundjames it all started around 4.15 ish. It used to be fine until then.
-
01-11-2018, 04:00 AMDukeStardust
Same here as well, and finally good to know it's not just me since it's been driving me crazy. :] Cox Internet subscriber in Orange County, Calif., suddenly started experiencing serious lag spikes (especially in dungeons/raids) in the evenings, and started happening around that patch timing (4.15-ish). Never had a sustained problem like this previously (been playing for ~2 years), and only seems to impact FF14. Can play other games, stream, etc. just fine. Please look into this; it's been bad enough for long enough that we've been considering unsubscribing since the game has sadly become borderline unplayable. Many thanks!
-
01-11-2018, 04:02 AMEinmimiria
Thank you for the reply cosmicrobot,
And both you and your boyfriend are getting the same lag correct? on two separate devices? Is this only in dungeons or during the evening? Have you had this same issue during other times of the day (not during peak hours)?
We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV! -
01-11-2018, 04:52 AMcosmicrobot
We both have similar windows computers and share the same internet so lag i feel he also does. We've been leveling another class and spamming dungeons so we've only been doing dungeons where we get lag noticeably. I can say when we were in a not populated city we were lagging as well so I don't think its just dungeons.
We usually play 6 pm central time to 11 pm tues-friday, on sunday and monday we play at any time of the day and still experienced the lag. -
01-11-2018, 05:34 AMKevsop
I am a Cox Communication Customer in Arizona and I know of at least one other person in a similar situation. Just posting here to make sure this topic gets the attention it deserves. The game has been very hard to play, and this was not the situation that the game was in when the servers first moved west. I am not having any connection issues in any other program or service, only FFXIV. With the new patch not so far away I'd like to get back into the game more but at this rate it is very hard to enjoy doing anything.
-
01-11-2018, 07:24 AMMizunoNekoEveryone Should Call Square Enix to Report This Problem
Yesterday I called Square Enix to talk to them about the severe packet loss on NTT network causing lag that makes the game unplayable. I was shocked to be told that no one else is experiencing this problem, and it is probably just a problem I am having. And until more people report it, there is nothing they can do.
Therefore, I'm suggesting EVERYONE on this thread who is having bad lag issues due to packet loss on NTT's network should CALL IN AND REPORT THIS VIA PHONE. Here is Square Enix's support number: 1 (858) 790-7529.
To check to see if you are having packet loss on ntt's network, in Windows, go into your start menu and type cmd and hit enter. At the command prompt type
tracert 204.2.229.9
The ip listed there is my particular server ip (aether), the others are all listed here https://arrstatus.com/. Anywhere you see a * on the output means a packet was lost. Here is an example of my tracert and you can see that I have lost packets on the hops that end with ntt.net:
1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 18 ms 8 ms 8 ms 10.7.82.1
3 8 ms 7 ms 9 ms 68.4.15.32
4 12 ms 11 ms 15 ms ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
5 15 ms 16 ms 14 ms 68.1.1.63
6 15 ms 14 ms 21 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 37 ms 42 ms * ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 30 ms 31 ms * ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 * 46 ms 39 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 38 ms * 39 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 39 ms 37 ms * ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 42 ms 45 ms 45 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 25 ms * 26 ms 204.2.229.242
14 42 ms 42 ms 42 ms 204.2.229.9
I am very disappointed with how Square Enix is handling this issue. I cannot play any current content (Shinryu or Deltascape Savage, and of course Ultimate Coils are completely out). This will affect my ability to raid come 4.2 and if I lose my group due to it I will be canceling my subscription. -
01-11-2018, 07:32 AMlordcook
Cox cable in California having this same issue since early December. I thought it was related to my county being on fire and just dealt with it thinking it was temporary (started having issues basically right when the fires started for my county). Still occurring daily during primetime, 6pm pacific past 10pm (aka the only time I have to play).
Hopefully they get this settled with NTT otherwise theres not much point in being subscribed for me. -
01-11-2018, 08:43 AMElasmoFan
What ISP do you have?
-
01-11-2018, 09:02 AMcosmicrobot
We have comcast
-
01-11-2018, 11:29 AMCallinonI did. You helped someone else instead. I'm still getting high latency every evening like clockwork. During the day no problems at all, 50-70ms. After 6pm CST, 170-230ms. I've seen it spike as high as 520ms. I've given you loads of data on this which includes where the likely problem is in your ISP's network. Is there something else you want?Quote:
Originally Posted by Ariellendera
-
01-11-2018, 12:14 PMLaraul
I have Cox im AZ and have not been noticing any issues with latency and the game. No lag spikes. No 90001 errors.
A 30 minute span during prime time. As you see I have no packet loss.
https://i.imgur.com/BHGvxle.png
I'm unclear why some people are having problems and others not.
A few observations.
1. If it were NTT servers that were at fault then the latency problems would not be limited to just one ISP. All ISPs would be effected.
2. I don't see how an Cox support operator would know details for why just one game isn't working.
3. Back when the game passed through Level3 servers, a few people had these same problems. People complained that Level3 servers were garbage and they we're at fault. Like people are blaming NTT now.
4. A lot of people like me aren't experiencing problems. But you never here from us because why visit these threads unless we start having trouble. -
01-11-2018, 01:48 PMSyrehnThe reason you're not having an issue and others are is because they're hitting the congested NTT nodes during peak hours that are failing under the load and you're not. Simple as that.Quote:
Originally Posted by Laraul
It's not limited to just Cox, there are other threads with other people from other ISP's having the exact same problem when their connection is travelling through specific NTT nodes. -
01-11-2018, 02:11 PMNega_Nomicon"But you never here from us because why visit these threads unless we start having trouble." - So why are you here? We've already established that it's not affecting everybody which is what makes this situation frustrating and strange. I have exceptional hardware and I pay my ISP for the highest speeds they offer. If you did more research you'd learn that it's affecting Cox and other ISPs. If I play any other online game it runs beautifully as it should. This issue is entirely up to Square Enix to solve or they're going to lose a lot of subscribers from the west coast, southern, regions.Quote:
Originally Posted by Laraul
-
01-11-2018, 02:30 PMBucklesTrespen
I'd just like to add that I am experiencing the same on the Behemoth server.
Currently in Royal City and I am freezing for 5-30 seconds and people are constantly ice skating around me.
Asked if anyone else is experiencing this and most of the raid says they are.
We wiped twice to the third boss because the lag was so unplayable no one could do the click mechanic. -
01-11-2018, 02:32 PMBluefveWrong. MMOs don't work like that. Internet Data Centers often have numerous routes and uplinks, depending on geolocation and IP (for the intent of optimizing connections and providing more bandwidth. This could be a situation where one particular uplink is messed up, and why not everyone sees it.Quote:
Originally Posted by Laraul
True, but an ISP Network Engineer would have better insight and understanding for enterprise-level network architecture and their own infrastructure. The engineer I spoke to talked about his own experience working with Blizzard on a similar issue, back in 2013, for WoW.Quote:
Originally Posted by Laraul
Level3 does have bad routing. Its worse in certain geographic areas though, like France.Quote:
Originally Posted by Laraul
Right, no one said EVERYONE is experiencing the problem. But the internet is a complicated beast, and a large number of people ARE experiencing a problem.Quote:
Originally Posted by Laraul
Two additional observations from your own data that I've noticed, is that...
1) Mostly (if not all) everyone who's having this problem is from California, CA. (You yourself are in AZ, which may not be affected)
2) Mostly (if not all) everyone who's reporting the problem are pinging 204.2.229.9 (You are pining 204.2.229.103 -- could mean everything, could mean nothing)
I don't know how relevant these details are, but they are nonetheless details. :)
My Pingplotter results taken just now.
Target Name: 204.2.229.9
IP: 204.2.229.9
Date/Time: 1/10/2018 9:19:17 PM - 1/10/2018 9:29:17 PM
Hop Sent PL% Min Max Avg Host Name / [IP]
1 472 0 0.55 18.01 1.56 SYNOLOGYROUTER [192.168.1.1]
2 472 0 4.72 23.56 9.00
3 472 0 4.70 24.54 9.65 ip68-4-11-194.oc.oc.cox.net [68.4.11.194]
4 472 0 5.25 30.27 11.06 ip68-4-11-16.oc.oc.cox.net [68.4.11.16]
5 472 0 7.47 68.47 14.58 68.1.1.63 [68.1.1.63]
6 472 0 8.26 53.58 15.94 ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 472 1 17.92 40.26 21.84 ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 472 1 8.12 34.10 14.00 ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 472 3 34.06 59.62 38.16 ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 472 3 32.97 55.35 37.39 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 472 8 35.81 61.52 41.08 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
12 472 8 37.46 68.59 41.03 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
13 472 23 36.84 57.31 41.21 204.2.229.242 [204.2.229.242]
14 472 5 35.93 98.00 41.41 204.2.229.9 [204.2.229.9]
Would be interesting to see more people's PingPlotter results, too, versus plain traceroutes. -
01-11-2018, 03:50 PMLaraulSeveral posts we're from people in AZ, including the original poster. It is not limited to just people in California.Quote:
Originally Posted by Bluefve
I pinged my server, which is 204.2.229.103. I assume 204.2.229.9 is the pinger's server. I don't know for certainQuote:
Originally Posted by Bluefve
I was simply trying to say that the problem is likely an issue local to the user. If you are experiencing frequent disconnects and/or lag spikes over a number of days, call Cox and have them come out and do a line test. Try also checking your modem's web management server (if it has one). I believe it's usually found by typing "http://192.168.100.1" into a web browser. Lastly you can always reboot/reset/replace your router (if possible). Most people have already tried some of these already.
The last time I was experiencing frequent disconnects and lag spikes, it turned out that line that runs to my block was mauled on by some animal. And it wasn't discovered until they did a visual line check of the line. This was causing a dip in line signal power resulting in a poor connection. It took them two or three days to find and repair it. -
01-11-2018, 03:56 PMXenoCranelThat is totally unrelated to this issue.Quote:
Originally Posted by Laraul
-
01-11-2018, 10:16 PMKerwinThis is a tech forum post, if you are not having problems then take your posts elsewhere. Otherwise you clog the thread with your useless statements.Quote:
Originally Posted by Laraul
-
01-11-2018, 11:19 PMChortleABSOLUTELY DO NOT DO THIS!Quote:
Originally Posted by Laraul
Cox will charge you fees for sending someone out.
Also, the issue is NOT on Cox's end as it has been stated multiple times. What time of day did you check your latency? Most of the people here have issues between 6-10pm (sometimes later) ONLY. Every other time of day there seems to be no issue.
Please do not give people advice that could potentially cost them money. When a substantial amount of players from the southwest are experiencing an issue... chances are it's not "a local issue to the user" and it's definitely not because our lines were "mauled on by some animal".
There are plenty more people having this issue than those commenting on this thread. Someone posted about it on reddit yesterday even.
https://www.reddit.com/r/ffxiv/comme...ghly_unstable/ -
01-12-2018, 01:42 AMdrebbeGoing to copy what was said at reddit here so SE can clearly see it.Quote:
Originally Posted by Chortle
Quote:
This has been going on for nearly a month, and it looks like it's only recently come to light that the issue is dropped packets with the company SE contracts to host their servers. To quote one user,
"Cox got back to me. Confirmed on NTT.net's side, not a local network or Cox issue -- quite likely one of their several uplinks has has been designated for Cox users (perhaps, just for LA/OC) and is smaller than the real throughput traffic of Cox customers. Therefore, during peak times, it get's congested and drops packets and only users which have been assigned that particular route (based on ISP and perhaps geolocation) are affected and no one else.
Cox is unwilling to contact NTT.net directly, since they are the direct provider for SE. Cox urges users to pressure SE into getting their direct provider, NTT, to resolve the problem.
NTT.net is unwilling to investigate, unless a client directly requests it (AKA SE)-- per their Network Operations Team via noc@us.ntt.net.
Square Enix, please get your Network Engineers to validate based on provided data. I'm willing to cooperate further, and I'm sure other players will be willing to as well."
-
01-12-2018, 02:45 AMRahhI'm really surprised they say this issue is almost unheard of. I've seen multiple Reddit posts about it specifically to this game. This forum post has been going on for several weeks now too. I'll make sure to call to report it though. Thank you for the head's up.Quote:
Originally Posted by MizunoNeko
I couldn't agree with you more. I'm really hoping this issue gets resolved in the next few weeks because I am a raider as well and makes progression nearly impossible. I love this game to death and I appreciate everything SE, DEV and (of course) Yoshida but I just want to play the game :(Quote:
Originally Posted by MizunoNeko
-
01-12-2018, 02:47 AMLadonJust to add what the others have already said, please don't do this, it is not good advice and shows a fundamental lack of understanding how to read trace route results.Quote:
Originally Posted by Laraul
The trace routes being posted here clearly show issues after the peering hand-off to NTT. If this was an ISP or last mile issue, you would see high latency and/or packet loss the first couple of hops.
With that said, just want to add supporting evidence that it clearly looks to be a capacity issue with NTT during peak hours. I had the opportunity to play some this morning PT, off peak, and saw no issues and my trace route is totally clean:
https://i.imgur.com/P8c2DJl.png
Compared to last night where issues start to ramp up around 6pm PT, and then hit unplayable levels around 7:30PM PT:
https://i.imgur.com/Z2MB0QH.png -
01-12-2018, 03:59 AMChortle
Any updates on this Ariellendera?
Would you advise us to contact the SE support number to have a record of the issue? -
01-12-2018, 09:09 AMKerwinQuote:
- The kinds of connection issues you are having (lag, disconnections, etc.)
- Any potential error codes
- Your Internet Service Provider
- Frequency
- If you have the ability to perform a trace route, please post the details in full.
- Packet loss for upwards of 10-15 seconds (rubberbanding)
- In severe cases, 90k disconnection
- Comcast, Chicago IL
- Every day during prime time between 7:00pm till 11:00pm central time.
https://i.imgur.com/6qsYfRL.jpg
Round 2:
https://i.imgur.com/3sLm9iC.jpg
Round 3: NTT gets noticeably higher in ms response time and packet loss is still constant.
https://i.imgur.com/wBwuI7l.jpg
Oh Yes. The big one....
https://i.imgur.com/pWephpd.png
NTT is the cause. Take a look at the blocks that contain "NTT". These guys must be running hamster wheels or something because everything starts going bad when I hit their nodes.
The game is rendered UNPLAYABLE. I cannot raid with friends because I'm not fighting a boss. I'm fighting the rubberbanding lag! -
01-12-2018, 10:17 AMTsutla
Round 1
https://imgur.com/XB5joH2.png
Round 2
https://imgur.com/g8ejE0i.png -
01-12-2018, 01:02 PMDontTouchMe
This has been happening to me on a nightly basis for about 2 months now. It's unplayable due to constant lag.
Cox
https://i.imgur.com/e7SGEJJ.png -
01-12-2018, 01:52 PMdrebbe
Comcast, 11PM EST. NTT Hops like usual since server move.
Quote:
>pathping 204.2.229.10
Tracing route to 204.2.229.10 over a maximum of 30 hops
0 DESKTOP-M42FG6C [192.168.88.233]
1 192.168.88.1
2 ***********
3 te4-2-ur02.shelby.mi.michigan.comcast.net [68.86.121.157]
4 96.108.21.142
5 be-8-ar02.pontiac.mi.michigan.comcast.net [162.151.127.181]
6 be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45]
7 be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
10 ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
11 ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
14 xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
15 * 204.2.229.242
16 204.2.229.10
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-M42FG6C [192.168.88.233]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.88.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% ***********
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% te4-2-ur02.shelby.mi.michigan.comcast.net [68.86.121.157]
0/ 100 = 0% |
4 13ms 0/ 100 = 0% 0/ 100 = 0% 96.108.21.142
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% be-8-ar02.pontiac.mi.michigan.comcast.net [162.151.127.181]
0/ 100 = 0% |
6 18ms 0/ 100 = 0% 0/ 100 = 0% be-33668-cr02.350ecermak.il.ibone.comcast.net [68.86.90.45]
0/ 100 = 0% |
7 17ms 0/ 100 = 0% 0/ 100 = 0% be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
0/ 100 = 0% |
8 20ms 0/ 100 = 0% 0/ 100 = 0% ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
0/ 100 = 0% |
9 18ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
0/ 100 = 0% |
10 20ms 0/ 100 = 0% 0/ 100 = 0% ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
1/ 100 = 1% |
11 184ms 6/ 100 = 6% 5/ 100 = 5% ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
0/ 100 = 0% |
12 185ms 4/ 100 = 4% 3/ 100 = 3% ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
0/ 100 = 0% |
13 188ms 3/ 100 = 3% 2/ 100 = 2% ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
0/ 100 = 0% |
14 188ms 2/ 100 = 2% 1/ 100 = 1% xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
0/ 100 = 0% |
15 187ms 1/ 100 = 1% 0/ 100 = 0% 204.2.229.242
3/ 100 = 3% |
16 186ms 4/ 100 = 4% 0/ 100 = 0% 204.2.229.10
Trace complete.
-
01-13-2018, 06:29 AMXenoCranel
I have not experienced much lag in the last two nights. Anyone else?