The Elder Scrolls Online

Maintenance for the week of October 12:
• PC/Mac: NA and EU megaservers for maintenance – October 12, 6:00AM EDT (10:00 UTC) – 8:00AM EDT (12:00 UTC)
• Xbox One: NA and EU megaservers for maintenance – October 14, 6:00AM EDT (10:00 UTC) – 9:00AM EDT (13:00 UTC)
• PlayStation®4: NA and EU megaservers for maintenance – October 14, 6:00AM EDT (10:00 UTC) – 9:00AM EDT (13:00 UTC)
The Markarth DLC and Update 28 base game patch are now available to test on the PTS! Read the full patch notes here: https://forums.elderscrollsonline.com/en/categories/pts/

PC/NA Server routing help

Leave a Reply
SirDopey
SirDopey
✭✭✭✭✭
✭
Hey, so I did a quick search and couldn't find the answers I was looking for so hoping someone here can help.

Getting a worse ping on my 90mbs connection than I do on the farm with an 8mbs connection so I've assumed there's routing issues with my ISP. They have agreed to provide custom routing for me but I need to supply the appropriate server addresses for them. Can anyone give me the information I need to pass on to them if I'm based in Qld, Australia?
NA PC | AD
xx Doc Holliday xx
Quote
  • Sigtric
    Sigtric
    ✭✭✭✭✭
    ✭✭✭✭✭
    198.20.198.110 for the PC/NA server.

    Make sure you look at this too - it may just be a matter of differences in your router at each location. https://help.elderscrollsonline.com/app/answers/detail/a_id/1133/~/what-ports-do-i-need-to-open-for-the-elder-scrolls-online
    <Skål> [PC/NA]- An End Game Content Guild for Everyone
    Stormproof: Vibeke - 50 EP mDragonknight | Savi Dreloth - 50 EP Magsorc | Sadi Dreloth - 50 EP Magblade | Sigtric Stormaxe - 50 EP Stamsorc | Valora Dreloth - 50 EP Magplar | Sigtric the Unbearable 50 EP Stam Warden
    Scrub: Chews-on-Beavers - 50 EP DK Tank | Vera the Wild - 50 EP magicka Warden | Sigtric the Axe - 50 EP Dragonknight Crafter | Sigtric the Blade - 50 EP Lost Nightblade | Sigtric the Savage - 50 EP magicka Templar | Vibeka Shadowblade - 50 Ep Stealthy Ganky Nightblade |

    Show Me Your Dunmer
    Quote
  • PlagueSD
    PlagueSD
    ✭✭✭✭✭
    ✭
    Yep, just do a pathping 198.20.198.110 and let it run. It'll do a traceroute and then run 100 pings to each hop to check for packet loss. It will take almost 5 mins to run while it's doing it's thing...Should return something like below when done:
    Tracing route to 198.20.198.110 over a maximum of 30 hops

    0 [REMOVED]
    1 [REMOVED]
    2 [REMOVED]
    3 68.6.11.204
    4 68.1.1.199
    5 ae-25.a01.snjsca04.us.bb.gin.ntt.net [129.250.192.117]
    6 ae-2.r01.snjsca04.us.bb.gin.ntt.net [129.250.2.49]
    7 ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
    8 ae-7.r11.snjsca04.us.ce.gin.ntt.net [165.254.191.158]
    9 a209-200-184-202.deploy.static.akamaitechnologies.com [209.200.184.202]
    10 a209-200-184-205.deploy.static.akamaitechnologies.com [209.200.184.205]
    11 * * *
    Computing statistics for 250 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 [REMOVED]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% [REMOVED]
    3/ 100 = 3% |
    2 123ms 3/ 100 = 3% 0/ 100 = 0% [REMOVED]
    0/ 100 = 0% |
    3 109ms 9/ 100 = 9% 6/ 100 = 6% 68.6.11.204
    0/ 100 = 0% |
    4 118ms 7/ 100 = 7% 4/ 100 = 4% 68.1.1.199
    0/ 100 = 0% |
    5 125ms 5/ 100 = 5% 2/ 100 = 2% ae-25.a01.snjsca04.us.bb.gin.ntt.net [129.250.192.117]
    0/ 100 = 0% |
    6 116ms 3/ 100 = 3% 0/ 100 = 0% ae-2.r01.snjsca04.us.bb.gin.ntt.net [129.250.2.49]
    0/ 100 = 0% |
    7 142ms 3/ 100 = 3% 0/ 100 = 0% ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
    0/ 100 = 0% |
    8 133ms 3/ 100 = 3% 0/ 100 = 0% ae-7.r11.snjsca04.us.ce.gin.ntt.net [165.254.191.158]
    2/ 100 = 2% |
    9 124ms 5/ 100 = 5% 0/ 100 = 0% a209-200-184-202.deploy.static.akamaitechnologies.com [209.200.184.202]
    1/ 100 = 1% |
    10 126ms 6/ 100 = 6% 0/ 100 = 0% a209-200-184-205.deploy.static.akamaitechnologies.com [209.200.184.205]

    Trace complete.
    Edited by PlagueSD on October 13, 2017 6:32AM
    Quote
  • SirDopey
    SirDopey
    ✭✭✭✭✭
    ✭
    Okaaayy. So I'm on mac (don't hate on me) so have to do a trace route which I'm pretty sure is the same thing. this is what it spits out.

    1 mydevice (192.168.1.1) 3.401 ms 2.925 ms 1.919 ms 2.118 ms 2.933 ms 1.907 ms * 2.360 ms 1.829 ms 1.971 ms 1.967 ms 1.971 ms * 4.024 ms 2.861 ms 2.967 ms 2.943 ms 2.030 ms * 2.376 ms (15% loss)
    2 103-217-164-57.myrepublic.net (103.217.164.57) 21.284 ms 22.222 ms 20.843 ms 20.901 ms 21.004 ms 21.126 ms 22.216 ms 21.820 ms 20.922 ms 21.264 ms 21.596 ms 29.006 ms 21.060 ms 21.077 ms 20.980 ms 23.020 ms 20.644 ms 21.203 ms 31.020 ms 25.602 ms (0% loss)
    3 asn9310.bdr04.syd03.nsw.vocus.net.au (49.255.206.106) 22.833 ms 22.660 ms 22.766 ms 24.133 ms 22.820 ms 24.005 ms 22.882 ms 22.949 ms 23.934 ms 23.187 ms 22.783 ms 23.019 ms 27.645 ms 23.471 ms 22.960 ms 22.847 ms 22.886 ms 23.417 ms 23.575 ms 24.735 ms (0% loss)
    4 119.225.36.102 (119.225.36.102) 21.638 ms 21.344 ms 21.026 ms 22.469 ms 21.531 ms 21.825 ms 20.742 ms 20.825 ms 21.808 ms 22.840 ms 26.348 ms 23.565 ms 22.318 ms 27.121 ms 21.623 ms 25.917 ms 21.447 ms 21.689 ms 21.845 ms 21.514 ms (0% loss)
    5 119.225.36.101 (119.225.36.101) 22.378 ms 23.498 ms 23.070 ms 38.271 ms 22.585 ms 23.303 ms 22.897 ms 25.347 ms 24.513 ms 23.557 ms 23.159 ms 22.733 ms 23.144 ms 23.028 ms 23.034 ms 23.008 ms 22.776 ms 23.317 ms 22.647 ms 23.032 ms (0% loss)
    6 * * * * * * * * * * * * * * * * * * * * (100% loss)
    7 59.154.18.10 (59.154.18.10) 23.601 ms 24.235 ms
    59.154.18.12 (59.154.18.12) 23.189 ms
    59.154.18.6 (59.154.18.6) 23.400 ms
    59.154.18.8 (59.154.18.8) 29.483 ms
    59.154.18.6 (59.154.18.6) 23.153 ms
    59.154.18.4 (59.154.18.4) 23.237 ms 23.055 ms 24.069 ms
    59.154.18.6 (59.154.18.6) 23.228 ms
    59.154.18.14 (59.154.18.14) 23.091 ms 23.698 ms
    59.154.18.4 (59.154.18.4) 23.596 ms
    59.154.18.6 (59.154.18.6) 23.657 ms
    59.154.18.12 (59.154.18.12) 23.058 ms
    59.154.18.4 (59.154.18.4) 24.267 ms 23.269 ms
    59.154.18.6 (59.154.18.6) 22.906 ms
    59.154.18.8 (59.154.18.8) 27.946 ms
    59.154.18.14 (59.154.18.14) 24.213 ms (0% loss)
    8 ix-xe-10-2-1-40.tcore1.tv2-tokyo.as6453.net (180.87.180.73) 204.916 ms 204.183 ms 204.084 ms 205.931 ms 205.094 ms 204.728 ms 204.326 ms 204.540 ms 204.759 ms 205.867 ms 318.984 ms 204.885 ms 204.565 ms 204.925 ms 205.160 ms 204.793 ms 205.020 ms 205.213 ms 204.838 ms 305.947 ms (0% loss)
    9 if-ae-2-2.tcore2.tv2-tokyo.as6453.net (180.87.180.2) 203.961 ms 204.339 ms 203.970 ms 197.362 ms 195.412 ms 196.123 ms 204.830 ms 196.857 ms 202.901 ms 196.403 ms 210.865 ms 204.887 ms 208.627 ms 194.840 ms 249.655 ms 195.540 ms 195.192 ms 203.555 ms 205.139 ms 195.090 ms (0% loss)
    10 180.87.181.42 (180.87.181.42) 234.249 ms 306.416 ms 307.262 ms 307.005 ms 307.134 ms 206.563 ms 207.491 ms 302.793 ms 307.069 ms 307.183 ms 307.212 ms 307.070 ms 306.912 ms 307.287 ms 307.279 ms 307.208 ms 307.120 ms 307.091 ms 307.308 ms 307.169 ms (0% loss)
    11 a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 203.334 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 199.566 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 201.672 ms 201.263 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 199.445 ms 199.659 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 201.261 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 198.769 ms 199.498 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 201.224 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 203.176 ms 204.150 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 206.520 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 202.376 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 205.156 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 203.124 ms 204.289 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 204.785 ms
    a72-52-56-200.deploy.static.akamaitechnologies.com (72.52.56.200) 203.742 ms
    a72-52-56-192.deploy.static.akamaitechnologies.com (72.52.56.192) 204.475 ms (0% loss)
    12 a72-52-56-199.deploy.static.akamaitechnologies.com (72.52.56.199) 204.055 ms 204.154 ms
    a72-52-56-207.deploy.static.akamaitechnologies.com (72.52.56.207) 243.747 ms
    a72-52-56-199.deploy.static.akamaitechnologies.com (72.52.56.199) 306.032 ms 203.607 ms
    a72-52-56-207.deploy.static.akamaitechnologies.com (72.52.56.207) 206.129 ms
    a72-52-56-199.deploy.static.akamaitechnologies.com (72.52.56.199) 204.322 ms
    a72-52-56-207.deploy.static.akamaitechnologies.com (72.52.56.207) 204.669 ms 204.494 ms 204.849 ms
    a72-52-56-199.deploy.static.akamaitechnologies.com (72.52.56.199) 204.433 ms 204.227 ms
    a72-52-56-207.deploy.static.akamaitechnologies.com (72.52.56.207) 204.933 ms
    a72-52-56-199.deploy.static.akamaitechnologies.com (72.52.56.199) 203.222 ms
    a72-52-56-207.deploy.static.akamaitechnologies.com (72.52.56.207) 205.125 ms 204.552 ms
    a72-52-56-199.deploy.static.akamaitechnologies.com (72.52.56.199) 212.186 ms 204.144 ms
    a72-52-56-207.deploy.static.akamaitechnologies.com (72.52.56.207) 204.524 ms 297.594 ms (0% loss)
    13 * * * * * * * * * * * * * * * * * * * * (100% loss)
    14 * * * * * * * * * * * * * * * * * * * * (100% loss)
    15 * * * * * * * * * * * * * * * * * * * * (100% loss)

    Dunno why it doesn't find its way to the server when I can log in and play the game, going out to the farm tomorrow so will do one there to see what my ISP's routing there says
    NA PC | AD
    xx Doc Holliday xx
    Quote
  • SirDopey
    SirDopey
    ✭✭✭✭✭
    ✭
    adding to that, in game my /latency seems to be hovering around the 260 - 270 mark
    NA PC | AD
    xx Doc Holliday xx
    Quote
  • Banana
    Banana
    ✭✭✭✭✭
    ✭✭✭✭✭
    SirDopey wrote: »
    adding to that, in game my /latency seems to be hovering around the 260 - 270 mark

    Your always going to have a rubbish ping being so far from the server. Im in qld to but get 330+.
    Edited by Banana on October 13, 2017 1:26PM
    Quote
  • Taylor_MB
    Taylor_MB
    ✭✭✭✭✭
    ✭
    Banana wrote: »
    SirDopey wrote: »
    adding to that, in game my /latency seems to be hovering around the 260 - 270 mark

    Your always going to have a rubbish ping being so far from the server. Im in qld to but get 330+.

    Brisbane, I'm happy with under 350ping.
    PvP Defensive Set Comparison
    Firestarter MagDK 1vX     - build and gamplay!
    LagPlar Ranged Lag Proof(ish) Magplar     - build and gamplay!
    ShadowGaurd MagBlade Group Utility Tank     - build and gamplay!
    Oncoming Storm No-CP 11.6k Ward MagSorc - build and gamplay!
    My YouTube Chanel


    Quote
  • SirDopey
    SirDopey
    ✭✭✭✭✭
    ✭
    Yeah, I'm use to high pings. There's no content in the game that I can't complete with a 340 ping but any opportunity I can get to reduce it I will take.

    Know plenty of Australias with a sub 200 ping so I know based on my download and upload speeds that I can get mine a lot lower yet
    NA PC | AD
    xx Doc Holliday xx
    Quote
  • SirDopey
    SirDopey
    ✭✭✭✭✭
    ✭
    Turning Express VPN on before launching the game shaves about 60 off my in game latency so yeah, definitely routing improvements to be found on my ISP's end
    NA PC | AD
    xx Doc Holliday xx
    Quote
Sign In or Register to comment.