Actual Battle.net Status via Ping

BasementCat

Canada155 Posts

July 28 2010 02:53 GMT

Closed Until I'm sure it's not just me...+ Show Spoiler +

I'll be streaming the ping status of all the battle.net servers on my ustream.

no music, no distractions, just pings...

http://www.ustream.tv/channel/battle-net-ping-status

When you don't see the spam of "Request timed out" then that means that battle.net should be working.

Melancholia

United States717 Posts

July 28 2010 03:00 GMT

I like this idea, thanks.

R1CH

Netherlands10340 Posts

July 28 2010 03:04 GMT

Ping is not a very reliable way to determine if bnet is working or not as battle.net does not respond to ping. Additionally you are not pinging the actual game servers but the web servers. The bnet status thread stickied at the top of the SC2 forum should be more accurate as it actually tries to login to each realm.

BasementCat

Canada155 Posts

July 28 2010 03:06 GMT

login not working for me as well as all of the people streaming on tl can't use multiplayer.

web servers seem to be working fine as I am able to log into http://us.battle.net/en/

Blizzard still lists "ping" and "tracert" as reliable DNS troubleshooting methods.

R1CH

Netherlands10340 Posts

July 28 2010 03:09 GMT

The services inside battle.net cannot be monitored without dissecting the battle.net protocol and having working keys for each realm. This includes multiplayer, single player, matchmaking, custom games, etc. The best test you can do is try to login, which the bot is able to do successfully to each realm. If you are having trouble logging in, then something else is causing your problem as battle.net login is definitely up.

BasementCat

Canada155 Posts

July 28 2010 03:17 GMT

I'll be doing some investigating... but I know people aren't able to play multiplayer.

Chrisboy

Australia118 Posts

July 28 2010 03:17 GMT

What happened to the SEA status? It was being displayed the other day.

BasementCat

Canada155 Posts

July 28 2010 03:29 GMT

R1CH, if you could pm me an output of your tracert that would help me a lot.

I've been getting the "...temporary outage of the Battle.net service..." message whenever I try to log in.

Here's my Tracert.
C:\>tracert us.battle.net

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 * * * Request timed out.
2 49 ms 47 ms 50 ms rd1bb-ge4-0-0-5.vc.shawcable.net [64.59.158.242]

3 41 ms 31 ms 22 ms rc2bb-tge0-7-0-0.vc.shawcable.net [66.163.69.145
]
4 46 ms 38 ms 50 ms rc3wt-ge15-0-0.wa.shawcable.net [66.163.77.142]

5 38 ms 38 ms 31 ms xe-11-0-0.edge1.Seattle3.Level3.net [4.71.152.25
]
6 26 ms 28 ms 38 ms 192.205.36.153
7 53 ms 53 ms 74 ms cr1.st6wa.ip.att.net [12.122.146.50]
8 51 ms 76 ms 57 ms cr2.sffca.ip.att.net [12.122.31.194]
9 66 ms 53 ms 71 ms cr2.la2ca.ip.att.net [12.122.31.133]
10 60 ms 63 ms 58 ms cr84.la2ca.ip.att.net [12.123.30.249]
11 55 ms 55 ms 56 ms gar5.la2ca.ip.att.net [12.122.129.25]
12 89 ms 106 ms 126 ms 12.122.255.74
13 59 ms 65 ms 56 ms 12.129.193.242
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

hops 14-30 may mean that battle.net's unsolicited traffic protection has kicked in.

you can delete this thread now.

Please or register to reply.

Actual Battle.net Status via Ping

Completed

Ongoing

Upcoming