Request for information: ISPs and P2P throttling

-Viacabo
-Brazil
-Aways with error 90000(impossible to play)

- Name of ISP
Telstra BigPond
- Country of Residence
Australia
- When does the problem occur (always, only during specific times?)
Hourly, I timed it to the minute for 6hours once; hourly at 30mins past. Last night it was at 10mins past the hour. but consistent when it is happening.
- Reference number from your ISP, if you raised this matter with them
I havent yet but my ISP are a bunch of fucking muppets and I'm loathed to call their scripted "support" staff.

ok did some tracert to the IP I get connected to when playing ARR :199.91.189.58
I am in TX, USA
this one is straight up from my ISP

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.10.10.1
  2    *        3 ms    1 ms  ben2gw1.texascellnet.com [63.246.232.254]
  3    *        5 ms    2 ms  ben2bh.texascellnet.com [63.246.224.105]
  4    8 ms    3 ms    9 ms  corban1bh.texascellnet.com [63.246.224.33]
  5    6 ms    9 ms    *    corbanrtr.texascellnet.com [63.246.224.1]
  6    6 ms    6 ms    3 ms  216.171.64.1
  7    8 ms    5 ms    6 ms  xc_45-90-171.216.xcnetworks.com [216.171.90.45]

  8    5 ms    5 ms    *    ge-8-29.car2.Dallas1.Level3.net [4.71.171.121]
  9    *        *        *    Request timed out.
 10    45 ms    41 ms    44 ms  4.68.111.102
 11    43 ms    50 ms    43 ms  be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
 12    63 ms    76 ms    67 ms  be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.
217]
 13    *        *        *    Request timed out.
 14    46 ms    40 ms    49 ms  be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42
.10]
 15    53 ms    48 ms    *    be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
 16    49 ms    51 ms    51 ms  38.122.42.34
 17    *        *        *    Request timed out.
 18    55 ms    96 ms    *    192.34.76.2
 19    51 ms    51 ms    52 ms  199.91.189.234
 20    55 ms    52 ms    57 ms  199.91.189.58

Trace complete.

---

now I switch to VPN which allows me to connect to the Montreal data center for ARR from different locations
first I tried was TX

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    8 ms    6 ms    7 ms  10.156.1.1
  2    8 ms    13 ms    7 ms  23.29.126.101
  3    6 ms    9 ms    6 ms  r1-side-from-bc1.inceronetwork.com [192.211.63.5
]
  4    7 ms    7 ms    6 ms  te4-3.ccr01.dfw10.atlas.cogentco.com [38.88.50.1
]
  5    7 ms    7 ms    6 ms  te0-2-0-7.ccr21.dfw01.atlas.cogentco.com [154.54
.86.205]
  6    20 ms    19 ms    19 ms  be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.
217]
  7    28 ms    38 ms    31 ms  te0-7-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.2.234]
  8    44 ms    44 ms    50 ms  be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42
.10]
  9    51 ms    51 ms    55 ms  be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
 10    52 ms    70 ms    54 ms  38.122.42.34
 11    *        *        *    Request timed out.
 12    52 ms    55 ms    53 ms  192.34.76.2
 13    52 ms    65 ms    57 ms  199.91.189.234
 14    69 ms    63 ms    50 ms  199.91.189.58

Trace complete.

---

next one I tried was from Seattle since it's close to canada

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    47 ms    82 ms  103 ms  10.123.1.1
  2    68 ms    48 ms    51 ms  mpdedicated.com [173.192.170.65]
  3    53 ms    52 ms    54 ms  ae12.dar01.sr01.sea01.networklayer.com [67.228.1
18.224]
  4    51 ms    51 ms    55 ms  ae8.bbr02.wb01.sea02.networklayer.com [173.192.1
8.142]
  5    47 ms    49 ms    49 ms  te-3-2.car4.Seattle1.Level3.net [4.71.152.137]
  6    54 ms    48 ms    50 ms  ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]

  7  123 ms  120 ms  114 ms  te0-3-0-16.ccr21.sea02.atlas.cogentco.com [154.5
4.12.25]
  8  130 ms  127 ms  129 ms  be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.
198]
  9  144 ms  140 ms  159 ms  be2126.ccr21.den01.atlas.cogentco.com [154.54.25
.65]
 10  167 ms    *      283 ms  be2128.ccr21.mci01.atlas.cogentco.com [154.54.25
.174]
 11  206 ms  162 ms  162 ms  te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54
.82.142]
 12  178 ms  173 ms  178 ms  be2082.ccr22.yyz02.atlas.cogentco.com [154.54.28
.10]
 13  184 ms  197 ms  207 ms  be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
 14  127 ms  130 ms  129 ms  38.122.42.34
 15    *        *        *    Request timed out.
 16  138 ms  226 ms  149 ms  192.34.76.2
 17  174 ms  135 ms  243 ms  199.91.189.234
 18  130 ms  128 ms  132 ms  199.91.189.58

Trace complete.

---

next up is NY

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    43 ms    47 ms    42 ms  10.102.1.1
  2    48 ms    43 ms    40 ms  vl906-c10-8-b2-1.pnj1.choopa.net [209.222.7.233]

  3    45 ms    49 ms    47 ms  ethernet20-1-br1.pnj1.choopa.net [108.61.2.197]

  4    54 ms    48 ms    48 ms  ae7.ar2.nyc3.us.nlayer.net [69.31.34.77]
  5    42 ms    41 ms    40 ms  ae0-315.nyc41.ip4.tinet.net [199.229.230.93]
  6    49 ms    49 ms    53 ms  xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
  7    55 ms    52 ms    55 ms  xe-4-0-0.mtl10.ip4.tinet.net [141.136.108.190]
  8    50 ms    55 ms    *    ormuco-gw.ip4.tinet.net [216.221.156.110]
  9    56 ms    53 ms    60 ms  192.34.76.2
 10    50 ms    60 ms    49 ms  199.91.189.58

Trace complete.

---

now lets try from California

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    48 ms    49 ms    46 ms  10.180.200.1
  2    47 ms    48 ms    48 ms  50.23.65.1-static.reverse.uk2group.com [50.23.65
.1]
  3    75 ms    48 ms    *    ae0.dar01.sr01.sjc01.networklayer.com [50.23.118
.130]
  4    46 ms    91 ms    46 ms  ae8.bbr01.eq01.sjc02.networklayer.com [173.192.1
8.248]
  5    46 ms    54 ms    46 ms  xe-7-1-0.edge2.SanJose3.Level3.net [4.53.210.9]

  6    50 ms    56 ms    50 ms  ix-11-0.tcore2.SQN-SanJose.as6453.net [209.58.11
6.109]
  7  139 ms  135 ms  142 ms  if-5-2.tcore2.PDI-PaloAlto.as6453.net [64.86.21.
2]
  8  147 ms    *      139 ms  if-2-2.tcore1.PDI-PaloAlto.as6453.net [66.198.12
7.1]
  9  186 ms  206 ms  322 ms  if-1-2.tcore1.NYY-NewYork.as6453.net [66.198.127
.6]
 10  193 ms  137 ms  160 ms  if-11-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
1]
 11  141 ms  210 ms    *    if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.
30]
 12  138 ms  145 ms  166 ms  if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
 13  141 ms  137 ms  141 ms  if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
 14    *        *      185 ms  66.198.96.50
 15  130 ms  136 ms  133 ms  192.34.76.2
 16    *      134 ms    *    199.91.189.234
 17  135 ms  131 ms  132 ms  199.91.189.58

Trace complete.

---

now lets try London

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1  108 ms  112 ms  113 ms  10.124.22.1
  2    *      131 ms  114 ms  2582e38a.rdns.100tb.com [37.130.227.138]
  3  114 ms  112 ms  175 ms  83.170.70.229
  4    *      178 ms  189 ms  te4-5.ccr01.lon18.atlas.cogentco.com [149.14.8.4
1]
  5  112 ms  113 ms  109 ms  te0-0-0-23.ccr21.lon01.atlas.cogentco.com [154.5
4.62.41]
  6  110 ms    *        *    te0-1-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.106]
  7  121 ms  117 ms  123 ms  te0-2-0-5.ccr21.lpl01.atlas.cogentco.com [154.54
.37.173]
  8  193 ms  190 ms  188 ms  te0-2-0-4.ccr21.ymq02.atlas.cogentco.com [154.54
.0.70]
  9  189 ms  185 ms  186 ms  38.122.42.34
 10    *        *        *    Request timed out.
 11  185 ms  188 ms  187 ms  192.34.76.2
 12  189 ms  195 ms  190 ms  199.91.189.234
 13  190 ms  191 ms  187 ms  199.91.189.58

Trace complete.

---

last one I tried to go with Toronto, CA

Code:

---

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    *      46 ms    42 ms  10.120.1.1
  2    41 ms    42 ms    45 ms  184-75-223-65.amanah.com [184.75.223.65]
  3    41 ms    45 ms    41 ms  xe-0-0-1-3602.cr1.tor2.ca.nlayer.net [69.31.143.
109]
  4    47 ms    42 ms    47 ms  ae0-30g.cr1.tor1.ca.nlayer.net [69.31.143.24]
  5    45 ms    42 ms    45 ms  ae2-50.tor10.ip4.tinet.net [199.229.230.89]
  6    49 ms    49 ms    48 ms  xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
  7    49 ms    48 ms    *    ormuco-gw.ip4.tinet.net [216.221.156.110]
  8    50 ms    50 ms    67 ms  192.34.76.2
  9    54 ms    49 ms    50 ms  199.91.189.234
 10    54 ms    50 ms    62 ms  199.91.189.58

Trace complete.

---

very interesting results, noticed the ones that does NOT route through cogentco.com has no time outs, what does this mean? I don't know....maybe some IT guru can tell more on this or maybe even SE network staff....

- Name of ISP -Time Warner (Southern CA)
- Country of Residence - U.S.A.
- When does the problem occur (always, only during specific times?) Always

ISP: Xfinity/Comcast
Country: United States/Michigan
Problem Occur: Only lags during high volume times (Weekends, especially Friday night)

I play this on the PS3 and could not even click start for the longest time then when I set my router to activate DMZ mode I was FINALLY able to log in. Even though I experience lag during those high volume times but it's not THAT bad. Still get to play so I can't complain

ISP: KPN
Country: Netherlands
Problem Occurs: All the time

Game is unplayable because of the 90000 error or 10102 error :(

Baja Broadband
only playable from 12am to 3am
cant play rubber band lag all the time

Comcast
United State, Chicago, Illinois
Rubberbanding; Sometimes during certain instances, especially in Stone Vigil or Praetorium.

Also experienced during Praetorium & Hydra run at late hours, 1- 2 AM CT.

Comcast
United States, Sandy, Utah
Started about 4 hours ago, been leveling up crafting with massive delay between actions (up to 15 seconds for an action to register). Eventually it will get bad enough that I can't load up pages with the game open until it 90ks and I have to restart it to continue playing, in which case everything will be fine for 5 minutes until the process starts over

Comcast
United States
at random times during the day and night

Verizon FiOS
USA, Maryland
Started occurring about every 10-15 minutes on 9/29/2013.

Bredbandsbolaget
Sweden
8-12 p.m. since Saturday

ATT Uverse
United States, Florida
Always since 9/29/13

I cannot play as healer w/ 2-5 seconds lag

Century-link [DSL]
United States, Oregon
Randomly through out the entire day, peak or non peak hours it doesn't seem to matter.

Telenor
Norway
Happens mostly around 5-7pm gmt.

Posting this for my 3 friends. They all have the same ISP, while I live in the same area as them and don't have this problem (My ISP is Altibox).

Been here once before, returning since the issue is even worse as of the last maintenance.

ISP: Road Runner
Location: New York
Time: Always

This is not related to your isp.Its how the server handles information.Square enix is to blame, if you check the other posts about lag you can find out exactly how this horrible lag works.

Name of ISP: BT
Country: UK/Scotland
Time: From 6pm Onwards

Comcast
Northern Virginia

Terrible lag this morning.

Well met. Sadly I have to report that I'm affected by this issue aswell.

- Tyfon
- Sweden
- Since saturday somewhere, pretty much around the clock in intervals several minutes long. (much in the same way as stated in thread numerous times) I also get the 90k.
- Been in contact with ISP, and they should call me back tomorrow after consulting their techies.

I'd like to add that while the others all had their 90k issues and problems logging in during beta/early access/launch I never had anything like this. It all came after your last maintenance before this monday. Now it's unplayable. The worst part isn't the fact that I'm not able to play. The worst part is the fact that I don't know why and I can't seem to get an answer as a paying costumer. Adding to that is ofc the fact that I keep waiting around looking at forum and logging in, to see if that fix is here yet, or atleast any word about what's happening. I spend roughly about six hours today reading the forums and various sites, learning so much about everything network related. Like Peer to peer, packages, routing and tracing. I've done more than my reasonable share of hard work to find a solution for someone who doesn't really get all computer related stuff and has no interest in learning it, other than getting back to Eorzea. Come on now, SE. Make a statement about what we have to do to get this under control, and I for one will do it.

Regards.
Ithrent Threadbare.

-Name of ISP Canal Digital
- Country of Residence Norway
- When does the problem occur (always, only during specific times?) Everynight mainly during 6pm-12am GMT+2 up to 30 second freezing. ISP said they dont throttle.
- Reference number from your ISP, if you raised this matter with them - 01026406

for more refrence
http://forum.square-enix.com/ffxiv/t...27#post1359627

- Name of ISP : Canal Digital (Cable)
- Country of Residence : Norway
- When does the problem occur : Problem occurs more or less every day, from 19:00 (GMT+2 Daylightsavings ON) to 00:00 (GMT+2 Daylightsaving ON). The degree of the problem can vary from day to day, but its there, from very bad,to not SO bad, but still bad.
- Reference number : 01026406 (This ref-nr isnt mine, but from a friend, with the exact same problem, at the exact same time, same ISP)

- Name of ISP : Plus.net
- Country of Residence : England
- When does the problem occur : Not everyday but would say 4/7 days of the week. Around 7-8 GMT+1 will get heavy lag making it unplayable
- Reference number : None given as yet.

- Name of ISP : Comcast
- Country of Residence : US (georgia)
- When does the problem occur : at any given time, random
- Reference number : None given as yet.

The severe fate/group lag did not start until yesterday, but we've been getting random 90k since we starting using the current ISP. Never had these issues with our previous provider, Charter Comm.

Recently, the game has been getting throttle down by my ISP as due to this.

ISP: Comcast Business Class
Location: US (Chicago Area)
Time: During heavy traffic hours
Occurrence: Ever since a week ago

ISP: Comcast
Location: Sacramento
Time: Afternoons and Evenings

- Telia
- Sweden
- Randomly during the day, frequently during peak time. Timing out/disconnected, lagging and package losses (rubberbanding or nothing moves for x amount of seconds)
- Will call tomorrow about this.

- WI-Power
- NM, USA
- All day long, but worse between 11:00am pst - 4:00pm pst.
- Today 10/1/13 the game is unplayable due to lag issues.

Virgin Media
UK

Lag's ALL THE TIME, my ISP do throttle heavily but not 24/7, I dunno whether your server suck, my ISP are throttling me 24/7 or you somehow use a P2P network to run the servers.

But I would appreciate you fixing it, because, frankly, I am having a mediocre experience in what could be an excellent game.

120 pages to this thread and Square has not given any official release details or updates at all.

Pretty awesome ain't it......

http://forum.square-enix.com/ffxiv/t...%28Petition%29

Quote:

---

Originally Posted by Aethingie

Hi all,

As posted elsewhere before, we are investigating issues that might be caused by ISPs classifying FINAL FANTASY XIV: A Realm Reborn as P2P software.

To give us a clearer view on how widespread this issue is, it would be much appreciated if everyone who experienced such issues could post the following information as a reply to this thread:

- Name of ISP
- Country of Residence
- When does the problem occur (always, only during specific times?)
- Reference number from your ISP, if you raised this matter with them

Again, my apologies for the trouble this is causing and thank you for your cooperation!
- Aethingie

---

-Time Warner Cable
- US, New York (like 3 hours from Montreal, go figure)
- Problem occurs primarily during US Prime Times, that's 6 pm EST until about 12:00 pm EST, and then during most of the weekend hours.
- Time Warner Work Order Number: 103070639.

I have run tracert, posted elsewhere, showing massive slowdowns with Cogent Communications (38.122.42.122). Problem is huge lag spikes, where crafting macros often miss, or there's long delays while harvesting. I also see it with large groups of people during FATES, where they run for a period of time, pause for a full second, then sprint, then pause. It's pretty bad. Issue started since launch; however, it's gotten progressively worse lately.

- Frontier Communications FIOS
- Washington State USA
- Always

I have talked with my ISP, but I don't have a ticket number because there doesn't seem to be a problem with my ISP service. And let's be honest here: considering the overwhelming number and variety of responses in this thread so far, this does not appear to be an ISP related issue. I think it's time SE released a public statement.

This is the second time I've come across a widespread issue with this game (first issue was with billing, error 601) that SE has tried to sweep under the rug by NOT releasing a statement in acknowledgement of the problem. I had to go through a third party support call (UltimatePay) to find a work around. That was after waiting 3 hours to talk to SE support who was completely uninformed and of no help. This was not the support reps fault. It was SE not taking the issue seriously, informing their reps and/or releasing a public statement.

Stop leaving your customers in the dark and putting your support reps in a no-win situation. Own up to your problems and be front facing about dealing with them

Quote:

---

Originally Posted by Kellogs4toniee

120 pages to this thread and Square has not given any official release details or updates at all.

---

Hey now, it's only been a MONTH! :)

AT&T
California
630PM-1200

Once again, TATA Communications is dropping packets. Happens a good 2-4 nights a week.

Cox
USA(Arizona)
Happens during prime time a few days a week

COX
Arizona, US
5pm-11pm MST, 2-4 times a week, but consistently since the October 1st maintenance

This issue hit me recently.

-AT&T
-Texas, United States
-Prime time