Forum Discussion

Seasoned Ace

6 years ago

Tomorrow I have my routing checked by my ISP

So we will see if my gripes are warranted. I mean we already know their netcode is sub par according to the 3 analysis done by BattleNonSense (Chris) but whatever. I am going out of my way for the ...

discussion

EA_Blueberry

Community Manager

6 years ago

@GRiPSViGiL

Keep us updated. 👍

@Flashshark1980

Do you know if you have Killer Control Center? Check out these posts if you're rubberbanding or lagging at all on PC.

GRiPSViGiL

Seasoned Ace

6 years ago

@EA_Blueberry My NICs are Intel but i found that during my TSing.

Killtheism
6 years ago
Check out the difference between Iowa 3 and Iowa 4, from Minnesota in this screenshot. The game tells me they have the same ping (42), tracert says otherwise. 110 ping to Iowa 4 wtf is going on here, that's the same ping the game tells me I get to London.
- Killtheism
  6 years ago
  So I can't edit posts I guess. I bothered to geolocate the supposed "Iowa - CGE 4" IP I was connected to and I got. What.
  109.169.71.216 United Kingdom England Milton Keynes
  *Oh nice It's letting me edit again. There is something seriously wrong with the data center selection. I've restarted and chosen multiple data centers and it keeps connecting me to the wrong server. Currently trying to get back to Iowa 3 and now I'm in Dallas...
- GRiPSViGiL
  Seasoned Ace
  6 years ago
  @Killtheism Run a pathping to those IPs. I would be interested to see the packet loss of those routes.
  
  I attached the pathping stats of 2 of the servers one with 15 ping and the other usually at 45 for reference. I used the UOTrace tool EA provides but you can run pathping from the CMD opened as an admin.
  Salt Lake 107.182.233.168.txt2 KB
  OR1 52.40.240.176.txt3 KB
  - GRiPSViGiL
    Seasoned Ace
    6 years ago
    So Frontier has replaced my ONT and a card at the HUB I forget what he called it. He wasn't able to run any routing tests as I thought he was. I have run the pathping and still get 100% loss in a ton of hops for my Portland DC routes. I am going to play and let it marinate until I shake their tree again. I suspect this won't fix my issue but should fix some of the random outages I occasionally had.
    
    The real problem still looks to be routing from Frontier (my ISP) to ZAYO which gets me to the AWS APEX servers. Not sure how Frontier will handle that but it is my next step to get this shiz straightened out.