HUGE CONNECTION PROBLEM

[ProfVukasin]

Still having the same issues I have been having since the 2.4 patch. I had zero issues prior to this patch. And the issue only really begins to creep up when I am trying to FATE grind or if another FATE train happens to roll by. I have to actively check to make sure there are no FATE parties in the area. My only hope now of leveling up my ninja is levequests and instance grinding when someone in my FC is up for it.

[Callinon]

Was having this issue before 2.4, but it's WAY worse now. I'm getting booted every hour or so... which is a problem when melee dps queues are over an hour long and getting d/c'd removes you from the queue.

For the record, this is not just in heavily populated areas. I've sat in my inn room or my FC house all by myself. Doesn't seem to matter where I am.

[Raist]

got some signs of congestion coming in trying to get from Toronto through Southern California. Latency spiked to almost 4x cutting through that one hop across Hurricane Electric's line, right around where you are getting exchanged to the transcontinental undersea line to take you over to Asia. The source of the packet loss may be occurring around that Southern Cali area--it's been a hotbed of high congestion and losses for a long time for multiple providers.

TWC seems to now have a direct peering arrangement with PACNET out of LA, so I'm not getting any spikes like that over there atm (my problems are still focused around Hilton Head and Columbia here in SC, not to mention I ran the tests on my wifi from the back of the house) But, it's not uncommon to see the LA/San Jose/Palo Alto areas throw up on themselves under heavy loads, so I might see something skewed if I checked during prime-time.

Tracing route to 124.150.157.158 over a maximum of 30 hops

  1     2 ms    <1 ms     1 ms  LPTSRV [10.10.100.1]
  2    33 ms    21 ms    16 ms  cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
  3   100 ms    18 ms    26 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    13 ms    12 ms    16 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    28 ms    27 ms    28 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    31 ms    29 ms    31 ms  107.14.19.44
  7    98 ms    97 ms    99 ms  107.14.17.179
  8    98 ms    98 ms    95 ms  ae-4-0.cr0.lax30.tbone.rr.com [66.109.6.2]
  9    93 ms    95 ms    97 ms  ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
 10    96 ms    97 ms    95 ms  66.109.10.194
 11   203 ms   203 ms   204 ms  ip-202-147-0-52.asianetcom.net [202.147.0.52]
 12   203 ms   201 ms   202 ms  gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
 13   200 ms   203 ms   202 ms  squareco.asianetcom.net [203.192.149.210]
 14   206 ms   201 ms   204 ms  61.195.56.129
 15   202 ms   199 ms   203 ms  219.117.144.70
 16   194 ms   193 ms   197 ms  219.117.144.57
 17   198 ms   197 ms   197 ms  219.117.144.41
 18   195 ms   197 ms   194 ms  219.117.147.190
 19   213 ms   213 ms   213 ms  124.150.157.158

Trace complete.

Edit:
Yeah... poking around Hurricane's looking glass, things look pretty consistent on the Tokyo side of things, but coming out of Fremont the response times are showing elevated jitter.

core1.fmt2.he.net> traceroute 124.150.157.158 Target 	124.150.157.158
Hop Start 	1
Hop End 	30
Hop 	Packet 1 	Packet 2 	Packet 3 	Hostname
1 	0.232 ms 	0.279 ms 	0.314 ms 	ge5-19.core1.fmt2.he.net (64.71.148.109)
2 	0.621 ms 	0.614 ms 	0.635 ms 	10ge1-1.core1.sjc2.he.net (72.52.92.74)
3 	0.999 ms 	0.994 ms 	1.005 ms 	pacnet.10gigabitethernet2-2.core1.sjc2.he.net (216.218.192.234)
4 	0.726 ms 	103.159 ms 	103.156 ms 	gi2-0-0.gw1.sjc1.asianetcom.net (202.147.50.210) gi9-0-0.cr2.nrt1.asianetcom.net (202.147.50.134)
5 	103.669 ms 	103.674 ms 	114.631 ms 	ge-2-1-0-0.gw3.nrt5.asianetcom.net (202.147.0.182) po4-0-0.cr1.nrt1.asianetcom.net (202.147.0.33)
6 	114.005 ms 	113.948 ms 	113.983 ms 	gi6-0-0.gw1.nrt5.asianetcom.net (202.147.0.45)
7 	114.060 ms 	114.135 ms 	114.611 ms 	squareco.asianetcom.net (203.192.149.210) 61.195.56.129
8 	114.108 ms 	114.112 ms 	107.365 ms 	61.195.56.129 219.117.144.70
9 	106.604 ms 	106.584 ms 	106.695 ms 	219.117.144.49 219.117.144.70
10 	107.482 ms 	108.005 ms 	107.275 ms 	219.117.144.41 219.117.144.29 219.117.144.41
11 	107.657 ms 	107.650 ms 	107.673 ms 	219.117.144.29 219.117.147.190


core1.tyo1.he.net> traceroute 124.150.157.158 Target 	124.150.157.158
Hop Start 	1
Hop End 	30
Hop 	Packet 1 	Packet 2 	Packet 3 	Hostname
1 	6.213 ms 	6.238 ms 	6.255 ms 	ge2-3.core1.tyo1.he.net (74.82.46.5)
2 	1.141 ms 	1.022 ms 	1.054 ms 	as10026-2.ix.jpix.ad.jp (210.171.224.84)
3 	0.629 ms 	0.623 ms 	0.600 ms 	gi3-0-0.gw1.nrt5.asianetcom.net (202.147.1.186)
4 	0.673 ms 	0.656 ms 	0.637 ms 	squareco.asianetcom.net (203.192.149.210)
5 	0.660 ms 	0.745 ms 	0.719 ms 	61.195.56.129
6 	99.787 ms 	99.589 ms 	99.866 ms 	219.117.144.70
7 	100.331 ms 	100.388 ms 	100.375 ms 	219.117.144.57
8 	100.359 ms 	98.766 ms 	100.492 ms 	219.117.144.29 219.117.144.41 219.117.144.29
9 	98.776 ms 	98.849 ms 	98.949 ms 	219.117.147.182 219.117.147.190

[Rigus]

When is this going to be over with, I can't do anything!

[MetalVictini]

I can confirm that I've been having issues today. I have had lag and 90ks all over the place.
I'm on PS4 too.

[RaineAmorie]

Constant 90k's for about 4 days now. I get about 7 minutes online before being DC'd again. Instances are impossible, FATEs are miserable at best and Just running around is a struggle with the constant rubber band lag. I'm on PS4, direct lined into my router, which makes this all the more ridiculous. Brynhildr, Primal Data Center.

I'm in VA, USA - Comcast

[Raist]

Constant 90k's for about 4 days now. I get about 7 minutes online before being DC'd again. Instances are impossible, FATEs are miserable at best and Just running around is a struggle with the constant rubber band lag. I'm on PS4, direct lined into my router, which makes this all the more ridiculous. Brynhildr, Primal Data Center.

I'm in VA, USA - Comcast

Sounds a lot like the usual suspects.... (note these images will update periodically as the maps get archived)

https://downdetector.com/status/playstation-network


There's lots of tweets about PS3/4 problems at the source page for the map... PSN itself has been having big problems the last week or so. It's nothing unusual... been happening since PS4 launched. But to add insult to injury, the last firmware is knackered up pretty bad too on top of it (they announced Tuesday a new one is in the works to resolve a lot of issues).

And then there's the typical routing issues that are likely coming into play as well. Comcast subscribers throughout the northeast have been having issues:

https://downdetector.com/status/comcast-xfinity




More on the general topic of this thread though, keep in mind that internet usage has been on a steady and fast increase since late Spring/Early Summer as well. Akamai tracks a lot of statistics on web usage:

October peaks: over 170 Billion hits/sec on 10/28, over 215 Billion streams on 10/31. Compare that to the peaks in April: 35 Billion hits/sec on 4/05 and 76 Billion streams on 4/23.

Here are some direct links to some of the tools available at the same Akamai page I linked for those stats:
http://www.akamai.com/html/technology/dataviz1.html - Real Time web monitor. At 10 AM Eastern on a Saturday morning, global usage is up 29%--UK seems to be highest on usage. Real-time latency indexes to specific points are showing a 2x to 5x rise over their average in 3 key US areas they monitor in the US. The UK is showing 3x-10x, and Asia is registering 8x-10x

http://www.akamai.com/html/technolog...try/index.html - Net Usage by Industry. Can filter by type of traffic, as well as by region. Retail is currently showing +35% globally, Broadcasting is up 57%, Gaming is up 17%, Media/Entertainment is up 32%, Social Media is up 53% - that's global stats at 10:20 AM Eastern time on a Saturday morning. All of those numbers remain on the plus side even when you filter down to just North America---and the West Coast still hasn't even cranked up yet either.

Our infrastructure is just limping along trying to deal with all the cord cutters and other factors steadily increasing our dependency on the internet in general. Need to hold our ISP's accountable to enhance their peering/transit agreements to address all the congestion in our routes. It's not just speculation either.. it's a well known fact in the industry. Both Level3 and TATA have been going after the regulators for years trying to get things addressed. In the last year, Level3 has begun posting on these issues on their blog... hoping to raise awareness of the different problems to put pressure on the powers that be to actually DO something about them. Here are a few articles that may help people gain a better understanding on what is going on:

"Chicken" | A Game Played as a Child and by some ISPs with the Internet (March, 2014)
Observations of an Internet Middleman (May, 2014)
Verizon’s Accidental Mea Culpa (July, 2014)
“Not” Neutrality? (Sept., 2014)

Quoting specifically that last one, as it gets to a major point on the issues pretty quickly and directly. Brought over the URL links as well, as they further demonstrate some of what is going on. I would strongly recommend you guys read up on these issues--we need more informed consumers out there putting pressure on these guys, be that with their wallets or by putting pressure on their congressional representatives and/or the regulatory commissions. WE can and NEED to demand better from the people we purchase our service from--these problems are NOT SE's responsibility to address, but the people we pay for our internet services.

In early May, my Internet Middleman post described how a tiny number of very large broadband network operators, mostly in the United States, are using their market power to try to extract arbitrary access charges, and in so doing, are degrading the service they sold to their paying broadband customers. They achieve this degradation by refusing to add bandwidth at the interconnect points between their networks and other very large global networks, like Level 3’s. Despite this, some of them claim that they are unconditionally committed to Net Neutrality. They can do this because, as Mike Mooney pointed out, the old Net Neutrality rules had a gaping hole in them: since these rules did not explicitly include Internet interconnection in their scope, they allowed broadband providers to discriminate against third-party Internet traffic by causing bottlenecks at Internet interconnection points – and hurting consumers in the process.

But it is now late September. So what has changed? Well, let us look at three large Local Exchange Carriers (LECs) in the United States. These LECs are telephone companies that built broadband networks on the back of monopoly-funded telephone infrastructure. Over the past six months, the utilization of each interconnection location between their networks and Level 3’s has changed as shown in the following diagram.



Each number shows utilization at one of the interconnection locations in various cities throughout the United States between Level 3 and the LECs. Utilization above 85% indicates the LEC is causing congestion in that city by refusing to add interconnection capacity

This shows a dramatic improvement for LEC1 and LEC3, but a continued degradation for LEC2. You might say that it’s good news overall. But if you value an open Internet underpinned by a dynamic competitive environment, you may have a different opinion.

And that’s because the reason the interconnect utilization between Level 3 and LEC1 and LEC3 improved is that these LECs forced Netflix to pay them to interconnect directly with them. And as Netflix CEO Reed Hastings has pointed out several times, Netflix didn’t do that because they were taking advantage of a highly competitive Internet marketplace. They did it because they had no choice: all third-party content that LEC broadband users want to see eventually has to go through LEC interconnection points. When the LEC tries to turn these interconnection points into Internet tollbooths there is no alternate path for the content to take to reach the consumers.

How long will it be before LEC2 degrades the quality of service to their end customers to the point that Netflix is forced to pay them too? And how can LEC2 promise a new 1Gbps broadband service even though it is refusing to allow content that its consumers have requested into its network? In fact, some of their launch cities are also where the interconnect locations are severely congested with 97% utilization. Locations where LEC2 seems happy to simply discard Internet content that their customers have requested, for hours and hours every day. Locations where download speeds for such third-party content cannot possibly get close to 1Gbps – or other “high-speed” services they have sold to their customers.

Level 3 and other Internet content providers are not afraid of competition. The Internet needs Net Neutrality and fair and equitable interconnection to continue to grow and thrive. But what broadband providers are offering instead is “Not” Neutrality: a competitive distortion made possible by the monopoly control they have over access to their customers. These broadband providers are willing to degrade the performance of the service they sell to their customers to extract arbitrary access charges, discriminate against third-party Internet content and harm competition.

We have made concrete proposals (see our previous blog post) to ensure LECs and other broadband providers actually make available the Internet access bandwidth they have already sold to their consumers at interconnection points without congestion and without arbitrary access charges. Consumers should expect no less from their broadband providers.

[Wilbert]

9000 error now. Can't stay logged in for more then 5 sec... before it boots me.

[BookShonen]

This is absolute insanity. Starting a few days back I can no longer stay logged on for more than 5 minutes at a time before getting 90k error. It's like the game runs on a timer and proceeds to boot me no matter what I do. I live in Europe, on Chaos datacenter playing on PC.

[tykeisha]

been experiencing issue for the last 4 hours from about 15:30 (GMT) playing US excalibur being thrown off line constantly with error 9000 or error 2002. lost a lot of dungeons in the process now cant play for more than about `15 minutes without crashing. on each occasion i do reboot route pc etc.

using a pc have a 120mb www internet connection