[PC] We will be entering into maintenance on 7/23 at 7am PDT, and have an expected downtime of approx. 4 hours. For details, visit the following thread: http://bit.ly/2Ocm9O4

Status Update and Community Call-to-Action Regarding Recent Increase in Lag-Related Incidents

1468910

Comments

  • kubitoidkubitoid ✭✭✭✭✭
    LesbianVi wrote: »
    on BnS people from UK, Germany got 300 ms ping, what the heck is happening :anguished:
    its curse for ip block
  • I Came back after a few Months and the lagg is very noticeable. Used to get 70ms and now above 300ms and I live in seattle. EME I'm sure you can relate?
  • LesbianViLesbianVi ✭✭✭✭✭
    Jeszalin wrote: »
    I Came back after a few Months and the lagg is very noticeable. Used to get 70ms and now above 300ms and I live in seattle. EME I'm sure you can relate?

    All games are lagging, EME changed 3 ISP so far :anguished: well, we haven't had outage and heavy spikes we had before, so in this case we are hopeful that they might find a better solution.
  • ElinUsagiElinUsagi ✭✭✭✭✭
    edited July 2017
    Jeszalin wrote: »
    I Came back after a few Months and the lagg is very noticeable. Used to get 70ms and now above 300ms and I live in seattle. EME I'm sure you can relate?

    I live more than 1k miles away and have 80-120 ms.

    Q6201ri.jpg

    How ever I have to acknowledge that ping has been unstable from several days.

    peicKeN.jpg

    If you live nearer than me and have higher ping won't you think that your problem is not EME but something else the problem?
  • I can confirm insane "300ms" ping from greece i am uninstalling and bye bye tera. the sound effects from fps games and lineage 2 turned me off really quick .
  • Moscow - 160-175 my normal. Last few days spikes but we also have effing rains and wind. Anyway it is waaaay less than was in times of Anniversary. And no disconnects btw. Before had a lot.
  • So much desync! So much lags and spikes- INSANE! I changed 3 providers, I asked in the guild and all say me that IOD UNDOABLE on CH! 180-1500! I have 90% of white numbers! Before last maintance it was 90% crits!
    What has happened?
  • SocateKunSocateKun ✭✭
    edited July 2017
    Event+outdated server hardware +bad ISP= Tera.
    They did change ISP,worse then Zayo, I think they are trying to cut the costs down.

    Edit: Did I mention last night I had 1,2 sec ping, 20-30 sec chat lag and 20-30 sec UI lag?
  • 66ECX7NAN766ECX7NAN7 ✭✭✭✭
    Red ping during rally quest today, could hardly do anything.
  • feazesherofeazeshero ✭✭✭
    edited July 2017
    Yesterday around 9 pm eastern time, ping was about 150 ms higher than what I usually have and lasted for about 30-40 minutes.It then returned back to normal for the rest of the night, so thought that was just a temporary thing. As of this writing now, it's been happening again right now (as of 9:38 pm eastern) where the ping is about 100-150 ms higher. This reminds me when during ninja patch the horrible lagging occurred for 30 min-1 hour for certain part of the day (evening eastern time) and then would go back to normal. When running a trace, issue shows to be from the provider (qwest). Also I was not the only person to experience this yesterday, many other ppl in game experienced such a change for that time.
  • OK so I did a trace route and pulled the location from server location to server location,this is my case, but GM's should look @ this since its BAD in like really bad.I'll just put how my peering goes from city to city,server to server:
    Bucharest -> Frankfurt main->Frankfurt out server-> New York in server->New York->New York->Denver->St Louis->St Louis->St Louis->St Louis->St Louis->Seattle
    I see something really WORNG here the peering is a, how brits use to say, utter mess of a peering problem on US part.
    Fallowing servers have ping spikes and maintain the high ping
    206.28.100.245
    204.70.196.241
    206.28.101.165
    64.37.205.6 this one takes the cake jumping to 500ms and above
    208.67.49.150 EME server 100% packet loss.
  • edited July 2017
    SocateKun wrote: »
    Bucharest -> Frankfurt main->Frankfurt out server-> New York in server->New York->New York->Denver->St Louis->St Louis->St Louis->St Louis->St Louis->Seattle
    Post your actual traceroute, but the servers aren't in Seattle, they're in Chicago. I also highly doubt they go through Denver.

    The "100% packet loss" to the EME server you listed is because that server doesn't respond to ping requests. You should do a traceroute to diag.enmasse.com.

    And even it it were being routed the way you claim, the GMs can't do anything about the way the interconnects decide to route traffic; it's deterministic based on the various metrics used to route traffic over the Internet. They could try to switch to a different provider, but there's no guarantee it'll be better than the current one.
  • @counterpoint diag.enmasse.com has the same route only 1 st louis is missing
    diag.nemasse.com is in Seattle
  • SocateKun wrote: »
    @counterpoint diag.enmasse.com has the same route only 1 st louis is missing
    diag.nemasse.com is in Seattle

    No, it's in Chicago. If you are looking up the registration address of the IP address, this is not an accurate indicator of where it is actually used. Your traceroute will show you the hops along the way, and their names indicate the location of the hop.

    For example, the last Savvis hop before entering the datacenter (at least for me) is:
    hr3-xe-8-0-0.elkgrovech3.savvis.net

    This is the CenturyLink (Cyxtera) Elk Grove CH3 datacenter in Chicago.

    If you post your full traceroute, it will help to explain the path your connection is actually taking.
  • @counterpoint
    Address type IPv4
    Hostname hr3-xe-8-0-0.elkgrovech3.savvis.net
    ASN 3561 - CENTURYLINK-LEGACY-SAVVIS - Savvis
    ISP Savvis
    Timezone America/Chicago (UTC-5)
    Local time 08:30:03
    Country United States United States
    State / Region Missouri
    District / County Saint Louis County


    Target Name: diag.enmasse.com
    IP: 208.67.49.180
    Date/Time: 15.07.2017 16:29:56 to 15.07.2017 16:30:54

    Hop Sent Err PL% Min Max Avg Host Name / [IP]
    1 24 0 0,0 1 1 1 [10.0.0.1]
    2 24 0 0,0 2 2 2 [10.30.0.81]
    3 24 0 0,0 1 5 1 br01.bucuresti.rdsnet.ro [213.154.124.94]
    4 24 0 0,0 28 30 28 [83.217.231.5]
    5 24 0 0,0 28 34 28 ae-12.r24.frnkge08.de.bb.gin.ntt.net [129.250.3.194]
    6 24 0 0,0 114 129 116 ae-4.r25.nycmny01.us.bb.gin.ntt.net [129.250.2.4]
    7 24 0 0,0 111 112 111 ae-2.r07.nycmny01.us.bb.gin.ntt.net [129.250.3.98]
    8 24 0 0,0 116 142 118 ae-0.centurylink.nycmny01.us.bb.gin.ntt.net [129.250.8.14]
    9 24 0 0,0 112 114 112 63-235-40-42.dia.static.qwest.net [63.235.40.42]
    10 24 0 0,0 110 117 110 cr1-xe-10-0-1.jfk2.savvis.net [206.28.99.157]
    11 24 0 0,0 140 144 142 cr1-te-0-1-0-1.chd.savvis.net [206.28.100.233]
    12 24 0 0,0 139 162 139 hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
    13 24 0 0,0 140 142 140 [64.37.205.6]
    14 24 0 0,0 139 139 139 [208.67.49.180]

    If you didn't know static IP have geolocation
    Below the accurate location of the server you said is Chicago, pulled from 5 different geolocation,unless EME gives exact address like Wargameing EU does with the server IP you still run in circle for nothing cause US peering is done like dialup.
    204.70.198.73
    whois
    Savvis (SAVVI-3)
    route
    204.70.0.0/15
    bgp
    AS3561
    asname
    SAVVIS-AS SAVVIS-AS3561
    location
    Chesterfield, United States
    ptr
    hr3-xe-8-0-0.elkgrovech3.savvis.net
    a
    204.70.198.73
Sign In or Register to comment.