Peer with Blizzard servers?

[dehnert]

Any updates on this? Was Sonic ever able to establish a peer relationship with Blizzard?

[tomoc]

Sonic has been peering with Blizzard since early August 2016.

[dehnert]

Thanks for the update.

[viaggi]

I'm having a problem with a high-ping to their Servers. Based on some of these posts it seems like it can come and go. Was wondering if this is a standard issue with them?

I've tried tracing to their servers just to get a sense of where the slow down is but if Sonic has peer'd with Blizzard then I'm not sure what I should be looking for. The trace route dies after it leaves sonic.

C:\Users\Neon>pathping 24.105.13.38

Tracing route to 24.105.13.38 over a maximum of 30 hops

0 DESKTOP-U8S1VRP.pv.nerdbreedingproject.net [192.168.0.47]
1 pffirewall.pv.nerdbreedingproject.net [192.168.0.1]
2 homeportal [192.168.42.1]
3 173-228-88-1.dsl.dynamic.fusionbroadband.com [173.228.88.1]
4 gig1-29.cr1.lsatca11.sonic.net [70.36.243.77]
5 * * *
Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-U8S1VRP.pv.nerdbreedingproject.net [192.168.0.47]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% pffirewall.pv.nerdbreedingproject.net [192.168.0.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% homeportal [192.168.42.1]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% 173-228-88-1.dsl.dynamic.fusionbroadband.com [173.228.88.1]
0/ 100 = 0% |
4 23ms 0/ 100 = 0% 0/ 100 = 0% gig1-29.cr1.lsatca11.sonic.net [70.36.243.77]

[tomoc]

Hi viaggi,

What ping times are you experiencing?

The last hop you are showing me (cr1.lsatca11) is not the edge of the Sonic network. The equipment directly connected to that router tends to severely depref traceroute traffic, so it can take a while for the traceroute to register that hop. Can you increase the timeout on your traceroute program, or even just give it more time to complete?

Also keep in mind, equipment in Blizzard's own network may not respond to ping traffic either.

[viaggi]

Yesterday we were getting pings over 100ms.
According to my son, today response and ping times were a range he would expect which was about 30ms range.
So it appears the issue has gone away.

If it reoccurs I will take a more complete traceroute and paste that here.

Thanks,
//C

[tomoc]

You're absolutely welcome, I'm glad you aren't currently experiencing any problems.

I double checked, and our peering session with Blizzard has been up for the last 15 weeks.

[chrsitina]

Hi,

I've been trying to find a solution as to why I get random lag spikes and disconnects when I'm playing on the Blizzard servers. Sometimes they occur when my entire internet goes down, most of the time the disconnects/spikes happen independently. It's been so frustrating to the point where my ritual is to do a modem reset + computer restart + IP release/renew when I want to play any Blizzard game. I've read the thread, and I'm not entirely sure how everything got resolved? I do not have a technical background.

I'd appreciate any help.

[mike.perlas]

@christina send me an e-mail with your account details and I'd be glad to check on our end if there are any flagrant issues happening with your line. If your entire connection comes down, sounds like there is likely something fixable on our end. Unless this is only happening on one device!

Feel free to e-mail me at my username @sonic.com

[viaggi]

We're still having intermittent problems connecting and playing with the Blizzard servers.

This trace route is from last week. It seems to indicate some problem between my modem and the first hop.
Tracing route to 24.105.13.38 over a maximum of 30 hops

0 DESKTOP-U8S1VRP.pv.nerdbreedingproject.net [192.168.0.47]
1 pffirewall.pv.nerdbreedingproject.net [192.168.0.1]
2 homeportal [192.168.42.1]
3 173-228-88-1.dsl.dynamic.fusionbroadband.com [173.228.88.1]
4 gig1-29.cr1.lsatca11.sonic.net [70.36.243.77]
5 * * *
Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-U8S1VRP.pv.nerdbreedingproject.net [192.168.0.47]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% pffirewall.pv.nerdbreedingproject.net [192.168.0.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% homeportal [192.168.42.1]
21/ 100 = 21% |
3 3533ms 21/ 100 = 21% 0/ 100 = 0% 173-228-88-1.dsl.dynamic.fusionbroadband.com [173.228.88.1]
14/ 100 = 14% |
4 3523ms 35/ 100 = 35% 0/ 100 = 0% gig1-29.cr1.lsatca11.sonic.net [70.36.243.77]

Trace complete.


This is another trace route from today which seems to indicate no issues with my connection but may indicate some problem further down the routing chain. Are these expected hop times from my system to sonic? This particular trace route seems to indicate that it's a problem inside blizzard.

Tracing route to 24.105.13.38 over a maximum of 30 hops

0 DESKTOP-U8S1VRP.pv.nerdbreedingproject.net [192.168.0.47]
1 pffirewall.pv.nerdbreedingproject.net [192.168.0.1]
2 homeportal [192.168.42.1]
3 173-228-88-1.dsl.dynamic.fusionbroadband.com [173.228.88.1]
4 gig1-29.cr1.lsatca11.sonic.net [70.36.243.77]
5 * * ae2.cr2.lsatca11.sonic.net [50.0.79.178]
6 50.ae4.gw.pao1.sonic.net [50.0.2.5]
7 152.ae4.gw.equinix-sj.sonic.net [50.0.2.94]
8 eqix-ix-sv1.blizzard.com [206.223.116.55]
9 ae1-br01-eqsv5.blizzardonline.net [137.221.70.33]
10 137.221.65.6
11 be2-pe02-eqla1.blizzardonline.net [137.221.68.73]
12 lax-eqla1-ia-bons-03.blizzardonline.net [137.221.66.5]
13 24.105.30.147
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-U8S1VRP.pv.nerdbreedingproject.net [192.168.0.47]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% pffirewall.pv.nerdbreedingproject.net [192.168.0.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% homeportal [192.168.42.1]
17/ 100 = 17% |
3 44ms 18/ 100 = 18% 1/ 100 = 1% 173-228-88-1.dsl.dynamic.fusionbroadband.com [173.228.88.1]
0/ 100 = 0% |
4 36ms 19/ 100 = 19% 2/ 100 = 2% gig1-29.cr1.lsatca11.sonic.net [70.36.243.77]
0/ 100 = 0% |
5 40ms 19/ 100 = 19% 2/ 100 = 2% ae2.cr2.lsatca11.sonic.net [50.0.79.178]
0/ 100 = 0% |
6 39ms 18/ 100 = 18% 1/ 100 = 1% 50.ae4.gw.pao1.sonic.net [50.0.2.5]
0/ 100 = 0% |
7 38ms 18/ 100 = 18% 1/ 100 = 1% 152.ae4.gw.equinix-sj.sonic.net [50.0.2.94]
0/ 100 = 0% |
8 38ms 19/ 100 = 19% 2/ 100 = 2% eqix-ix-sv1.blizzard.com [206.223.116.55]
0/ 100 = 0% |
9 37ms 21/ 100 = 21% 4/ 100 = 4% ae1-br01-eqsv5.blizzardonline.net [137.221.70.33]
0/ 100 = 0% |
10 --- 100/ 100 =100% 83/ 100 = 83% 137.221.65.6
0/ 100 = 0% |
11 47ms 17/ 100 = 17% 0/ 100 = 0% be2-pe02-eqla1.blizzardonline.net [137.221.68.73]
83/ 100 = 83% |
12 --- 100/ 100 =100% 0/ 100 = 0% lax-eqla1-ia-bons-03.blizzardonline.net [137.221.66.5]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 24.105.30.147

Trace complete.