Can you guys ping d36kx37nk0bz9z.cloudfront.net in a command prompt and post what ip address it shows up as. This will give me an idea as to whether you’re downloading from the same data center or not.
I’ve also triggered a flush command for the file through Amazon’s servers just in case it had somehow got corrupted at the edge location you guys are ending up downloading from.
C:\xxxx>ping d36kx37nk0bz9z.cloudfront.net
Ping wird ausgeführt für d36kx37nk0bz9z.cloudfront.net [54.240.162.74] mit 32 By
tes Daten:
Antwort von 54.240.162.74: Bytes=32 Zeit=23ms TTL=55
Antwort von 54.240.162.74: Bytes=32 Zeit=22ms TTL=55
Antwort von 54.240.162.74: Bytes=32 Zeit=22ms TTL=55
Antwort von 54.240.162.74: Bytes=32 Zeit=22ms TTL=55
Ping-Statistik für 54.240.162.74:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 22ms, Maximum = 23ms, Mittelwert = 22ms
C:\xxxx>tracert d36kx37nk0bz9z.cloudfront.net
Routenverfolgung zu d36kx37nk0bz9z.cloudfront.net [54.240.162.74] über maximal 3
0 Abschnitte:
1 <1 ms <1 ms <1 ms xxxx
2 18 ms 17 ms 17 ms 87.186.224.68
3 18 ms 17 ms 17 ms 87.186.195.10
4 22 ms 22 ms 22 ms 217.239.48.162
5 22 ms 22 ms 22 ms ffm-b12-link.telia.net [213.248.103.169]
6 22 ms 22 ms 22 ms a100row-ic-151139-ffm-b12.c.telia.net [213.248.9
6.82]
7 * * * Zeitüberschreitung der Anforderung.
8 * * * Zeitüberschreitung der Anforderung.
9 22 ms 22 ms 23 ms 54.239.4.223
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 23 ms 22 ms 22 ms server-54-240-162-74.fra6.r.cloudfront.net [54.2
40.162.74]
Ablaufverfolgung beendet.i still can play at every time, but it need long time to start. And i can download the file without any problem.
Made ping and tracert tests twice to be sure …
PING:
Ping wird ausgefhrt fr d36kx37nk0bz9z.cloudfront.net [54.240.162.90] mit 32 Bytes Daten:
Antwort von 54.240.162.90: Bytes=32 Zeit=45ms TTL=54
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Ping-Statistik fr 54.240.162.90:
Pakete: Gesendet = 4, Empfangen = 1, Verloren = 3
(75% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 45ms, Maximum = 45ms, Mittelwert = 45ms
Ping wird ausgefhrt fr d36kx37nk0bz9z.cloudfront.net [54.240.162.90] mit 32 Bytes Daten:
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Antwort von 54.240.162.90: Bytes=32 Zeit=44ms TTL=54
Zeitberschreitung der Anforderung.
Ping-Statistik fr 54.240.162.90:
Pakete: Gesendet = 4, Empfangen = 1, Verloren = 3
(75% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 44ms, Maximum = 44ms, Mittelwert = 44ms
TRACERT:
Routenverfolgung zu d36kx37nk0bz9z.cloudfront.net [54.240.162.90] ber maximal 30 Abschnitte:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 17 ms 17 ms 17 ms 217.0.119.22
3 18 ms 19 ms 18 ms 87.186.198.170
4 21 ms 21 ms 21 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.62]
5 46 ms 46 ms 46 ms ffm-b12-link.telia.net [213.248.103.169]
6 47 ms 39 ms * a100row-ic-151139-ffm-b12.c.telia.net [213.248.96.82]
7 60 ms 47 ms * 54.239.107.102
8 45 ms 44 ms 44 ms 54.239.107.111
9 43 ms * 45 ms 54.239.5.57
10 * * * Zeitberschreitung der Anforderung.
11 * * * Zeitberschreitung der Anforderung.
12 * * * Zeitberschreitung der Anforderung.
13 * 44 ms 42 ms server-54-240-162-90.fra6.r.cloudfront.net [54.240.162.90]
Ablaufverfolgung beendet.
Routenverfolgung zu d36kx37nk0bz9z.cloudfront.net [54.240.162.90] ber maximal 30 Abschnitte:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 18 ms 18 ms 18 ms 217.0.119.22
3 18 ms 17 ms 18 ms 87.186.198.170
4 22 ms 21 ms 23 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.62]
5 46 ms 48 ms 54 ms ffm-b12-link.telia.net [213.248.103.169]
6 44 ms 43 ms 43 ms a100row-ic-151139-ffm-b12.c.telia.net [213.248.96.82]
7 * * 56 ms 54.239.107.102
8 * 35 ms 43 ms 54.239.107.111
9 * * 43 ms 54.239.5.57
10 * * * Zeitberschreitung der Anforderung.
11 * * * Zeitberschreitung der Anforderung.
12 * * * Zeitberschreitung der Anforderung.
13 45 ms 45 ms * server-54-240-162-90.fra6.r.cloudfront.net [54.240.162.90]
14 44 ms * 44 ms server-54-240-162-90.fra6.r.cloudfront.net [54.240.162.90]
Ablaufverfolgung beendet.
CONCLUSION
As you can see @Saint_X and i get a diffrent IP resolution for the same DNS Address
Saint: 54.240.162.74
Heurazio: 54.240.162.90
I can’t start the game at the moment …
C:\xxx>tracert d36kx37nk0bz9z.cloudfront.net
Routenverfolgung zu d36kx37nk0bz9z.cloudfront.net [54.240.162.90] über maximal 3
0 Abschnitte:
1 <1 ms <1 ms <1 ms xxx
2 17 ms 17 ms 18 ms 87.186.224.68
3 18 ms 17 ms 18 ms 87.186.195.14
4 22 ms 22 ms 21 ms 217.239.48.142
5 47 ms 47 ms 70 ms ffm-b12-link.telia.net [213.248.103.169]
6 46 ms 46 ms 46 ms a100row-ic-151139-ffm-b12.c.telia.net [213.248.96.82]
7 47 ms 47 ms 47 ms 54.239.5.22
8 47 ms 47 ms 46 ms 54.239.5.161
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * 46 ms 46 ms server-54-240-162-90.fra6.r.cloudfront.net [54.240.162.90]and i can still play, so i dont think it is the IP because I have this time the same IP(from the amazon cloud server) at the end.
and @Heurazio cant still connect he tried to connect the same time like i was testing now and still cant connect, but we have both get the same amazon cloud server. heurazio was testing with trancerout and canonnecting the game
checked it again …
Routenverfolgung zu d36kx37nk0bz9z.cloudfront.net [54.240.162.90] über maximal 3
0 Abschnitte:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 18 ms 17 ms 17 ms 217.0.119.22
3 17 ms 18 ms 18 ms 87.186.198.170
4 21 ms 21 ms 21 ms f-ed5-i.F.DE.NET.DTAG.DE [217.5.95.62]
5 46 ms 45 ms 45 ms ffm-b12-link.telia.net [213.248.103.169]
6 * * 43 ms a100row-ic-151139-ffm-b12.c.telia.net [213.248.96.82]
7 * * 47 ms 54.239.107.102
8 * * 44 ms 54.239.107.111
9 * 45 ms * 54.239.5.57
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * 44 ms * server-54-240-162-90.fra6.r.cloudfront.net [54.240.162.90]
14 44 ms * 45 ms server-54-240-162-90.fra6.r.cloudfront.net [54.240.162.90]
Ablaufverfolgung beendet.
now we have the same IP but i still can’t play
pinged and tracert too. That’s my results:
I can’t enter the game between 7 pm and 10 pm german timezone since the last 5 days.
Other times I could not try, because I work or sleep then 
But I have to say, it worked also in evenings in october and november.
First problems started at my first post.
From that time it was blocked for me in the evenings sometimes.
No possibilities to enter since 5 days is the first time now.
I guess, if I would try in the morning at 9 am, I can enter.
This leads me to following assumption:
I think it has to do with amount of information requesting users.
In morning or midday (during the week) I never had problems and probably still don’t have.
In the evenings there was sometimes this problem.
In the evening most people come home, and use their free time. So potentially more people interacting with thos servers.
Maybe they kinda run out of capacity and people who are too far away or have a “slow” connection cannot get enough information anymore. It sounds weird but what else is different in the evenings from all other times of the day?
After 0AM i can login (till around 10AM).
Same here … but i didn’t had time so i don’t know for sure when it started
unlikely (more likely is a problem with Load-Balancing)
VDSL 50k here … for sure not “slow”
For the record I get the following down in Munich.
James: 54.192.95.207
traceroute: d36kx37nk0bz9z.cloudfront.net has multiple addresses; using 54.192.95.254
And the game works.
If the game isn’t working, and you confirm that curl also fails?
It failed for heurazio, so I guess I will have the same effect.
Do you guys know something about your routers? I got a Fritz!box 7490.
Edit: have VDSL 16k btw
You need to curl the tzo file url, not the domain.
@Smoothy has informed me that EVE-Online is faced with the same problem.
The problem occurs in combination of cloudfront and some ISP (Telekom, Unitymedia). Some player report that it is working over VPN.
HTH
PS: @james: i changed the image above … now it’s showing the correct thing
I read through all posts since now they seem to have the issue still.
Another try for a solution or explanation was written here:
post 53:
sorry
for writing this in English here but I hope this helps someone else. As
I already mentioned in the English forums, I am pretty sure it’s a
problem between the Telekom’s network and parts of Amazon’s CDN, where
Eve stores its resources. I have seen this being reported in other
fields, not EVE related. I can’t say if this is a problem with the
peering between those two networks or with something in between.
This
translates in horrible download speeds. Also, even if there is nothing
to patch, the EVE client itself (even if all resources are downloaded)
still accesses some things from those CDN addresses. This means that
sometimes you log in and you see a black screen while “Loading
Resources” cycles in the lower left corner.
The “solution” I use
is to point some of the hostnames EVE uses to different IP addresses,
belonging to a different part of Amazon’s CDN network to which Telekom
seems to have a good connection.
Since I use my own DNS server, I
can do this easily. But even if you don’t, you should still be able to
do this by using Window’s host file (typically c:\windows\system32\drivers\etc\hosts).
54.230.200.26 cdn1.eveonline.com
54.230.200.69 cdn1.eveonline.com
54.230.200.61 cdn1.eveonline.com
54.230.200.95 cdn1.eveonline.com
54.230.200.97 cdn1.eveonline.com
54.230.200.109 cdn1.eveonline.com
54.230.200.62 cdn1.eveonline.com
54.230.200.73 cdn1.eveonline.com
54.230.92.92 binaries.eveonline.com
54.230.92.23 binaries.eveonline.com
54.230.92.13 binaries.eveonline.com
54.230.92.93 binaries.eveonline.com
54.230.92.52 binaries.eveonline.com
54.230.92.17 binaries.eveonline.com
54.230.92.78 binaries.eveonline.com
54.230.92.20 binaries.eveonline.com
Ever since I started using the above, I can again patch and play without problems.
Disclaimer: use this at your own risk. EVE can decide at any time to change those hostnames and then the launcher will break. But all you would have to do is remove those lines from your host file.
Hope this helps.
Answer Post 54:
==== English Version as answer to previous post ====
You can do this with your own DNS server… BUT…
…parsing the HOSTS file has no Round-Robin concept included.
So each query against the HOSTS gets only the first entry of a given host name as answer.
54.230.200.26 cdn1.eveonline.com
54.230.92.92 binaries.eveonline.com
All IP address entries below the first entry which points to the given name are not read.
So to manipulate the HOSTS this way is very dangerous and NOT to recommend.
If the first server .26 / .92 is offline, you will get NO connection.
==== German Version and additional a better, alternate tip ====
Das kann man mit einem eigenen DNS Server machen… ABER …
…abfrage der HOSTS Datei beinhaltet kein Round-Robin Konzept.
Jede Abfrage der HOSTS ergibt als Antwort immer nur den ersten Eintrag:
54.230.200.26 cdn1.eveonline.com
54.230.92.92 binaries.eveonline.com
Alle IP Adressen für denselben Servernamen unter diesem ersten Eintrag werden übergangen.
Die HOST in dieser Form zu ändern ist gefährlich und NICHT zu empfehlen!
Wenn der erste eingetragene Server (.26/.92) nicht antwortet, bekommt man gar keine Verbindung!
=== Alternative ===
Die bessere Variante ist, in der TCP/IP Konfiguration des Systems den DNS Server zu ändern, der abgefragt wird.
DNS Server in anderen Ländern antworten mit völlig anderen IP Adressen bei der Abfrage der Namen
‘cdn1.eveonline.com’ / ‘binaries.eveonline.com’.
Der Google DNS gibt zum Beispiel aus:
C:>nslookup binaries.eveonline.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8 <<<<<<<---- Google DNS Server
Nicht autorisierende Antwort:
Name: d17ueqc3zm9j8o.cloudfront.net
Addresses: 54.192.44.66
54.192.44.25
54.192.44.88
54.192.44.47
54.192.44.5
54.192.44.110
54.192.44.114
54.192.44.26
Aliases: binaries.eveonline.com
Ein DNS von FreeZone gibt diese aus:
C:>nslookup binaries.eveonline.com 37.235.1.174
Server: resolver1.freedns.zone.powered.by.emerion.com
Address: 37.235.1.174 <<<<<<<---- DNS Server von FreeZone - FreeDNS - https://freedns.zone/de/
Nicht autorisierende Antwort:
Name: d17ueqc3zm9j8o.cloudfront.net
Addresses: 54.230.15.18
54.230.15.108
54.230.15.64
54.230.15.45
54.230.15.97
54.230.15.35
54.230.15.87
54.230.15.32
Aliases: binaries.eveonline.com
Ein DNS Server in Reijkjavik, Island gibt diese IP Adressen aus:
C:>nslookup binaries.eveonline.com
Server: 25-81-126-149.ftth.simafelagid.is
Address: 149.126.81.25 <<<<<<<---- DNS Server in Island
Nicht autorisierende Antwort:
Name: d17ueqc3zm9j8o.cloudfront.net
Addresses: 216.137.63.254
216.137.63.118
216.137.63.88
216.137.63.14
216.137.63.44
216.137.63.69
216.137.63.157
216.137.63.138
Aliases: binaries.eveonline.com
Ein DNS Server in Moskau, Russland, gibt diese aus:
C:>nslookup binaries.eveonline.com
Server: host31-76.lease.p-t-k.net
Address: 178.217.31.76 <<<<<<<---- DNS Server in Russland
Nicht autorisierende Antwort:
Name: d17ueqc3zm9j8o.cloudfront.net
Addresses: 54.240.166.206
54.240.166.146
54.240.166.197
54.240.166.23
54.240.166.165
54.240.166.105
54.240.166.32
54.240.166.178
Aliases: binaries.eveonline.com
Den DNS, der die Adressen vom Vorposter ausgibt (54.230.200…) hab ich nicht gefunden…
Ich würde empfehlen den FreeZone DNS oben zu verwenden.
Hope it get’s us closer…
If you type “cloudfront telekom problems?” in google, you get quite a lot hits…
Did the download fail / get stuck again? Stuck at 5%
When we chatting about this issue today - our biggest suspect was the ISP and their routing hardware.
the download / curl has loose contact … it’s loading at 3-5kb/s and stops for a long period. than it continues loading at low rates (3-5kb/s) … and so on
I can start the game at the moment … It took some time (30s) to start but at least it started 
TRACERT
Routenverfolgung zu d36kx37nk0bz9z.cloudfront.net [54.240.162.50] über maximal 3
0 Abschnitte:
1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 17 ms 17 ms 17 ms 217.0.119.22
3 18 ms 19 ms 18 ms 87.186.198.170
4 22 ms 21 ms 21 ms 217.239.48.142
5 21 ms 21 ms 21 ms ffm-b12-link.telia.net [213.248.103.169]
6 22 ms 23 ms 21 ms a100row-ic-151139-ffm-b12.c.telia.net [213.248.96.82]
7 22 ms 22 ms 21 ms 54.239.4.248
8 23 ms 21 ms 21 ms 54.239.4.223
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 21 ms 23 ms 21 ms server-54-240-162-50.fra6.r.cloudfront.net [54.240.162.50]
Ablaufverfolgung beendet.
cURL
cURL finished fast as f***this time … 
And we changed nothing in between these attempts.
I’m far from a networking expert, but it feels like the issue is with your ISP.