Cannot access Battle.net

[dylanbaumann]

I'm running into issues connecting to the Battle.net service, but only when accessing the site/services through Sonic's connection.

To demonstrate, here's what I'm seeing, I ran a `tracert` on my PC as seen here. It confirms that the request reach's Sonic's routing IPs, but times out when attempting to reach out to Blizzard's "battle.net" services.

Code: Select all

PS C:\Users\dylan> tracert us.battle.net

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

  1     4 ms     3 ms     3 ms  192.168.1.1
  2     5 ms     5 ms     5 ms  lo0.bng1.okldca04.sonic.net [75.101.33.35]
  3    10 ms     6 ms     7 ms  305.irb.cr2.okldca04.sonic.net [23.93.52.34]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     6 ms     5 ms     5 ms  100.ae1.nrd1.equinix-sj.sonic.net [75.101.33.185]
  8     6 ms     5 ms     6 ms  blizzard.450.ae3.nrd1.equinix-sj.sonic.net [209.148.113.218]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16
 

Any insight on how to fix this?

[dylanbaumann]

I was able to connect by hotspotting via my mobile device, which helps to confirm it's an upstream issue from my PC itself. This means it's either a Model/Router block, or upstream at Sonic themselves.

The traceroute does make it all the way to Sonic before it times out, so I do not believe this is a local modem/router config issue.

[brandonc]

I'm running into issues connecting to the Battle.net service, but only when accessing the site/services through Sonic's connection.

To demonstrate, here's what I'm seeing, I ran a `tracert` on my PC as seen here. It confirms that the request reach's Sonic's routing IPs, but times out when attempting to reach out to Blizzard's "battle.net" services.

Code: Select all

PS C:\Users\dylan> tracert us.battle.net

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

  1     4 ms     3 ms     3 ms  192.168.1.1
  2     5 ms     5 ms     5 ms  lo0.bng1.okldca04.sonic.net [75.101.33.35]
  3    10 ms     6 ms     7 ms  305.irb.cr2.okldca04.sonic.net [23.93.52.34]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     6 ms     5 ms     5 ms  100.ae1.nrd1.equinix-sj.sonic.net [75.101.33.185]
  8     6 ms     5 ms     6 ms  blizzard.450.ae3.nrd1.equinix-sj.sonic.net [209.148.113.218]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16
 

Any insight on how to fix this?

Hi Dylan,

I'm sorry to hear this. I'm having someone in our Network Operations team look into this as I type this message. I'll follow-up after they are finished investigating what could be causing this problem.

Out of curiosity, did this issue just start happening as of today or has this been going on for awhile now?

Hope to hear from you soon.

Kind regards,

[conradpino]

Both ping and traceroute work from AWS EC2 instance but not via Sonic network.

Code: Select all

admin@awsec2:~$ ping -c 4 us.battle.net
PING us.battle.net (137.221.106.102) 56(84) bytes of data.
64 bytes from 137.221.106.102 (137.221.106.102): icmp_seq=1 ttl=49 time=48.4 ms
64 bytes from 137.221.106.102 (137.221.106.102): icmp_seq=2 ttl=49 time=48.5 ms
64 bytes from 137.221.106.102 (137.221.106.102): icmp_seq=3 ttl=49 time=48.4 ms
64 bytes from 137.221.106.102 (137.221.106.102): icmp_seq=4 ttl=49 time=48.8 ms

--- us.battle.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 48.371/48.519/48.826/0.185 ms

admin@awsec2:~$ sudo traceroute --icmp us.battle.net
traceroute to us.battle.net (137.221.106.102), 30 hops max, 60 byte packets
 1  100.64.88.63 (100.64.88.63)  2.358 ms  2.078 ms  2.068 ms
 2  240.5.196.10 (240.5.196.10)  0.351 ms  0.340 ms  0.335 ms
 3  242.16.227.65 (242.16.227.65)  1.002 ms  0.996 ms  0.991 ms
 4  240.1.248.15 (240.1.248.15)  11.392 ms  11.387 ms  11.607 ms
 5  242.5.19.1 (242.5.19.1)  11.424 ms  11.419 ms  11.414 ms
 6  150.222.212.148 (150.222.212.148)  11.472 ms  11.149 ms  11.140 ms
 7  eqix-ix-ch1.blizzard.com (208.115.136.85)  10.162 ms  10.341 ms  10.312 ms
 8  * * *
 9  * * *
10  et-0-0-0-pe02-swlv10.as57976.net (137.221.83.83)  48.577 ms  48.572 ms  48.567 ms
11  las-swlv10-ia-bons-02.as57976.net (137.221.66.19)  48.768 ms  48.761 ms  48.820 ms
12  137.221.105.29 (137.221.105.29)  48.719 ms  48.733 ms  48.849 ms
13  137.221.106.102 (137.221.106.102)  48.477 ms  48.470 ms  48.450 ms

[brandonc]

Update: We have identified it is an issue between Sonic and Battle.net and will work to correct it as soon as possible. Blizzard appears to have a routing problem with a specific Sonic subnet. This is only going to affect customers served out of that subnet block. We are opening a ticket with Blizzard for someone on that side of the fence to look at why they are not properly routing traffic back to that subnet.

We do appreciate you bringing this to our attention and I hope we can resolve this with Blizzard shortly.

Kind regards,

[nymarra]

Just wanted to chime in that I am also affected. This was new to me as of ~ 1:30 Pm PST today.

They've been the target of several DDoS attacks lately, so perhaps they've blocked a block of your IPS due to the culprits?

[jansolo]

I am having the same issue. I was playing a game earlier today and then it just stopped working. WinMTR shows the same issue as your traceroute. Either way, I am glad that Sonic is on it and that it will hopefully be fixed soon.

BattleNet.png (30.13 KiB) Viewed 4623 times

[blat001]

Also having this issue, and the mobile hotspot worked here is the tracert if that is helpful

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

1 <1 ms <1 ms <1 ms homeportal [192.168.42.1]
2 3 ms 2 ms 2 ms lo0.bng2.snfcca05.sonic.net [157.131.132.31]
3 10 ms 100 ms 81 ms 302.irb.cr1.snfcca05.sonic.net [184.23.209.106]
4 3 ms 7 ms 8 ms ae14.cr2.snrfca01.sonic.net [198.27.244.49]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 4 ms 3 ms 4 ms 100.ae1.nrd1.equinix-sj.sonic.net [75.101.33.185]
11 5 ms 4 ms 63 ms blizzard.450.ae3.nrd1.equinix-sj.sonic.net [209.148.113.218]
12 * * * Request timed out.
13 * * * Request timed out.
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.

[blat001]

Working now thanks for the amazing support Sonic!

[conradpino]

Confirmed, working from Windows PC via Sonic 10G Fiber service:

Code: Select all

C:\>ping us.battle.net

Pinging us.battle.net [137.221.106.102] with 32 bytes of data:
Reply from 137.221.106.102: bytes=32 time=15ms TTL=48
Reply from 137.221.106.102: bytes=32 time=15ms TTL=48
Reply from 137.221.106.102: bytes=32 time=15ms TTL=48
Reply from 137.221.106.102: bytes=32 time=14ms TTL=48

Ping statistics for 137.221.106.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 15ms, Average = 14ms