Error 1016, lost connection.

Technical Support
Hi guys,

trying to log into d3 and got a new error i've never seen before: error 1016.

Just before this happened i clicked the " uninstall necromancer beta " PTR option, then tried to fire up D3 and seem to be unable to get a connection to the Americas servers?

Any ideas on how i can fix this?

nevermind - seems to have fixed itself. disregard this
Hey Bliss,

I have seen this before with this error. I have a few things we can do to resolve this and I like you to start by running the Scan and Repair on the Diablo 3.

Then make sure you are power cycle your modem and router. When the computer comes back up from that Flush your DNS.

Also we have seen players using Razer Chroma getting this error. I do not know if you are but disabling it has resolved this issue for them. So please disable it if you have that.
I have been getting this same stupid *#@$!$# error along with the dumb network disconnected error along with it and i have done everything to fix it but nothing worked so i need help cuz im getting real ticked ofd about this n i will end up deleteing d3 n i really dont want to do tht but if this crap keeps happening im getting rid of it
Hello,

I too have started receiving this error since the past 2 days. And I urge you to trust me that I've tried each and every thing mentioned in terms of solutions in almost all the threads on this topic listed in the first 2 pages of google search. Including some very ridiculous suggestions, I might add. Needless to say, I've isolated everything in these forums but nothing seems to be working. Client disconnects while trying to launch the game or sending a whisper. If not, the error just pops up in game after a few minutes or seconds into the game.

And no, my internet is fine. Everything else works fine. Destiny 2 works like a charm. So I highly doubt it has got something to do with my ISP.
well after many years of playing D3 never have any problems till this week
getting this same error 1016...I don't know what to do now any help is very much appreciated
i also getting the same error. my goodness i have to restart my pc all the time. Please help
9 days without playing D3 because I getting code 1016 every single time I logging in the game I have try almost everything here :-(
@HappyPants...

Troubleshooting for Diablo III error 1016 :
https://us.battle.net/support/en/article/103102
(words in blue are links to additional information/procedures)

If the troubleshooting does not solve the issue, then contact Blizzard Support directly... https://us.battle.net/support/en/help/product/diablo3/273/277/channels
Pls do let them know that you are only playing on Asia region... I'm not sure if the US region Support can help you, but they will let you know if they cannot. You should also include a WinMTR and a looking glass with your ticket.
WinMTR : https://us.battle.net/support/en/article/27780
Looking-Glass : https://us-looking-glass.battle.net/ (make sure you select Korea for the Region, and Diablo 3 for Service)

---------------------------
Edit : My looking-glass shows some issue with one node in the Blizzard network
TRACEROUTE:
traceroute to 173.176.78.2 (173.176.78.2), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.393 ms 0.365 ms 0.343 ms
2 117.52.34.130 (117.52.34.130) 0.797 ms 0.801 ms 0.925 ms
3 117.52.161.193 (117.52.161.193) 1.072 ms 1.087 ms 1.139 ms
4 137.221.66.100 (137.221.66.100) 0.742 ms 0.747 ms 0.745 ms
5 137.221.84.68 (137.221.84.68) 3.634 ms 3.632 ms 3.629 ms
6 137.221.84.32 (137.221.84.32) 0.729 ms * *
7 110.45.174.217 (110.45.174.217) 0.796 ms 0.798 ms 0.794 ms
8 61-111-34-121.kidc.net (61.111.34.121) 2.818 ms 2.815 ms 2.304 ms
9 117.52.1.221 (117.52.1.221) 1.234 ms 1.227 ms 1.244 ms
10 1.208.105.45 (1.208.105.45) 1.637 ms 1.354 ms 1.339 ms
11 1.213.105.38 (1.213.105.38) 134.785 ms 134.799 ms 134.714 ms
12 211.118.180.146 (211.118.180.146) 143.543 ms 211.118.180.150 (211.118.180.150) 143.460 ms 211.118.180.146 (211.118.180.146) 143.699 ms
13 144.223.44.61 (144.223.44.61) 137.578 ms 137.592 ms 137.540 ms
14 144.232.4.129 (144.232.4.129) 150.209 ms 150.227 ms 150.222 ms
15 ix-ae-13-0.tcore1.eql-los-angeles.as6453.net (206.82.129.1) 134.648 ms 134.637 ms 134.615 ms

14/02/2019 13:39:12 UTC
--------------------

MTR:
Start: Thu Feb 14 13:39:12 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 117.52.34.2 0.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- 117.52.161.193 0.0% 10 0.9 1.4 0.9 3.7 0.6
4.|-- 137.221.66.96 0.0% 10 0.5 0.6 0.5 0.7 0.0
5.|-- 137.221.84.66 0.0% 10 2.7 6.1 0.9 14.9 4.3
6.|-- 137.221.84.36 30.0% 10 0.5 0.6 0.5 0.6 0.0
7.|-- 110.45.174.213 0.0% 10 0.5 0.5 0.5 0.6 0.0
8.|-- 182.162.152.9 0.0% 10 0.5 0.5 0.4 0.6 0.0
9.|-- 117.52.1.217 0.0% 10 1.2 1.3 1.1 2.1 0.0
10.|-- 61.42.234.253 0.0% 10 4.4 4.0 1.4 10.4 3.6
11.|-- 1.213.105.38 0.0% 10 168.4 145.9 143.3 168.4 7.9
12.|-- 211.118.180.146 0.0% 10 140.5 140.5 134.6 148.4 4.5
13.|-- 144.232.154.205 0.0% 10 136.9 137.1 135.8 138.7 0.5
14.|-- 144.232.4.129 0.0% 10 144.7 146.4 144.7 150.0 1.5
15.|-- ix-ae-13-0.tcore1.eql-los-angeles.as6453.net 0.0% 10 134.4 136.2 134.4 150.1 4.9
16.|-- if-ae-30-2.tcore1.lvw-los-angeles.as6453.net 0.0% 10 216.4 219.9 216.4 239.1 6.9
17.|-- if-ae-8-2.tcore1.sv1-santa-clara.as6453.net 0.0% 10 220.0 220.1 220.0 220.5 0.0
18.|-- if-ae-0-2.tcore2.sv1-santa-clara.as6453.net 0.0% 10 216.5 216.5 216.3 216.9 0.0
19.|-- if-ae-18-4.tcore1.sqn-san-jose.as6453.net 0.0% 10 216.2 216.3 216.2 216.5 0.0
20.|-- if-ae-1-2.tcore2.sqn-san-jose.as6453.net 0.0% 10 223.2 223.4 223.0 224.4 0.3
21.|-- if-ae-29-2.tcore1.ct8-chicago.as6453.net 0.0% 10 217.3 216.8 216.6 217.3 0.0
22.|-- if-ae-22-2.tcore2.ct8-chicago.as6453.net 0.0% 10 220.0 219.9 219.7 220.0 0.0
23.|-- if-ae-30-2.tcore1.w6c-montreal.as6453.net 0.0% 10 222.7 223.4 222.5 229.6 2.1
24.|-- if-ae-12-2.tcore1.mtt-montreal.as6453.net 0.0% 10 232.9 224.5 222.8 232.9 3.2
25.|-- 64.86.31.62 0.0% 10 218.8 219.0 218.7 219.4 0.0
26.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

14/02/2019 13:39:12 UTC
--------------------

but I'm located in Eastern Canada.... depending on your physical location, you may or may not see the same issue.
Okay bro thanks for the info I will fallow up hopefully this will fix (code1016) problem..... :-)

02/14/2019 05:37 AMPosted by Boubou
@HappyPants...

Troubleshooting for Diablo III error 1016 :
https://us.battle.net/support/en/article/103102
(words in blue are links to additional information/procedures)

If the troubleshooting does not solve the issue, then contact Blizzard Support directly... https://us.battle.net/support/en/help/product/diablo3/273/277/channels
Pls do let them know that you are only playing on Asia region... I'm not sure if the US region Support can help you, but they will let you know if they cannot. You should also include a WinMTR and a looking glass with your ticket.
WinMTR : https://us.battle.net/support/en/article/27780
Looking-Glass : https://us-looking-glass.battle.net/ (make sure you select Korea for the Region, and Diablo 3 for Service)

---------------------------
Edit : My looking-glass shows some issue with one node in the Blizzard network
TRACEROUTE:
traceroute to 173.176.78.2 (173.176.78.2), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.393 ms 0.365 ms 0.343 ms
2 117.52.34.130 (117.52.34.130) 0.797 ms 0.801 ms 0.925 ms
3 117.52.161.193 (117.52.161.193) 1.072 ms 1.087 ms 1.139 ms
4 137.221.66.100 (137.221.66.100) 0.742 ms 0.747 ms 0.745 ms
5 137.221.84.68 (137.221.84.68) 3.634 ms 3.632 ms 3.629 ms
6 137.221.84.32 (137.221.84.32) 0.729 ms * *
7 110.45.174.217 (110.45.174.217) 0.796 ms 0.798 ms 0.794 ms
8 61-111-34-121.kidc.net (61.111.34.121) 2.818 ms 2.815 ms 2.304 ms
9 117.52.1.221 (117.52.1.221) 1.234 ms 1.227 ms 1.244 ms
10 1.208.105.45 (1.208.105.45) 1.637 ms 1.354 ms 1.339 ms
11 1.213.105.38 (1.213.105.38) 134.785 ms 134.799 ms 134.714 ms
12 211.118.180.146 (211.118.180.146) 143.543 ms 211.118.180.150 (211.118.180.150) 143.460 ms 211.118.180.146 (211.118.180.146) 143.699 ms
13 144.223.44.61 (144.223.44.61) 137.578 ms 137.592 ms 137.540 ms
14 144.232.4.129 (144.232.4.129) 150.209 ms 150.227 ms 150.222 ms
15 ix-ae-13-0.tcore1.eql-los-angeles.as6453.net (206.82.129.1) 134.648 ms 134.637 ms 134.615 ms

14/02/2019 13:39:12 UTC
--------------------

MTR:
Start: Thu Feb 14 13:39:12 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 117.52.34.2 0.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- 117.52.161.193 0.0% 10 0.9 1.4 0.9 3.7 0.6
4.|-- 137.221.66.96 0.0% 10 0.5 0.6 0.5 0.7 0.0
5.|-- 137.221.84.66 0.0% 10 2.7 6.1 0.9 14.9 4.3
6.|-- 137.221.84.36 30.0% 10 0.5 0.6 0.5 0.6 0.0
7.|-- 110.45.174.213 0.0% 10 0.5 0.5 0.5 0.6 0.0
8.|-- 182.162.152.9 0.0% 10 0.5 0.5 0.4 0.6 0.0
9.|-- 117.52.1.217 0.0% 10 1.2 1.3 1.1 2.1 0.0
10.|-- 61.42.234.253 0.0% 10 4.4 4.0 1.4 10.4 3.6
11.|-- 1.213.105.38 0.0% 10 168.4 145.9 143.3 168.4 7.9
12.|-- 211.118.180.146 0.0% 10 140.5 140.5 134.6 148.4 4.5
13.|-- 144.232.154.205 0.0% 10 136.9 137.1 135.8 138.7 0.5
14.|-- 144.232.4.129 0.0% 10 144.7 146.4 144.7 150.0 1.5
15.|-- ix-ae-13-0.tcore1.eql-los-angeles.as6453.net 0.0% 10 134.4 136.2 134.4 150.1 4.9
16.|-- if-ae-30-2.tcore1.lvw-los-angeles.as6453.net 0.0% 10 216.4 219.9 216.4 239.1 6.9
17.|-- if-ae-8-2.tcore1.sv1-santa-clara.as6453.net 0.0% 10 220.0 220.1 220.0 220.5 0.0
18.|-- if-ae-0-2.tcore2.sv1-santa-clara.as6453.net 0.0% 10 216.5 216.5 216.3 216.9 0.0
19.|-- if-ae-18-4.tcore1.sqn-san-jose.as6453.net 0.0% 10 216.2 216.3 216.2 216.5 0.0
20.|-- if-ae-1-2.tcore2.sqn-san-jose.as6453.net 0.0% 10 223.2 223.4 223.0 224.4 0.3
21.|-- if-ae-29-2.tcore1.ct8-chicago.as6453.net 0.0% 10 217.3 216.8 216.6 217.3 0.0
22.|-- if-ae-22-2.tcore2.ct8-chicago.as6453.net 0.0% 10 220.0 219.9 219.7 220.0 0.0
23.|-- if-ae-30-2.tcore1.w6c-montreal.as6453.net 0.0% 10 222.7 223.4 222.5 229.6 2.1
24.|-- if-ae-12-2.tcore1.mtt-montreal.as6453.net 0.0% 10 232.9 224.5 222.8 232.9 3.2
25.|-- 64.86.31.62 0.0% 10 218.8 219.0 218.7 219.4 0.0
26.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

14/02/2019 13:39:12 UTC
--------------------

but I'm located in Eastern Canada.... depending on your physical location, you may or may not see the same issue.
Hi Guys i get this error all the time and im in Australia.
and is very frustrating.
I also from Australia yes I know how you feel getting code 1016 error every time you logging and D3..... :-(
Me too. I'm also in Australia. SC2 is fine, but the D3 will crash in several mins....

Join the Conversation

Return to Forum