Talk:Americas region realm list by datacenter

Links still need to be added for most of the 222 servers. I will revisit this when I am less tired. :) Nandini 10:09, 6 October 2007 (UTC)

Thanks for this list, I've been looking for a new realm for a while and wanted a list that actually shows where the servers are, not where they "claim" to by arbitrary time-zone. pzykotic

You're welcome, I'm glad someone else has found it useful! Nandini

There is no 'Oceanic' time zone. Oceanic is a class of realm describing which are of the planet Blizz are attempting to serve via these realms. They use AEST (Australian Eastern Standard Time) which is UTC/GMT+10, or +11 during summertime. Further, I suggest the designators used here for US time zones are fairly pathetic. For example, it says Eastern - but to an Aussie, Eastern time is Oceanic. Anyone have any thoughts as how the page ould be edited to provide this kind of useful info? Use the real timezone names? -Normal 21:16, 22 January 2008 (UTC)

When I originally created the page, I simply borrowed the time zone designators found on other pages, so I'm glad to have some feedback from someone from outside the U.S. Would changing the designations to "U.S. Eastern Time, U.S. Central Time, U.S. Mountain Time, U.S. Pacific Time, Aust. Eastern Time" be easier to follow? Nandini 22:29, 12 February 2008 (UTC)

New Datacenter

It appears that the Ruin and Vindication battlegroups have been relocated to a datacenter in Washington, DC. Can anyone else confirm this? Nandini (talk) 17:55, September 17, 2009 (UTC)

I did some reasearch and indeed, those two battlegroups appear to have been moved. I updated the article accordingly.Nandini (talk) 18:34, September 17, 2009 (UTC)

No Data Centres have moved. Ruin & Vindication are still located in Dallas - they're just in a SEPARATE Data Centre than Rampage & Shadowburn. This was confirmed by a GM about 2 weeks ago when Ruin & Vindication were experiencing login issues. Resa1983 (talk) 19:17, September 17, 2009 (UTC)

Found the problem - you didn't run netstat while logged into one of the servers in that Data Centre. That ENTIRE data centre's IP addresses have changed. Instead of being 206.16.235.x, they're now 206.16.23.x - which are located in Dallas, Texas. Reverting your change (sorry). Resa1983 (talk) 19:30, September 17, 2009 (UTC)

Sorry about that, I relied on the "updated" IP addresses which were changed on the page a few hours earlier (and were apparently long outdated). Thanks for reverting both the changes! No need to be sorry. :) Nandini (talk) 21:09, September 17, 2009 (UTC)

Ping

Just out of curiosity, but is there a reason why the IPs listed here are unpingable? RobertM525 09:14, 13 March 2008 (UTC)

Blizz's firewall filters out all ICMP frames at the border of their network. --k_d³ 18:12, 13 March 2008 (UTC)

in my personal opinion, it woudl be an attempt to prevent packet flooding and thusly a denial of service attack, but that's just me --AU518987077 (talk) 23:05, 18 December 2008 (UTC)

How to Find IP Addresses of New Servers

I found this procedure on Blizzard's forum:

1. Start WoW & log in to the realm you want to trace.
2. Press ALT-TAB to minimize WoW and return to the desktop.
3. Click Start, then Run, then type "cmd"
4. In the DOS window type "netstat -an"

You will see at least 2 IP addresses - the first will be Established on port 1119 and the rest will show an established (or waiting) connection on port 3724. It will look like this:

TCP    192.168.1.100:49701    12.129.206.130:1119    ESTABLISHED
TCP    192.168.1.100:49703    206.16.23.70:3724      ESTABLISHED
TCP    192.168.1.100:49703    206.16.23.69:3724      WAITING

The first line is your connection to Blizzard's login server. Either IP address connected to port 3724 will be correct for your server as Blizzard now uses multiple IPs for the same server. --Ibemerson (talk) 01:08, 23 November 2008 (UTC)

Alternatively, if you manage to crash the WoW client, the second line of the crash report will be the realm "Realm: Alleria [63.241.255.8:3724]" MentalPower (talk) 16:29, October 14, 2009 (UTC)

Edited the instructions above, as Battle.net now randomly connects via 1 of 5 ports to the login server (from just connecting via 1119), and Wow connects via a random port (from just connecting via 3724). This change seems to have happend in 3.3.3. Resa1983 (talk) 01:49, April 10, 2010 (UTC)

I have been looking at Server IP information the last couple of days and I have found that the remote port connection to the server is on one of the 6 (5 above plus 4000) ports. --Protuhj (talk) 00:50, July 13, 2010 (UTC)

Another way of finding the IP address if you are on Windows 7 (and possibly Vista) is opening up the Resource Monitor and filtering to the Wow.exe process. You should see 2 active connections. One is to the login server and seems to be in the 12.129.206.xxx block every time I have connected. The other connection is your game server. As a note to anybody going through all of the servers if you go to the character select screen a connection is opened to the server, so you don't need to have a character on every server to test it's IP address. Landon.abney (talk) 23:16, September 2, 2010 (UTC)

Edited the above instructions again as Blizzard has reverted to using 1119/3724 due to some fail ISPs blocking/packet shaping the other ports. Also updated for the 4.0.1 changes User:Napsterbater reported below. Ressy (talk) 16:20, 7 March 2011 (UTC)

Boston Data Center IP Lookup

Out of curiosity I did an IP lookup for one of the Boston Data Center Servers (Turalyon).

The IP address of Turalyon is 206.17.111.74 and according to an IP lookup the information that comes back is referenced to Irvine California.

Does that mean the server(s) moved from Boston to Irvine? Or is there some other reason why Turalyon, and a few others from the Boston Data Center that I checked (Scilla, Thrall, Area 52) seem to be in Irvine, CA? Does IP lookup automatically list Blizzard's Home office location? --Danjf (talk) 22:03, January 17, 2010 (UTC)

There's been some major changes to their server setup... At some point we need to rework this list as they have moved servers around. Feel free to update the IP for your server if you like. --k_d³ 02:20, January 18, 2010 (UTC)

At some point, don't know when for sure, all the servers in Boston got moved to New York. --ShicKla (talk) 02:58, August 30, 2010 (UTC)

The move was made during the 24 hour maintenance window on the affected servers. --Landon.abney (talk) 23:22, September 2, 2010 (UTC)

The IP addresses are registered under ARIN to Blizzard's headquarters as their location. There really isn't a way to know for sure where exactly they are located, however looking at the DNS names of the traceroute hops to get there will usually give you a pretty close idea as to the city they are in. --Landon.abney (talk) 23:22, September 2, 2010 (UTC)

Dallas Datacenter

Seems the Dallas Datacenters have been closed, and both were moved to Chicago during yesterday's 24hr extended maintenance for Cataclysm preparations. All IP addresses for Chicago are now out of date. Resa1983 (talk) 02:17, July 1, 2010 (UTC)

Updated the IP from Warsong, don't know the others. Fleabr (talk) 01:58, July 5, 2010 (UTC)

Updated IP for Staghelm. --Zéddicus (talk) 20:26, July 8, 2010 (UTC)

Updated IP's for All Chicago Realms. Sorry If i stomped on your change. While I've not actually investigated I get the feeling these are all now in the single location, I might come back to this at some point. Anythingss (talk) 05:56, July 13, 2010 (UTC)

Los Angeles Datacentre

Has the IP addresses for the LA servers changed? I did a netstat and a tracert while logged into Gurubashi and it comes back with Hop 16 going to 12.122.129.25 then jumping to 12.122.255.74 as the final destination, which is not matching with the info for the LA Datacentres. Coraldayton (talk) 05:42, August 22, 2010 (UTC)

I know Exodar in the Retaliation Battlegroup (Boston) is the has changed IP blocks from 206.16.147.xxx to 199.107.24.xxx in the past mouth or two. Napsterbater (talk) 08:11, August 22, 2010 (UTC)

Patch 4.0.1 Changes

Looks like each server may use more then one IP now, for example on Exodar US I routinely have a connection or two to any one these IP's 199.107.24.239, 199.107.24.240 and 199.107.24.241, the 12.x.x.x is still there as-well. Napsterbater (talk) 21:27, October 16, 2010 (UTC)

Updates?

as of 06/2011 im thinking this stuff is all good... some confirmation that this stuff isn't out of date would be nice... updated as of.. etc.

one thing else... what would it take to have a web page that takes your address (whomever goes to the page) and all the server addresses, and establishes a 'ping' between you and each, then lists the results in a sortable spreadsheet type of thing, grouped by datacenter and battlegroups, showing good pings in green, bad in red, etc. hmm? would that be so hard? really, lemme know, thanks ;>jamvaru (talk) 03:04, 27 June 2011 (UTC)

oh, and some relevant data might be such as (stuff wow census has) as well as auction house quantities for each faction per server... shows the real popn of a server and the balance between factions. Of the Chicago datacenter realms (of the ones i surveyed, which included the top popn servers from wowcensus/realms...) Emerald Dream had the most balanced AH readings, with 31,388 horde auctions and 30,795 Alliance auctions... Warsong had more Horde entries, as did Illidan, but relatively few alliance entries. Whisperwind had more alliance entries, by over half again (A:27,711; H:15,312);>jamvaru (talk) 03:08, 27 June 2011 (UTC)

Brazilian Realms

Hi, with the launch of wowPT, I've added to the Rampage list the two new servers, Goldrin and Nemesis. 12/08/2011

Accuracy

MMO-Champion reports that "the Raid Browser [seems to not be] completely cross-realm, but instead cross realm for each datacenter, with the Phoenix and Los Angeles datacenters being combined". Can this be verified? --g0urra[T҂C] 12:45, 12 December 2013 (UTC)

Connected Realms

Blizzard's ongoing Connected Realms process not only connects realms together, but is also consolidating the 4 datacenters down into just 2. As New York datacenter realms get connected, they get moved to the Chicago datacenter. As Phoenix dc realms get connected, they get moved to Los Angeles dc. IPs, battlegroups, and even some timezones get changed.

As of 21 Aug 2014, all realms that have been connected so far, are up-to-date with their new location, timezone, and IP. --Frankz2 (talk) 12:18, 22 August 2014 (UTC)

All realms, whether connected or not, have been moved from New York to Chicago and from Phoenix to Los Angeles. As of 14 Aug, New York datacenter has been completely emptied, there are no longer any realms left in it, it is removed from list. As of 21 Aug, Phoenix datacenter has been completely emptied, there are no longer any realms left in it, it is removed from list. --Frankz2 (talk) 12:18, 22 August 2014 (UTC)

All realm IPs in the Chicago datacenter have been changed, from 206.18.x.x to 199.108.x.x --Frankz2 (talk) 16:30, 27 July 2014 (UTC)

Also part of the Connected Realms process, the 13 battlegroups have already been consolidated down into just 8 battlegroups. As of December 2013, the Emberstorm and Whirlwind battlegroups in the Phoenix datacenter no longer exist. All realms still in the Phoenix datacenter have been assigned to battlegroups in the Los Angeles datacenter. As of January 2014, the Nightfall, Retaliation, and Stormstrike battlegroups in the New York datacenter no longer exist. All realms still in the New York datacenter have been assigned to battlegroups in the Chicago datacenter. As of 1 March 2014, all realms are now listed in their correct battlegroup. --Frankz2 (talk) 21:47, 1 March 2014 (UTC)