Failed to connect to server after every game

Technical Support
Prev 1 2 3 4 7 Next
No, there are two separate issues. One is "failed to connect to server", where you start joining a game, get kicked back to menu, start to join it again, and get kicked back to the menu again. You are then removed from your group and back in the main menu. This is the one that I'm getting, and most people in this thread are getting.

The other is "Lost connection to game server." which I believe actually makes you log back in to Overwatch. It's something that will happen when you're already in and playing a game.
I thought that I am the only one who actually have this problem. Hopefully Blizzard will make something with it..... cause is annoying. If I am playing alone is allright - I don't mind to have "failed to connect to server" every 1-3 games. But when I am playing in a group is reaaaaaaaaaly annoying.
It would be nice that someone from Blizzard could write something about it here :)
I don't know if it actually worked, but last night I opened all the Overwatch ports on my router and enjoyed a full evening of playing uninterrupted with my friends. I didn't get kicked from my group and could join every game, no problem. I'll try again tonight and see if it still works (I also updated my nVidia driver, but I don't see how that has anything to do with connectivity issues). My worry is that I had no issues to begin with and that I only began having them the day before yesterday. I hope they don't return.

So it seems that opening the correct ports worked for me, but others said that it didn't work for them (It didn't work at first for me either, but that was because I had a dynamic IP. Worked when I changed IP to static and opened ports on my router again with static IP).
05/30/2016 04:54 PMPosted by winter
No, there are two separate issues. One is "failed to connect to server", where you start joining a game, get kicked back to menu, start to join it again, and get kicked back to the menu again. You are then removed from your group and back in the main menu. This is the one that I'm getting, and most people in this thread are getting.

The other is "Lost connection to game server." which I believe actually makes you log back in to Overwatch. It's something that will happen when you're already in and playing a game.


Okay, When I listed them both as Failed to connect its because the people in the messages that described disconnecting after playing said that they got "failed to connect to server" as well ; like in the 1st, 11th, and the title.
Your second post (quoted) is the first time that a "Lost connection to game server" error was mentioned. Everything else was "me too" posts or "Failed to connect" errors - I went back and double checked
Having the same issue of not being able to play with the same people twice, just doesn't let me join the game again afterwards. So if I like a group that I just played with, I can't stay in the game with them. Also can't play with my friends unless they leave after every game as well.
Hi all, we're continuing to investigate these reports and have found that some of the players who are experiencing this have been able to make progress with the general connection troubleshooting info that we offer here.

In addition to the latency troubleshooting, programs like Advanced SystemCare and Asusgamefirstservice.exe have been found to cause connection issues with Overwatch. For the sake of troubleshooting, we recommending uninstalling IOBit - Advanced SystemCare and disabling asusgamefirstservice.exe through the services.

To disable asusgamefirstservice.exe:
  • press the windows key and R on your keyboard at the same time
  • type and enter: services.msc
  • find asusgamefirstservice.exe and double-click to open
  • change the "startup" dropdown to disabled
  • click the 'Stop' button then okay to apply the changes.

Additional Troubleshooting Steps:
  • Add an exception/exclusion for the game in Avast (if present)
  • Disable Plays.tv services
  • Run the Battle.net App in Administrator Mode

If you continue to experience the error message after trying the above steps, it will be helpful to have you report the make/model of your router in a new post in this thread, along with your Trace Route, Pathping, and Looking Glass results.

Much appreciated!
05/31/2016 02:55 PMPosted by Araxom
Hi all, we're continuing to investigate these reports and have found that some of the players who are experiencing this have been able to make progress with the general connection troubleshooting info that we offer [url="https://battle.net/support/article/611?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]here[/url].

In addition to the latency troubleshooting, programs like Advanced SystemCare and Asusgamefirstservice.exe have been found to cause connection issues with Overwatch. For the sake of troubleshooting, we recommending uninstalling IOBit - Advanced SystemCare and disabling asusgamefirstservice.exe through the services.

To disable asusgamefirstservice.exe:
  • press the windows key and R on your keyboard at the same time
  • type and enter: services.msc
  • find asusgamefirstservice.exe and double-click to open
  • change the "startup" dropdown to disabled
  • click the 'Stop' button then okay to apply the changes.

Additional Troubleshooting Steps:
  • Add an exception/exclusion for the game in Avast (if present)
  • Disable Plays.tv services
  • Run the Battle.net App in [url="https://battle.net/support/article/2700027?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Administrator Mode[/url]

If you continue to experience the error message after trying the above steps, it will be helpful to have you report the make/model of your router in a new post in this thread, along with your [url="https://battle.net/support/article/7648?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Trace Route[/url], [url="https://battle.net/support/article/718?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Pathping[/url], and [url="https://battle.net/support/article/7263?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Looking Glass[/url] results.

Much appreciated!


Soo what about console players?
For console connection troubleshooting please review the information we offer here.

If those steps don't help, please respond with the console platform you're on (PS4/XB1) and be sure to list your router's make/model. Ty
05/31/2016 03:11 PMPosted by Araxom
For console connection troubleshooting please review the information we offer [url="https://battle.net/support/article/7778?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]here[/url].

If those steps don't help, please respond with the console platform you're on (PS4/XB1) and be sure to list your router's make/model. Ty


Ps4 wired fiber line.
Router is Technicolor tg58n2 pro

Obtain ip successful
Connection successful
Psn sign in successful
Nat type 2
Download speed 52.2 mbps
Upload 4.9 mbps

as for looking glass I'm using a tablet atm and ps4 won't copy/paste. No way am I typing all that out on this thing :p

However I can tell you that it has high latency 2998ms and 100% package loss. No other problems with any other games be it on Pc or console.
Try disabling Game Mode in the router settings, and then enable the built in Router firewall on the Medium setting. You should be able to set those without rebooting the router and the changes should kick in immediately.
Iv had the same issue, worked in beta now it doesn't bla bla bla... Iv tried all the thing Araxom has said and then some. I would like some sort of assurance that this will be fixed, or my money back.
Appears to have worked. Who would of guessed that was the issue :p hope this don't effect any other games though.

Tyvm
Glad that helped you, Vicarious! :)

@Isalex: are you on PC or Console? Also- what's the make/model of your router?
Didn't work with me -_-
TRACERT
Tracing route to 37.244.0.3 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.1.1
2 3 ms 2 ms 2 ms 118.69.253.217
3 1 ms 1 ms 1 ms 100.123.0.255
4 3 ms 37 ms 2 ms 42.114.246.74
5 26 ms 28 ms 26 ms 118.69.132.169
6 195 ms 198 ms 194 ms 80.150.171.225
7 190 ms 193 ms 196 ms 217.239.45.6
8 190 ms 192 ms 196 ms 217.6.51.246
9 175 ms 175 ms 175 ms ae-4-90.edge2.LosAngeles9.Level3.net [4.69.144.207]
10 185 ms 184 ms 184 ms BLIZZARD-EN.edge2.LosAngeles9.Level3.net [4.53.230.238]
11 195 ms 197 ms 195 ms 37.244.0.3

PATHPING
Tracing route to 37.244.0.3 over a maximum of 30 hops

0 DESKTOP-3UQDCCJ [192.168.1.4]
1 192.168.1.1
2 100.123.0.20
3 118.69.253.217
4 42.114.246.74
5 118.69.132.169
6 80.150.171.225
7 217.239.45.6
8 217.6.51.246
9 ae-4-90.edge2.LosAngeles9.Level3.net [4.69.144.207]
10 BLIZZARD-EN.edge2.LosAngeles9.Level3.net [4.53.230.238]
11 37.244.0.3

TRACEROUTE:
traceroute to 42.113.162.118 (42.113.162.118), 15 hops max, 60 byte packets
1 24.105.12.6 (24.105.12.6) 1.739 ms 1.825 ms 1.883 ms
2 24.105.30.148 (24.105.30.148) 1.061 ms 1.162 ms 1.171 ms
3 37.244.0.100 (37.244.0.100) 1.952 ms 2.031 ms 2.124 ms
4 37.244.0.32 (37.244.0.32) 1.757 ms 1.899 ms 1.903 ms
5 te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net (173.167.56.217) 1.338 ms 1.452 ms 1.469 ms
6 hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25) 3.191 ms hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13) 2.286 ms hu-0-5-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.83.21) 1.978 ms
7 hu-0-1-0-1-pe01.losangeles.ca.ibone.comcast.net (68.86.85.98) 2.615 ms 2.623 ms 2.520 ms
8 203.208.169.61 (203.208.169.61) 2.117 ms 1.089 ms 1.079 ms
9 203.208.173.81 (203.208.173.81) 368.074 ms 203.208.171.233 (203.208.171.233) 1.211 ms 203.208.151.113 (203.208.151.113) 246.210 ms
10 203.208.171.198 (203.208.171.198) 186.360 ms 203.208.182.77 (203.208.182.77) 161.320 ms 203.208.153.121 (203.208.153.121) 163.384 ms
11 203.208.183.13 (203.208.183.13) 238.100 ms 203.208.183.154 (203.208.183.154) 270.429 ms 203.208.153.253 (203.208.153.253) 227.513 ms
12 203.208.171.198 (203.208.171.198) 173.274 ms 186.833 ms 203.208.177.90 (203.208.177.90) 174.956 ms
13 203.208.149.78 (203.208.149.78) 209.496 ms 209.480 ms *
14 203.208.177.90 (203.208.177.90) 174.609 ms 172.257 ms 172.357 ms
15 * * *

01/06/2016 03:06:36 UTC
--------------------

TRACEROUTE:
traceroute to 42.113.162.118 (42.113.162.118), 15 hops max, 60 byte packets
1 24.105.44.5 (24.105.44.5) 0.606 ms 0.754 ms 0.833 ms
2 24.105.62.150 (24.105.62.150) 2.082 ms 2.092 ms 2.091 ms
3 37.244.1.102 (37.244.1.102) 3.822 ms 3.832 ms 3.834 ms
4 37.244.1.34 (37.244.1.34) 2.238 ms 2.601 ms 2.615 ms
5 te-0-11-0-0-3-pe01.350ecermak.il.ibone.comcast.net (50.242.151.153) 2.617 ms 2.618 ms 2.620 ms
6 hu-2-0-0-9-cr02.350ecermak.il.ibone.comcast.net (68.86.85.49) 2.665 ms 4.626 ms 4.608 ms
7 be-10517-cr02.denver.co.ibone.comcast.net (68.86.85.170) 26.609 ms 26.084 ms 26.069 ms
8 be-11719-cr01.1601milehigh.co.ibone.comcast.net (68.86.86.78) 24.870 ms 25.141 ms 25.282 ms
9 be-10919-cr01.sunnyvale.ca.ibone.comcast.net (68.86.85.153) 53.590 ms 54.638 ms 54.652 ms
10 hu-0-13-0-0-pe02.529bryant.ca.ibone.comcast.net (68.86.86.94) 54.652 ms 54.650 ms 55.538 ms
11 75.149.231.242 (75.149.231.242) 53.960 ms 53.724 ms 53.865 ms
12 203.208.151.89 (203.208.151.89) 329.401 ms 203.208.182.121 (203.208.182.121) 249.464 ms 203.208.158.125 (203.208.158.125) 337.395 ms
13 203.208.151.217 (203.208.151.217) 251.946 ms 203.208.182.85 (203.208.182.85) 235.990 ms 203.208.182.134 (203.208.182.134) 261.267 ms
14 * * *
15 203.208.182.134 (203.208.182.134) 248.968 ms 254.214 ms *

01/06/2016 03:06:37 UTC
--------------------

PING:
PING 42.113.162.118 (42.113.162.118) 56(84) bytes of data.

--- 42.113.162.118 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

01/06/2016 03:06:36 UTC
--------------------

PING:
PING 42.113.162.118 (42.113.162.118) 56(84) bytes of data.

--- 42.113.162.118 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

01/06/2016 03:06:37 UTC
--------------------

MTR:
Start: Wed Jun 1 03:06:36 2016
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.12.6 0.0% 10 0.6 0.7 0.5 1.5 0.0
2.|-- 24.105.30.148 0.0% 10 1.2 1.2 1.1 1.5 0.0
3.|-- 37.244.0.100 0.0% 10 1.4 1.4 1.3 2.0 0.0
4.|-- 37.244.0.32 0.0% 10 2.1 1.8 1.4 3.0 0.3
5.|-- te-0-4-0-9-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 1.8 1.8 1.5 2.2 0.0
6.|-- hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 1.8 2.8 1.8 3.6 0.3
7.|-- hu-0-1-0-1-pe01.losangeles.ca.ibone.comcast.net 0.0% 10 1.5 3.8 1.4 20.9 6.1
8.|-- 203.208.169.61 0.0% 10 1.6 4.8 1.2 33.5 10.1
9.|-- 203.208.183.146 0.0% 10 169.7 90.1 1.2 184.0 93.5
10.|-- 203.208.171.198 0.0% 10 182.6 182.6 163.5 203.3 10.6
11.|-- 203.208.149.78 0.0% 10 191.7 183.6 170.4 197.3 10.7
12.|-- 203.208.171.198 0.0% 10 177.3 180.9 173.4 195.3 7.5
13.|-- 203.208.149.78 40.0% 10 198.0 190.9 183.4 198.0 5.8
14.|-- 203.208.177.90 60.0% 10 165.4 167.0 165.0 172.3 3.5
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

01/06/2016 03:06:36 UTC
--------------------

MTR:
Start: Wed Jun 1 03:06:37 2016
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.44.5 0.0% 10 0.6 0.7 0.5 1.2 0.0
2.|-- 24.105.62.150 0.0% 10 1.0 1.0 0.7 1.3 0.0
3.|-- 37.244.1.102 0.0% 10 4.0 2.7 2.4 4.0 0.3
4.|-- 37.244.1.34 0.0% 10 5.2 3.6 1.7 5.8 1.4
5.|-- te-0-11-0-0-3-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.2 2.1 1.7 2.7 0.0
6.|-- hu-2-0-0-9-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 4.5 3.3 2.5 4.5 0.5
7.|-- be-10517-cr02.denver.co.ibone.comcast.net 0.0% 10 25.9 25.9 24.5 27.1 0.7
8.|-- be-11719-cr01.1601milehigh.co.ibone.comcast.net 90.0% 10 24.5 24.5 24.5 24.5 0.0
9.|-- be-10919-cr01.sunnyvale.ca.ibone.comcast.net 0.0% 10 53.6 54.3 53.6 59.8 1.8
10.|-- hu-0-13-0-0-pe02.529bryant.ca.ibone.comcast.net 0.0% 10 54.3 54.4 54.3 54.9 0.0
11.|-- 75.149.231.242 0.0% 10 53.9 53.9 53.7 54.4 0.0
12.|-- 203.208.171.110 0.0% 10 237.3 130.6 54.0 246.6 94.4
13.|-- 203.208.182.134 0.0% 10 255.0 236.7 224.0 255.0 9.6
14.|-- 203.208.177.90 0.0% 10 228.9 254.2 228.9 369.8 41.4
15.|-- 203.208.182.134 40.0% 10 240.8 239.6 231.9 256.5 9.0
16.|-- 203.208.177.90 30.0% 10 238.9 237.1 232.1 240.4 3.3
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

01/06/2016 03:06:37 UTC
--------------------
05/31/2016 03:59 PMPosted by Araxom
Try disabling Game Mode in the router settings, and then enable the built in Router firewall on the Medium setting. You should be able to set those without rebooting the router and the changes should kick in immediately.


I love You :D.
Now it's work perfectly !!!!. Thank You !!!.
Stilling getting disconnected after every game so i can't play with the same people after troubleshooting =(
i still have the: failed to connect to server and getting booted from games. i play on pc and only this game is doing anything like this so it aint my pc or my inet, we shouldnt have to change our software. it is your job to make sure the game works when you launch it.... i had no issues at all during beta. bought game and cant play more than 2-3 games in a row without getting failed to connect to server. it is getting beyond annoying. any eta on fix? or are we all going to be forced into specific brands of pc hardware+software so we can play blizzard games in the future?
06/01/2016 05:23 AMPosted by Hoedeplank
i still have the: failed to connect to server and getting booted from games. i play on pc and only this game is doing anything like this so it aint my pc or my inet, we shouldnt have to change our software. it is your job to make sure the game works when you launch it.... i had no issues at all during beta. bought game and cant play more than 2-3 games in a row without getting failed to connect to server. it is getting beyond annoying. any eta on fix? or are we all going to be forced into specific brands of pc hardware+software so we can play blizzard games in the future?


I have benn trying everything to fix this problem, still no results. Is there any fix comming soon?
Same here
05/31/2016 02:55 PMPosted by Araxom
Hi all, we're continuing to investigate these reports and have found that some of the players who are experiencing this have been able to make progress with the general connection troubleshooting info that we offer [url="https://battle.net/support/article/611?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]here[/url].

In addition to the latency troubleshooting, programs like Advanced SystemCare and Asusgamefirstservice.exe have been found to cause connection issues with Overwatch. For the sake of troubleshooting, we recommending uninstalling IOBit - Advanced SystemCare and disabling asusgamefirstservice.exe through the services.

To disable asusgamefirstservice.exe:
  • press the windows key and R on your keyboard at the same time
  • type and enter: services.msc
  • find asusgamefirstservice.exe and double-click to open
  • change the "startup" dropdown to disabled
  • click the 'Stop' button then okay to apply the changes.

Additional Troubleshooting Steps:
  • Add an exception/exclusion for the game in Avast (if present)
  • Disable Plays.tv services
  • Run the Battle.net App in [url="https://battle.net/support/article/2700027?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Administrator Mode[/url]

If you continue to experience the error message after trying the above steps, it will be helpful to have you report the make/model of your router in a new post in this thread, along with your [url="https://battle.net/support/article/7648?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Trace Route[/url], [url="https://battle.net/support/article/718?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Pathping[/url], and [url="https://battle.net/support/article/7263?utm_source=Internal-TechForum&utm_medium=Posting&utm_campaign=BlizzardCS&utm_content=solution"]Looking Glass[/url] results.

Much appreciated!


PC user
--------------router---------------
netgear N600 wireless dual band
gigabit ADSL2 + modem router
DGND3700v2
-----------------looking glass----------------
TRACEROUTE:
traceroute to 172.164.36.227 (172.164.36.227), 15 hops max, 60 byte packets
1 24.105.44.5 (24.105.44.5) 2.418 ms 2.553 ms 2.686 ms
2 24.105.62.146 (24.105.62.146) 2.803 ms 2.993 ms 3.045 ms
3 37.244.1.100 (37.244.1.100) 3.164 ms 3.236 ms 3.246 ms
4 37.244.1.32 (37.244.1.32) 3.314 ms 3.410 ms 4.758 ms
5 te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net (173.167.56.237) 3.120 ms 3.130 ms 3.132 ms
6 hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net (68.86.89.245) 5.120 ms 3.306 ms 3.284 ms
7 hu-0-13-0-1-pe04.350ecermak.il.ibone.comcast.net (68.86.87.126) 1.382 ms 1.544 ms 1.527 ms
8 as1668-pe01.350ecermak.il.ibone.comcast.net (75.149.230.222) 22.178 ms 22.177 ms 22.178 ms
9 bb1-vie-xe-1-0-0.atdn.net (66.185.152.217) 19.899 ms 19.701 ms 19.720 ms
10 dar1-mtc-ae2.atdn.net (66.185.152.88) 20.771 ms 20.854 ms 20.858 ms
11 cam1-mtc-ae4.net.aol.com (66.185.144.46) 21.428 ms 21.514 ms 21.474 ms
12 * * *
13 ipt-mtcc02.proxy.aol.com (64.12.120.66) 19.940 ms 20.003 ms 19.822 ms
14 * * *
15 * * *

01/06/2016 18:12:31 UTC
--------------------

TRACEROUTE:
traceroute to 172.164.36.227 (172.164.36.227), 15 hops max, 60 byte packets
1 24.105.12.5 (24.105.12.5) 0.721 ms 0.831 ms 0.948 ms
2 24.105.30.146 (24.105.30.146) 1.119 ms 1.182 ms 1.245 ms
3 12.129.199.181 (12.129.199.181) 2.297 ms * *
4 12.129.193.253 (12.129.193.253) 4.404 ms 4.572 ms 4.579 ms
5 cr2.la2ca.ip.att.net (12.122.129.242) 1.816 ms 1.822 ms 1.940 ms
6 cr2.la2ca.ip.att.net (12.122.129.242) 1.943 ms 3.538 ms 3.495 ms
7 gar29.la2ca.ip.att.net (12.122.129.233) 3.175 ms 2.750 ms 2.723 ms
8 bb2-las-xe-0-1-0.atdn.net (66.185.151.105) 12.783 ms 12.787 ms 12.782 ms
9 bb1-las-xe-4-1-0.atdn.net (66.185.152.100) 13.298 ms 13.268 ms 13.285 ms
10 bb1-dls-xe-4-2-0.atdn.net (66.185.153.9) 36.417 ms 36.437 ms 36.381 ms
11 bb2-dls-xe-0-0-0.atdn.net (66.185.133.97) 36.297 ms 36.296 ms 36.293 ms
12 bb2-vie-xe-1-0-0.atdn.net (66.185.133.117) 70.267 ms 70.269 ms 70.283 ms
13 dar2-mtc-ae2.atdn.net (66.185.152.194) 70.358 ms 70.360 ms 70.333 ms
14 cam2-mtc-ae4.net.aol.com (66.185.144.50) 70.550 ms 70.498 ms 70.815 ms
15 * * *

01/06/2016 18:12:31 UTC
--------------------

PING:
PING 172.164.36.227 (172.164.36.227) 56(84) bytes of data.

--- 172.164.36.227 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

01/06/2016 18:12:31 UTC
--------------------

PING:
PING 172.164.36.227 (172.164.36.227) 56(84) bytes of data.

--- 172.164.36.227 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

01/06/2016 18:12:31 UTC
--------------------

MTR:
Start: Wed Jun 1 18:12:31 2016
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.44.5 0.0% 10 0.9 0.7 0.5 0.9 0.0
2.|-- 24.105.62.146 0.0% 10 1.1 1.3 0.9 2.0 0.0
3.|-- 37.244.1.100 0.0% 10 1.4 1.7 1.4 2.7 0.0
4.|-- 37.244.1.32 0.0% 10 2.0 2.2 1.3 3.4 0.5
5.|-- te-0-11-0-0-2-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 2.2 2.0 1.5 3.2 0.3
6.|-- hu-2-4-0-1-cr02.350ecermak.il.ibone.comcast.net 0.0% 10 3.3 3.0 2.3 3.7 0.0
7.|-- hu-0-13-0-1-pe04.350ecermak.il.ibone.comcast.net 0.0% 10 2.1 1.9 1.5 2.3 0.0
8.|-- as1668-pe01.350ecermak.il.ibone.comcast.net 0.0% 10 1.8 1.7 1.1 2.0 0.0
9.|-- bb1-vie-xe-1-0-0.atdn.net 0.0% 10 19.9 20.4 19.8 23.9 1.1
10.|-- dar1-mtc-ae2.atdn.net 0.0% 10 20.8 21.0 20.7 21.5 0.0
11.|-- cam1-mtc-ae4.net.aol.com 0.0% 10 22.2 21.6 21.4 22.2 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ipt-mtcc02.proxy.aol.com 0.0% 10 20.0 20.1 19.9 20.8 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

01/06/2016 18:12:31 UTC
--------------------

MTR:
Start: Wed Jun 1 18:12:31 2016
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.12.5 0.0% 10 0.8 0.6 0.5 0.9 0.0
2.|-- 24.105.30.146 0.0% 10 1.3 1.1 0.9 1.4 0.0
3.|-- 12.129.199.181 0.0% 10 2.3 20.9 2.3 104.0 39.0
4.|-- 12.129.193.253 0.0% 10 4.3 6.6 4.3 24.9 6.4
5.|-- cr2.la2ca.ip.att.net 0.0% 10 3.6 3.9 1.8 5.4 1.1
6.|-- cr2.la2ca.ip.att.net 0.0% 10 2.0 3.2 1.5 4.5 0.9
7.|-- gar29.la2ca.ip.att.net 0.0% 10 4.8 5.1 2.9 13.5 3.0
8.|-- bb2-las-xe-0-1-0.atdn.net 0.0% 10 29.0 14.5 12.8 29.0 5.1
9.|-- bb1-las-xe-4-1-0.atdn.net 0.0% 10 13.4 16.6 13.4 44.2 9.7
10.|-- bb1-dls-xe-4-2-0.atdn.net 0.0% 10 36.4 37.3 36.2 45.5 2.8
11.|-- bb2-dls-xe-0-0-0.atdn.net 0.0% 10 36.3 36.4 36.2 36.7 0.0
12.|-- bb2-vie-xe-1-0-0.atdn.net 0.0% 10 70.3 70.3 70.2 70.7 0.0
13.|-- dar2-mtc-ae2.atdn.net 0.0% 10 70.6 70.5 70.4 71.2 0.0
14.|-- cam2-mtc-ae4.net.aol.com 0.0% 10 70.7 70.6 70.5 70.7 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ipt-mtcc02.proxy.aol.com 0.0% 10 70.8 70.7 70.6 70.8 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

01/06/2016 18:12:31 UTC
--------------------

------------------------------Tracert----------------------------------------

Tracing route to 37.244.0.3 over a maximum of 30 hops

1 1 ms 1 ms 1 ms www.routerlogin.com [192.168.0.1]
2 64 ms 63 ms 74 ms ipt-mtcc02.dial.aol.com [64.12.7.194]
3 73 ms 61 ms 67 ms iptfarmc-mr2-sw0-vla3.conc.aol.com [64.12.120.94]
4 61 ms 63 ms 60 ms cam1-mtc-ae2.net.aol.com [172.20.201.43]
5 62 ms 64 ms 61 ms dar1-mtc-ae1.atdn.net [66.185.144.45]
6 62 ms 71 ms 62 ms pop1-ash-ae4.atdn.net [66.185.152.9]
7 63 ms 66 ms 62 ms xe-2-0-0.er4.iad10.us.zip.zayo.com [64.125.12.221]
8 68 ms 65 ms 66 ms ae15.cr1.dca2.us.zip.zayo.com [64.125.31.21]
9 74 ms 65 ms 67 ms ae6.er1.iad10.us.zip.zayo.com [64.125.20.118]
10 65 ms 73 ms 65 ms ae7.er2.iad10.us.zip.zayo.com [64.125.25.50]
11 66 ms 64 ms 64 ms 208.184.253.38.IPYX-106626-003-ZYO.zip.zayo.com [208.184.253.38]
12 154 ms 150 ms 153 ms 37.244.4.33
13 154 ms 153 ms 151 ms 24.105.31.13
14 150 ms 155 ms 151 ms 24.105.31.3
15 150 ms 153 ms 150 ms 37.244.0.3

Trace complete.

--------------------------------pathping---------------------------------------------------

Tracing route to 37.244.0.3 over a maximum of 30 hops

0 CuSith-PC [192.168.0.3]
1 www.routerlogin.com [192.168.0.1]
2 ipt-mtcc02.dial.aol.com [64.12.7.194]
3 iptfarmc-mr2-sw0-vla3.conc.aol.com [64.12.120.94]
4 cam1-mtc-ae2.net.aol.com [172.20.201.43]
5 dar1-mtc-ae1.atdn.net [66.185.144.45]
6 pop1-ash-ae4.atdn.net [66.185.152.9]
7 xe-2-0-0.er4.iad10.us.zip.zayo.com [64.125.12.221]
8 ae15.cr1.dca2.us.zip.zayo.com [64.125.31.21]
9 ae6.er1.iad10.us.zip.zayo.com [64.125.20.118]
10 ae7.er2.iad10.us.zip.zayo.com [64.125.25.50]
11 208.184.253.38.IPYX-106626-003-ZYO.zip.zayo.com [208.184.253.38]
12 37.244.4.33
13 24.105.31.13
14 24.105.31.3
15 37.244.0.3

Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 CuSith-PC [192.168.0.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% www.routerlogin.com [192.168.0.1]
0/ 100 = 0% |
2 62ms 0/ 100 = 0% 0/ 100 = 0% ipt-mtcc02.dial.aol.com [64.12.7.194]
0/ 100 = 0% |
3 63ms 0/ 100 = 0% 0/ 100 = 0% iptfarmc-mr2-sw0-vla3.conc.aol.com [64.12.120.94]
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% cam1-mtc-ae2.net.aol.com [172.20.201.43]
0/ 100 = 0% |
5 63ms 0/ 100 = 0% 0/ 100 = 0% dar1-mtc-ae1.atdn.net [66.185.144.45]
0/ 100 = 0% |
6 64ms 0/ 100 = 0% 0/ 100 = 0% pop1-ash-ae4.atdn.net [66.185.152.9]
0/ 100 = 0% |
7 64ms 0/ 100 = 0% 0/ 100 = 0% xe-2-0-0.er4.iad10.us.zip.zayo.com [64.125.12.221]
0/ 100 = 0% |
8 66ms 0/ 100 = 0% 0/ 100 = 0% ae15.cr1.dca2.us.zip.zayo.com [64.125.31.21]
0/ 100 = 0% |
9 67ms 0/ 100 = 0% 0/ 100 = 0% ae6.er1.iad10.us.zip.zayo.com [64.125.20.118]
0/ 100 = 0% |
10 67ms 0/ 100 = 0% 0/ 100 = 0% ae7.er2.iad10.us.zip.zayo.com [64.125.25.50]
0/ 100 = 0% |
11 66ms 0/ 100 = 0% 0/ 100 = 0% 208.184.253.38.IPYX-106626-003-ZYO.zip.zayo.com [208.184.253.38]
0/ 100 = 0% |
12 65ms 0/ 100 = 0% 0/ 100 = 0% 37.244.4.33
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% 24.105.31.13
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% 24.105.31.3
0/ 100 = 0% |
15 151ms 0/ 100 = 0% 0/ 100 = 0% 37.244.0.3

Trace complete.

Join the Conversation

Return to Forum