Results -9 to 0 of 25

Threaded View

  1. #14
    Player
    Raist's Avatar
    Join Date
    Aug 2013
    Posts
    2,457
    Character
    Raist Soulforge
    World
    Midgardsormr
    Main Class
    Thaumaturge Lv 60
    In addition to Enepttastic's post, have to understand that this (as usual) loosk like a routing problem occurring upstream from our localized networks. This is something managed by your ISP, and is affected by your point of origin and the requested destination. Rebooting your network can cause new leases to be assigned, effectively sometimes changing something in your auto-assigned IP config or otherwise correcting an issue with your geolocation---which has been known to resolve issues in the past. It is also sometimes required by your ISP in order for you to download an updated config file from the ISP's TFTP server to address potential issues with your modem and/or their network.

    Basically... the old Microsoft mantra of rebooting your devices can and does have it's place because it is a documented step in the troubleshooting process that has been shown to sometimes work and at times is actually necessary to address issues.

    Back to the OP though, this is something that needs to be addressed by your ISP. you ned to get in touch with no less then their Tier3 people---not the tier1 and tier2's that you will get on the phone when you call in or that come out and check the cables and possibly swap out your modem. That's not to say that you don't have an issue with your network---you may find signs of issues because of out of spec Signal to Noise Ratio (SNR) or other values listed on your modem's signal pages that those guys will need to address. But you have specifically identified the very common issue we've all been dealing with for some time now---a routing issue with our ISP's routing partners. Our ISP's have the enforceable agreements with these third (and sometimes fourth) parties and not SE, so it actually falls to our ISP's to go lean on them to address their problems on our behalf.

    And yes, such an issue can affect a LOT of players at the same time. When PSN goes AWOL like it has been doing more and more often since the launch of the PS4, it potentially affects EVERY console player of this game. OTher games may run just fine because they don't continually check in with PSN like XIV does. Likewise, comparing how LoL, GW2, or WoW is performing against XIV is not an accurate comparison. XIV is hosted in Canada for the NA/EU accounts--they aren't run on state-side servers in New York, LA, Chicago, or Seattle and so may not be affected by routing issues getting into and/or across Canada.

    Important point of fact there... a very large part of the problems stem from getting into and/or across Canada. There are very limited entry points into Canada, as well as a limited number of trunks for getting across Canada. If AT&T, Verizon, Comcast, TWC, etc. all use the same 3 companies for this process and any number of those three get overloaded it can severely knacker up access for a LOT of people at once. This in fact is what is happening---Level3's lines are crapping out, and everyone using their routes through that same corridor are getting hosed.

    [Edit:]
    Just picked up signs of congestion within TWC's own network around Scarborough, Maine as well. Fluctuations from 20's up to around 400ms, with the occasional spikes up over 1 second. Things are just getting out of hand in general up near the border I guess... Northeast is showing it's usual signs for TWC, as well as the other usual areas of Southern California, Texas, Georgia, the Carolinas. Nothing new here... just more of the same oversold markets and under maintained markets we've dealt with for years:



    You can find more maps like this for other services (including PSN and XBL, among others) and a few other ISP's at the downdetector's company pages:
    http://downdetector.com/companies
    (2)
    Last edited by Raist; 06-09-2014 at 07:56 AM.

Tags for this Thread