I tried again this morning before going to work, same problem as yesterday: launcher stuck on "Loading", nothing happens, nothing moves, no "Play" button.

I tried Tunnel Bear as someone suggested, and I was able to update the launcher and download the patch from yesterday's update; I turned off the VPN once the launcher finished updating, and back on my usual connection I ran ESO64.exe directly to see if the problem was fixed; the games starts and I get to the login screen, which says "Could not retrieve announcements" and gives me the same error everybody gets.

On a side note, I am on Telecom 20Mbit (TIM Smart), not on fiber, and I am connected to the router through an Ethernet cable.

I am not using the white TIM Smart router, I am using a NetGear DGN2200, and I set it to use OpenDNS.

Now, it would be nice to know if Telecom did some changes on the routing that are blocking us or if it's somehow an issue on Zenimax or Akamai.

Junkriid wrote: »

Both me and my friend (both from italy) have the same issue. A couple of minutes with the loading message and then "Error 210 - PatchManifestError_DownloadFail" and the "Repair" button instead of "Play".

same here since yesterday but i am from Greece

tunnelbear is not free. i'm not going to pay 10 euros to play when i already pay 12 for my sub.
@ZOS_GinaBruno i know no one cares of italy and that you are all busy with summerset launch on console but could we get some tech support so that as someone has stated we can provide details to our isp? telecom is the main isp of italy , it's a lot of ppl.

Any neews about? Not that i think it's a zos issue, but maybe some help locating the problem would be great! Large portion of italian people is out for this problem.

Scusate la mia ignoranza ma cosa dovremmo chiedere esattamente a Tim? Non mi funziona più Eso? Non sono ironico, non so davvero cosa chiedere.

ZOS_GinaBruno wrote: »

Thanks everyone, just confirming we're seeing your posts and are actively investigating.

And we do care about Italia

Thanks you @ZOS_GinaBruno. Italy loves you

Having the same issue, I'm also using TIM. I can't access the main website at all, I pinged it and it timed out.

lol i told telecom i could not play eso and i got told to go play world of warcraft.. i swear it's what the guy on the phone told me.. i just hung the phone on him. @ZOS_GinaBruno
@BaneOfBattler calla tio

Let's try to keep it to English, so that everybody (ZOS employees and other forums users) can understand us more easily.

Tonnopesce wrote: »

Junkriid wrote: »

Raga questo problema probabilmente non riceverà un fix perchè mi sa che è un problema di quello schifo di Tim/Telecom. Vi consiglio vivamente TunnelBear come riportato in qualche post precedente. It's ridicolous I can't play a game without a Vpn but it seems it's a telecom problem and not Zos.

Tunnelbear non è esattamente sicuro adesso che è stato acquisito da macafee ci sono molti altri servizi che fanno lo stesso lavoro a prezzi più bassi.
COMUNQUE... Non è accettabile che dobbiamo pagare un servizio extra per giocare a un gioco nel quale onestamente abbiamo già sborsato fior di soldini.
Telecom dal canto loro non hanno idea di quale sia il problema ( sono riuscito a chiamare sta mattina) e non essendoci un problema non risolveranno nulla

Non è che a me cadano i soldi dall'aria e di certo nemmeno io voglio pagare per un Vpn quando già pago per un servizio internet, solo che, vedendo che finora non ci sono altre soluzioni, *** voluto provare e *** visto che con quello funziona. Poi ti da tipo 500 mb al mese se non lo paghi, quindi per giocare non si può di certo usare e per quanto riguarda la sicurezza, non ne *** idea e non saprei nemmeno quale Vpn potrei usare che sia più sicuro visto che fino a ieri non sapevo nemmeno cosa fosse un Vpn.. Infine non mi rincuora affatto sapere che già almeno tu ed un altro utente avete provato a contattare Telecom/Tim senza ottenere alcun risultato, anzi, all'altro utente hanno persino consigliato di andare a giocare su Wow, il che, se fosse vero, sarebbe esilarante ma sicuramente triste per noi giocatori.
Sorry, this was just to answer to Tonnopesce, no further informations given.

P.s. mi stanno censurando la prima persona del verbo avere xD

I asked a friend to perform a nestat -n with the bethesda launcher opened.

Looks like the launcher tries to concect to 4 different hosts.

These are the traceroutes to the hosts from a Telecom Italia connection:

root@cricchetto:~# traceroute 95.101.114.82
traceroute to 95.101.114.82 (95.101.114.82), 30 hops max, 60 byte packets
1 gateway (192.168.1.1) 1.028 ms 1.387 ms 1.753 ms
2 * * *
3 172.17.88.170 (172.17.88.170) 8.777 ms 172.17.88.166 (172.17.88.166) 10.164 ms 172.17.88.162 (172.17.88.162) 10.438 ms
4 172.17.89.230 (172.17.89.230) 10.782 ms 172.17.89.232 (172.17.89.232) 12.449 ms 172.17.89.230 (172.17.89.230) 12.627 ms
5 172.19.241.101 (172.19.241.101) 17.520 ms 20.920 ms 172.19.240.41 (172.19.240.41) 12.697 ms
6 a95-101-114-82.deploy.static.akamaitechnologies.com (95.101.114.82) 18.278 ms 17.306 ms 172.19.241.101 (172.19.241.101) 19.441 ms



root@cricchetto:~# traceroute 88.221.145.26
traceroute to 88.221.145.26 (88.221.145.26), 30 hops max, 60 byte packets
1 gateway (192.168.1.1) 0.951 ms 1.305 ms 1.678 ms
2 * * *
3 172.17.89.122 (172.17.89.122) 8.910 ms 172.17.88.170 (172.17.88.170) 10.190 ms 172.17.88.166 (172.17.88.166) 10.351 ms
4 172.17.89.230 (172.17.89.230) 10.483 ms 172.17.89.232 (172.17.89.232) 12.022 ms 12.183 ms
5 172.19.241.113 (172.19.241.113) 16.253 ms 172.19.241.101 (172.19.241.101) 18.546 ms 20.530 ms
6 172.19.240.57 (172.19.240.57) 19.907 ms a88-221-145-26.deploy.static.akamaitechnologies.com (88.221.145.26) 17.876 ms 17.695 ms



root@cricchetto:~# traceroute 159.100.230.100
traceroute to 159.100.230.100 (159.100.230.100), 30 hops max, 60 byte packets
1 gateway (192.168.1.1) 1.026 ms 1.383 ms 1.785 ms
2 * * *
3 172.17.89.122 (172.17.89.122) 8.924 ms 172.17.88.170 (172.17.88.170) 10.197 ms 172.17.89.208 (172.17.89.208) 10.467 ms
4 172.17.89.228 (172.17.89.228) 10.709 ms 12.253 ms 172.17.89.234 (172.17.89.234) 12.526 ms
5 172.19.177.18 (172.19.177.18) 17.837 ms 172.19.177.28 (172.19.177.28) 14.844 ms 15.011 ms
6 etrunk49.milano1.mil.seabone.net (195.22.205.98) 16.110 ms etrunk49.milano50.mil.seabone.net (195.22.205.116) 17.958 ms etrunk49.milano1.mil.seabone.net (195.22.205.98) 14.537 ms
7 ae21.milano51.mil.seabone.net (195.22.205.39) 16.170 ms 10.527 ms 11.341 ms
8 ntt-verio.milano51.mil.seabone.net (93.186.128.157) 14.694 ms 13.012 ms 12.584 ms
9 ae-1.r01.mlanit01.it.bb.gin.ntt.net (129.250.5.82) 23.610 ms 24.822 ms 22.129 ms
10 ae-2.r24.frnkge08.de.bb.gin.ntt.net (129.250.3.183) 24.750 ms 27.360 ms 25.574 ms
11 ae-13.r03.frnkge03.de.bb.gin.ntt.net (129.250.6.207) 28.349 ms ae-1.r04.frnkge08.de.bb.gin.ntt.net (129.250.3.218) 26.809 ms 27.193 ms
12 ae-1.a01.frnkge03.de.bb.gin.ntt.net (129.250.6.193) 34.755 ms 32.708 ms 31.707 ms
13 212.119.27.190 (212.119.27.190) 24.792 ms 212.119.27.178 (212.119.27.178) 27.794 ms 28.223 ms
14 po111.bs-b.sech-fra.netarch.akamai.com (72.52.48.202) 24.339 ms 22.502 ms po110.bs-b.sech-fra.netarch.akamai.com (72.52.48.200) 24.994 ms
15 ae121.access-a.sech-fra.netarch.akamai.com (72.52.48.205) 22.529 ms ae120.access-a.sech-fra.netarch.akamai.com (72.52.48.197) 24.914 ms 26.000 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *





root@cricchetto:~# traceroute 198.20.198.110
traceroute to 198.20.198.110 (198.20.198.110), 30 hops max, 60 byte packets
1 gateway (192.168.1.1) 0.904 ms 1.260 ms 1.632 ms
2 * * *
3 172.17.88.170 (172.17.88.170) 8.890 ms 9.058 ms 172.17.89.204 (172.17.89.204) 10.200 ms
4 172.17.89.232 (172.17.89.232) 10.371 ms 172.17.89.228 (172.17.89.228) 10.489 ms 12.008 ms
5 172.19.177.18 (172.19.177.18) 17.885 ms 172.19.177.28 (172.19.177.28) 13.479 ms 14.811 ms
6 etrunk49.milano1.mil.seabone.net (195.22.205.98) 14.968 ms 13.821 ms 13.858 ms
7 ae20.milano51.mil.seabone.net (195.22.205.13) 18.376 ms ae21.milano51.mil.seabone.net (195.22.205.39) 10.066 ms ae20.milano51.mil.seabone.net (195.22.205.13) 14.881 ms
8 ntt-verio.milano51.mil.seabone.net (93.186.128.157) 14.894 ms 13.311 ms 14.711 ms
9 ae-1.r01.mlanit01.it.bb.gin.ntt.net (129.250.5.82) 24.067 ms 23.997 ms 22.354 ms
10 ae-2.r24.frnkge08.de.bb.gin.ntt.net (129.250.3.183) 24.636 ms 27.323 ms 25.632 ms
11 ae-13.r03.frnkge03.de.bb.gin.ntt.net (129.250.6.207) 28.149 ms 25.119 ms 25.084 ms
12 ae-1.a01.frnkge03.de.bb.gin.ntt.net (129.250.6.193) 24.921 ms ae-0.a01.frnkge03.de.bb.gin.ntt.net (129.250.6.112) 25.037 ms ae-1.a01.frnkge03.de.bb.gin.ntt.net (129.250.6.193) 24.889 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I'm going to share my traceroute here. Seems like a Frankfurt Akamai node is down.

same problem for me, Italy and Telecom connection

This morning there were many italian website with huge problems, and probably it all started yesterday and still is not fixed. Too bad that Telecom Italia is not giving us info about what is going on...

You can temporarily use a PPPoE connection to bypass the problem. Check how to set it up here: https://assistenzatecnica.tim.it/at/portals/assistenzatecnica.portal?_nfpb=true&nodeId=/AT_REPOSITORY/874038#874038