Akamai Timeouts with German Websites and OpenDNS

Since the beginning of this year I get timeouts and very low loading times on multiple German websites,
for example
xing.de
bild.de
bmw.de
audi.de

Other websites works quite well, e.g. telekom.de or heise.de

ISP: Deutsche Telekom (DSL 16Mbit/s)
DNS-Provider: OpenDNS (208.67.222.222,208.67.220.220)

All these problematic websites have one thing in common: they use a CDN, here Akamai.

Example:

http://bild.de

Media_httpbilderbildd_sbgzi

dig @208.67.222.222 bilder.bild.de

;; ANSWER SECTION:
bilder.bild.de.        145    IN    CNAME    bilder.bild.de.edgesuite.net.
bilder.bild.de.edgesuite.net. 20630 IN    CNAME    a122.d.akamai.net.
a122.d.akamai.net.    5    IN    A    77.67.28.74
a122.d.akamai.net.    5    IN    A    77.67.28.91

There are 3 observations that could lead to the problem of timeouts of loading German websites with Deutsche Telekom.

1) OpenDNS requests are routed to NL not to DE

Why are OpenDNS requests routed through Deutsche Telekom to NL and not to DE?
OpenDNS operates server in Frankfurt/DE, but why are they not used?

traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  2.826 ms  1.365 ms  1.245 ms
 2  87.186.224.194 (87.186.224.194)  16.368 ms  17.943 ms  17.927 ms
 3  87.186.255.250 (87.186.255.250)  17.241 ms  18.430 ms  17.215 ms
 4  * * 194.25.210.46 (194.25.210.46)  32.941 ms
 5  ae-34-52.ebr2.berlin1.level3.net (4.69.146.153)  31.820 ms  30.188 ms  29.286 ms
 6  ae-3-3.ebr2.dusseldorf1.level3.net (4.69.133.146)  29.429 ms  28.465 ms  31.879 ms
 7  ae-46-46.ebr1.amsterdam1.level3.net (4.69.143.201)  31.685 ms
    ae-48-48.ebr1.amsterdam1.level3.net (4.69.143.209)  31.436 ms
    ae-45-45.ebr1.amsterdam1.level3.net (4.69.143.197)  33.533 ms
 8  ae-59-114.csw1.amsterdam1.level3.net (4.69.153.198)  36.278 ms
    ae-58-113.csw1.amsterdam1.level3.net (4.69.153.194)  32.136 ms
    ae-57-112.csw1.amsterdam1.level3.net (4.69.153.190)  32.282 ms
 9  ae-1-51.edge4.amsterdam1.level3.net (4.69.139.138)  31.865 ms  33.105 ms  31.975 ms
10  splice-comm.edge4.amsterdam1.level3.net (212.72.40.98)  39.748 ms  38.664 ms  40.013 ms

traceroute to 208.67.220.220 (208.67.220.220), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  5.176 ms  1.489 ms  3.031 ms
 2  87.186.224.194 (87.186.224.194)  16.335 ms  16.928 ms  16.552 ms
 3  87.186.255.242 (87.186.255.242)  16.533 ms  17.211 ms  18.996 ms
 4  194.25.210.46 (194.25.210.46)  30.249 ms  29.390 ms  28.991 ms
 5  ae-34-52.ebr2.berlin1.level3.net (4.69.146.153)  29.144 ms  26.905 ms  26.355 ms
 6  ae-3-3.ebr2.dusseldorf1.level3.net (4.69.133.146)  27.841 ms  28.808 ms  28.599 ms
 7  ae-48-48.ebr1.amsterdam1.level3.net (4.69.143.209)  32.860 ms
    ae-45-45.ebr1.amsterdam1.level3.net (4.69.143.197)  32.144 ms
    ae-46-46.ebr1.amsterdam1.level3.net (4.69.143.201)  30.932 ms
 8  ae-59-114.csw1.amsterdam1.level3.net (4.69.153.198)  32.617 ms  36.026 ms  31.629 ms
 9  ae-1-51.edge4.amsterdam1.level3.net (4.69.139.138)  32.384 ms  30.457 ms  30.320 ms
10  splice-comm.edge4.amsterdam1.level3.net (212.72.40.98)  40.033 ms  40.136 ms  39.262 ms

3) requesting different OpenDNS servers results in different Akamai servers

In my case here through ISP Deutsche Telekom, I get the answer from the NL OpenDNS server to Akamai Server 77.67.28.74 or 77.67.28.91.

#Amsterdam, The Netherlands
#    a122.d.akamai.net
#    bilder.bild.de.edgesuite.net
#    77.67.28.74
#    77.67.28.91
#

traceroute to 77.67.28.91 (77.67.28.91), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  4.592 ms  1.566 ms  1.381 ms
 2  87.186.224.194 (87.186.224.194)  17.199 ms  16.714 ms  18.311 ms
 3  87.186.255.246 (87.186.255.246)  60.847 ms  16.435 ms  15.820 ms
 4  f-ed3-i.f.de.net.dtag.de (62.154.14.198)  28.209 ms
    194.25.6.62 (194.25.6.62)  27.289 ms
    f-ed3-i.f.de.net.dtag.de (62.154.14.198)  26.678 ms
 5  194.25.211.134 (194.25.211.134)  27.124 ms  27.513 ms  34.102 ms
 6  xe-9-3-0.ams21.ip4.tinet.net (89.149.180.190)  34.250 ms
    xe-5-1-0.ams21.ip4.tinet.net (89.149.185.65)  30.561 ms
    xe-3-0-0.ams21.ip4.tinet.net (89.149.186.130)  32.908 ms
 7  77.67.28.91 (77.67.28.91)  30.941 ms  32.730 ms  31.004 ms

This response I get through other German DNS servers, e.g. Telekom, Hetzner, Vodafone, but not through OpenDNS.

#Frankfurt, Germany   
#    a122.d.akamai.net
#    bilder.bild.de.edgesuite.net
#    77.67.27.57
#    77.67.27.58

traceroute to 77.67.27.57 (77.67.27.57), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  5.600 ms  1.438 ms  1.159 ms
 2  87.186.224.194 (87.186.224.194)  16.280 ms  16.031 ms  16.660 ms
 3  87.186.255.242 (87.186.255.242)  46.383 ms  19.214 ms  16.272 ms
 4  f-ed3-i.f.de.net.dtag.de (62.154.14.186)  27.957 ms
    194.25.6.26 (194.25.6.26)  26.822 ms
    f-ed3-i.f.de.net.dtag.de (62.154.14.186)  26.968 ms
 5  194.25.211.134 (194.25.211.134)  25.488 ms  26.434 ms  28.173 ms
 6  xe-1-2-1.fra23.ip4.tinet.net (89.149.184.78)  26.193 ms
    xe-4-0-1.fra23.ip4.tinet.net (89.149.181.157)  28.130 ms
    xe-9-0-1.fra23.ip4.tinet.net (89.149.181.205)  26.784 ms
 7  77.67.27.57 (77.67.27.57)  25.829 ms  27.276 ms  25.926 ms

As the NL DNS servers are requested, different Akamai server are responsible for delivery: 77.67.28.74 or 77.67.28.91.

3) Akamai server 77.67.28.91 (NL) ping timeouts

Why are there ping timeouts to one of the NL akamai server through Deutsche Telekom ISP:

PING 77.67.28.91: 56 data bytes
64 bytes from 77.67.28.91: icmp_seq=0 ttl=58 time=43.979 ms
Request timeout for icmp_seq 1
64 bytes from 77.67.28.91: icmp_seq=2 ttl=58 time=37.295 ms
64 bytes from 77.67.28.91: icmp_seq=3 ttl=58 time=34.840 ms
64 bytes from 77.67.28.91: icmp_seq=4 ttl=58 time=32.596 ms
Request timeout for icmp_seq 5
64 bytes from 77.67.28.91: icmp_seq=6 ttl=58 time=36.561 ms
Request timeout for icmp_seq 7
64 bytes from 77.67.28.91: icmp_seq=8 ttl=58 time=36.848 ms
64 bytes from 77.67.28.91: icmp_seq=9 ttl=58 time=33.648 ms
64 bytes from 77.67.28.91: icmp_seq=10 ttl=58 time=34.241 ms
Request timeout for icmp_seq 11
64 bytes from 77.67.28.91: icmp_seq=12 ttl=58 time=37.528 ms
64 bytes from 77.67.28.91: icmp_seq=13 ttl=58 time=36.146 ms
^C
— bilder.bild.de ping statistics —
14 packets transmitted, 10 packets received, 28.6% packet loss
round-trip min/avg/max/stddev = 32.596/36.368/43.979/2.982 ms

traceroute to 77.67.28.91 (77.67.28.91), 64 hops max, 52 byte packets
 1  192.168.0.1 (192.168.0.1)  4.592 ms  1.566 ms  1.381 ms
 2  87.186.224.194 (87.186.224.194)  17.199 ms  16.714 ms  18.311 ms
 3  87.186.255.246 (87.186.255.246)  60.847 ms  16.435 ms  15.820 ms
 4  f-ed3-i.f.de.net.dtag.de (62.154.14.198)  28.209 ms
    194.25.6.62 (194.25.6.62)  27.289 ms
    f-ed3-i.f.de.net.dtag.de (62.154.14.198)  26.678 ms
 5  194.25.211.134 (194.25.211.134)  27.124 ms  27.513 ms  34.102 ms
 6  xe-9-3-0.ams21.ip4.tinet.net (89.149.180.190)  34.250 ms
    xe-5-1-0.ams21.ip4.tinet.net (89.149.185.65)  30.561 ms
    xe-3-0-0.ams21.ip4.tinet.net (89.149.186.130)  32.908 ms
 7  bilder.bild.de (77.67.28.91)  30.941 ms  32.730 ms  31.004 ms

This seems to be the root cause of the problem with accessing big German websites through Deutsche Telekom and OpenDNS.
Maybe it is routing problem from Akamai to Deutsche Telekom or an Akamai (77.67.28.91) problem itself.

The question is now which hostmaster can solve this problem: Akamai, OpenDNS, Deutsche Telekom?

[1] Similar T-online Forum Entry from another user at 2011-12-27 http://foren.t-online.de/foren/read/service/dsl-festnetz/internet-performance…

Advertisements
Tagged with:
Posted in Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s