Euro servers dc's

serraphine
serraphine Posts: 18 Arc User
edited May 2012 in General Discussion
We're having mass DC's at euro servers constantly today.
When trying to log back in the servers show as being down, unable to log in at it.
Many ppl complain about it but it seems to be at euro end only, Americans for example dont have that trouble.
Im just putting it out here hoping there will be taken notice to this.
Post edited by serraphine on

Comments

  • mulee
    mulee Posts: 2 Arc User
    edited May 2012
    Same here, alrdy got killed a vew times because of those DC's. DC is like a smart meanie person, it will come while killing a bossb:cryb:angry
  • SylenThunder - Twilight Temple
    edited May 2012
    Here, take this and do something with it...

    Common reasons that you can't connect to the servers, experience disconnects, or just have lag in general...

    1. You don't have the three .exe files for the client set to run as administrator.
    2. You don't have the game directory set as an exception in your security softwares.
    3. Your network adapter driver is out of date and needs to be refreshed.
    4. Your local area network settings are improperly configured.
    5. You have more than one firewall and don't realize it.
    6. Your firewall settings are too strict. (Very common with ZoneAlarm and Commodo firewall.)
    7. Your router is configured improperly.
    8. you have a bad network cable.
    9. You're using a wireless network connection. (Which leads to another huge list.)
    10. You have a lot of traffic on your local network that is bogging your router/modem down.
    11. There's a fault in your router.
    12. There's a fault in your modem.
    13, You have a bad phone cord plugged into your modem.
    14. There's an issue with your house wiring.
    15. There's an issue with your outside wiring.
    16. A squirrel chewed on your phone line at the pole and it's raining. (I've had this happen personally.)
    17. A switch/router at the CO for your ISP is having an issue.
    18. One of the many hubs between you and PWI is having an issue. (most common)
    19. There is heavy sunspot activity. (has happened within the past two years)
    20. There's a regional router outage. (Has happened several times, most recently just a couple of weeks ago.)

    That's just a few. The more details you give, the better I can narrow it down and tell you what the issue is.

    Also, post a copy of a traceroute to the server.
    [SIGPIC][/SIGPIC]
  • MistaBwanden - Sanctuary
    MistaBwanden - Sanctuary Posts: 2,803 Arc User
    edited May 2012
    2x drops as compensation.
  • RageKill - Lost City
    RageKill - Lost City Posts: 297 Arc User
    edited May 2012
    12x drops as compensation.

    b:laugh
  • condo2009
    condo2009 Posts: 406 Arc User
    edited May 2012
    they said MASS dc, not i'm am dc'ing. MASS= server side. save the copy paste for something usefull
  • LeCookie - Lothranis
    LeCookie - Lothranis Posts: 1 Arc User
    edited May 2012
    I've also noticed that, but it was more like two days ago not yesterday. Bunch of friends on there also dc'd and had the same problem so it has to be the server's end x.x
  • SylenThunder - Twilight Temple
    edited May 2012
    condo2009 wrote: »
    they said MASS dc, not i'm am dc'ing. MASS= server side. save the copy paste for something usefull
    Remember when we had the problem with mass DC's on the East coast servers a while back?

    Guess what, it wasn't the server, it was a router hub in New York.

    Or the time when we had massive lag and Mass DC's on the west coast servers just a few months ago?

    Guess what, it wasn't the servers then either, it was a whole lot of hubs being overloaded because of traffic re-routing due to an earthquake in the greater LA area.

    Traceroutes showed that.

    It had nothing to do with the servers.

    Why don't you keep your mouth shut until you can say something useful that has supporting evidence. (You know, like a traceroute to the server when you're having an issue.)
    [SIGPIC][/SIGPIC]
  • condo2009
    condo2009 Posts: 406 Arc User
    edited May 2012
    because if it's a hub on the way to or from pwi server, it is STILL server side moron
  • MistaBwanden - Sanctuary
    MistaBwanden - Sanctuary Posts: 2,803 Arc User
    edited May 2012
    24.5x compensation.
  • ZoracGallant - Raging Tide
    ZoracGallant - Raging Tide Posts: 1,624 Arc User
    edited May 2012
    condo2009 wrote: »
    because if it's a hub on the way to or from pwi server, it is STILL server side moron

    lol no

    It's not your side and it's also not a problem with the server so it's not server side its a routing problem
    [SIGPIC][/SIGPIC]

    Want to solve alot of my problems? On your computer Click - Start - now click - Run - now type - cmd - now type - format c: - If you are using Windows Vista or 7 please be sure you run as administrator.
  • SylenThunder - Twilight Temple
    edited May 2012
    condo2009 wrote: »
    because if it's a hub on the way to or from pwi server, it is STILL server side moron

    Wow you really don't get it.
    It's a hub IN BETWEEN you and the server, which IS NOT server side.
    Who's the moron here?

    Here's an example, for those of you that are still being a bit dense....

    E:\>tracert pwieu2.de.perfectworld.eu

    Tracing route to pwieu2.de.perfectworld.eu [69.174.40.91]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.15.1 My Router
    2 1 ms <1 ms <1 ms 192.168.1.254 My Modem
    3 7 ms 7 ms 7 ms 76-250-208-3.lightspeed.livnmi.sbcglobal.net [76.250.208.3] My ISP's regional hub. (I do not use a CO because I have fiber.)
    4 * * * Request timed out. A hub in Ohio that has disabled ping responses.
    5 10 ms 9 ms 9 ms 75.26.64.82 A hub on the path to the server
    6 8 ms 8 ms 8 ms 12.83.32.133 Another hub on the path to the server.
    7 16 ms 15 ms 16 ms gar1.clboh.ip.att.net [12.122.133.105] Another hub... you get the idea...
    8 15 ms 15 ms 16 ms ge6-37-1000M.ar2.DAL2.gblx.net [64.208.110.161] Each one of these hubs is a possible point of failure for your signal.
    9 147 ms 148 ms 115 ms 64.213.76.230 Hub BEFORE the PWE ISP
    10 * * * Request timed out. PWE's ISP
    11 * * * Request timed out. PWE's hub, then firewall, router, bridges, load balancers, ect. ect. ect.

    You won't ever get a response from PWE's ISP or past that for security reasons.

    And that's a decent connection. in-game ping is about 177ms on that server now.
    [SIGPIC][/SIGPIC]