Hi all
Anbody else having problems to reach large websites, such as www.microsoft.com or www.dell.com? Problems in or to the akamai network?
Trying from AS13030 (Init7) here...
Cheers,
Mike
dell.com working perfectly, from init7-VDSL Am 28.01.2008 um 17:20 schrieb Mike Kellenberger:
Hi all
Anbody else having problems to reach large websites, such as www.microsoft.com or www.dell.com? Problems in or to the akamai network?
Trying from AS13030 (Init7) here...
Cheers,
Mike
-- Mike Kellenberger mike.kellenberger@escapenet.ch Escapenet - the Web Company Tel +41 52 235 0700 http://www.escapenet.ch Skype mikek70atwork _______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
dell.com works, but try any other host that is being contacted while loading www.dell.com and is hosted by akamai, such as i.dell.com
Freundliche Grüsse
dell.com works, but try any other host that is being contacted while loading www.dell.com and is hosted by akamai, such as i.dell.com
No problem via Bluewin-DSL:
$ telnet i.dell.com 80 Trying 212.243.223.139... Connected to i.dell.com (212.243.223.139). Escape character is '^]'. HEAD / HTTP/1.0
HTTP/1.0 400 Bad Request Server: AkamaiGHost Mime-Version: 1.0 Content-Type: text/html Content-Length: 187 Expires: Mon, 28 Jan 2008 17:05:56 GMT Date: Mon, 28 Jan 2008 17:05:56 GMT Connection: close
(Bad Request ? WTF?)
hm... from AS12429 its working fine. your problem sounds for me like a MTU and/or firewall problem...
-steven
Mike Kellenberger schrieb:
Hi all
Anbody else having problems to reach large websites, such as www.microsoft.com or www.dell.com? Problems in or to the akamai network?
Trying from AS13030 (Init7) here...
Cheers,
Mike
Hello
Steven Glogger wrote:
hm... from AS12429 its working fine. your problem sounds for me like a MTU and/or firewall problem...
I don't think so, I could also not reaching http://www.sf.tv/ around 20:00, but now it is working again.
During the outage (hop 3 + 4 are ch-zrh01a-ra1-ge-1-1-0.aorta.net [213.46.171.49]):
fabian@flashback:~$ traceroute www.sf.tv traceroute: Warning: www.sf.tv has multiple addresses; using 80.67.84.75 traceroute to www.sf.tv.edgesuite.net (80.67.84.75), 64 hops max, 40 byte packets 1 gate2.home4u.ch (62.2.85.177) 2.090 ms 1.683 ms 1.139 ms 2 cc-10-179-64-1.home4u.ch (10.179.64.1) 8.117 ms 6.147 ms 4.760 ms 3 * * * 4 * * * 5 tix2-nap.netarch.akamai.com (194.42.48.48) 15.525 ms 5.481 ms 6.043 ms 6 * * * 7 * *^C fabian@flashback:~$ host www.sf.tv www.sf.tv is an alias for www.sf.tv.edgesuite.net. www.sf.tv.edgesuite.net is an alias for a1133.g.akamai.net. a1133.g.akamai.net has address 80.67.84.75 a1133.g.akamai.net has address 80.67.84.74 fabian@flashback:~$
Now it looks different:
fabian@flashback:~$ traceroute www.sf.tv traceroute: Warning: www.sf.tv has multiple addresses; using 212.243.221.214 traceroute to www.sf.tv.edgesuite.net (212.243.221.214), 64 hops max, 40 byte packets 1 gate2.home4u.ch (62.2.85.177) 47.432 ms 1.574 ms 1.106 ms 2 cc-10-179-64-1.home4u.ch (10.179.64.1) 32.915 ms 4.358 ms 8.884 ms 3 * * * 4 * * * 5 i79tix-015-gig2-4.bb.ip-plus.net (164.128.22.9) 17.091 ms 20.524 ms 9.976 ms 6 i79zhh-015-xxx1-4.bb.ip-plus.net (138.187.129.73) 18.855 ms 7.312 ms 25.770 ms 7 i79zhh-005-gig6-0x2.bb.ip-plus.net (138.187.129.45) 23.617 ms 6.916 ms 5.532 ms 8 i79zhh-101-vla201.bb.ip-plus.net (138.187.129.42) 7.519 ms 6.321 ms 7.802 ms 9 212.243.221.214 (212.243.221.214) 16.905 ms 8.681 ms 7.759 ms fabian@flashback:~$ host www.sf.tv www.sf.tv is an alias for www.sf.tv.edgesuite.net. www.sf.tv.edgesuite.net is an alias for a1133.g.akamai.net. a1133.g.akamai.net has address 212.243.221.214 a1133.g.akamai.net has address 212.243.221.208 fabian@flashback:~$
Seems really to have been a problem somewhere on Akamai's network, also i.dell.com does resolv the same now:
fabian@flashback:~$ host i.dell.com i.dell.com is an alias for img.dell-cidr.akadns.net. img.dell-cidr.akadns.net is an alias for img.dell.com.edgesuite.net. img.dell.com.edgesuite.net is an alias for a569.g.akamai.net. a569.g.akamai.net has address 212.243.221.208 a569.g.akamai.net has address 212.243.221.214 fabian@flashback:~$
Could it be possible, that edgesuite.net/akamai.net is doing anycast [1] with its IP addresses? This would explain why it could be reached from some places but not from others.
[1] http://en.wikipedia.org/wiki/Anycast
bye Fabian
Same problem here
tracert www.sf.tv
from home Routenverfolgung zu a1133.g.akamai.net [80.67.84.74] über maximal 30 Abschnitte :
1 1 ms 1 ms 1 ms smc.senntec.ch [10.1.1.1] 2 3 ms 3 ms 3 ms eth0.r1.senn.ch [213.144.132.49] 3 12 ms 13 ms 13 ms lo0.lns1.bbcs.init7.net [213.144.128.205] 4 13 ms 17 ms 23 ms r1.core.init7.net [213.144.128.1] 5 12 ms 13 ms 13 ms tix2-nap.netarch.akamai.com [194.42.48.48] 6 *
from switch
Traceroute to 80.67.84.74
traceroute to 80.67.84.74 (80.67.84.74), 30 hops max, 40 byte packets 1 swiCS5-V108 (130.59.108.5) 0.267 ms 0.204 ms 0.194 ms 2 swiCS3-10GE-1-3 (130.59.15.189) 0.248 ms 0.212 ms 0.214 ms 3 swiEZ2-10GE-5-2 (130.59.36.18) 0.221 ms 0.212 ms 0.219 ms 4 swiIX1-10GE-1-1 (130.59.36.250) 0.386 ms 0.354 ms 0.340 ms 5 tix2-nap.netarch.akamai.com (194.42.48.48) 0.509 ms 0.504 ms 0.323 ms 6 * * *
; <<>> DiG 9.3.1 <<>> www.sf.tv @213.144.132.52 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53005 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 9, ADDITIONAL: 0
;; QUESTION SECTION: ;www.sf.tv. IN A
;; ANSWER SECTION: www.sf.tv. 1779 IN CNAME www.sf.tv.edgesuite.net. www.sf.tv.edgesuite.net. 21579 IN CNAME a1133.g.akamai.net. a1133.g.akamai.net. 20 IN A 80.67.84.74 a1133.g.akamai.net. 20 IN A 80.67.84.75
;; AUTHORITY SECTION: g.akamai.net. 1778 IN NS n5g.akamai.net. g.akamai.net. 1778 IN NS n6g.akamai.net. g.akamai.net. 1778 IN NS n7g.akamai.net. g.akamai.net. 1778 IN NS n8g.akamai.net. g.akamai.net. 1778 IN NS n0g.akamai.net. g.akamai.net. 1778 IN NS n1g.akamai.net. g.akamai.net. 1778 IN NS n2g.akamai.net. g.akamai.net. 1778 IN NS n3g.akamai.net. g.akamai.net. 1778 IN NS n4g.akamai.net.
;; Query time: 574 msec ;; SERVER: 213.144.132.52#53(213.144.132.52) ;; WHEN: Mon Jan 28 23:58:31 2008 ;; MSG SIZE rcvd: 287
was ok a few minutes ago, now the problem is back...
tracert www.sf.tv
Tracing route to a1133.g.akamai.net [80.67.84.75] over a maximum of 30 hops:
1 11 ms <1 ms <1 ms 192.168.10.1 2 7 ms 7 ms 7 ms r1.escapenet.init7.net [82.197.167.89] 3 7 ms 7 ms 7 ms 82.197.174.1 4 8 ms 7 ms 7 ms r1.core.init7.net [213.144.128.1] 5 8 ms 8 ms 8 ms tix2-nap.netarch.akamai.com [194.42.48.48] 6 *
tracert i.dell.com
Tracing route to a569.g.akamai.net [80.67.84.74] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.10.1 2 7 ms 7 ms 7 ms r1.escapenet.init7.net [82.197.167.89] 3 7 ms 7 ms 7 ms 82.197.174.1 4 8 ms 7 ms 7 ms r1.core.init7.net [213.144.128.1] 5 8 ms 8 ms 8 ms tix2-nap.netarch.akamai.com [194.42.48.48] 6 * *
Freundliche Grüsse
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Hello,
Works perfectly from here.
Cu,
Nico
was ok a few minutes ago, now the problem is back...
tracert www.sf.tv
Tracing route to a1133.g.akamai.net [80.67.84.75] over a maximum of 30 hops:
1 11 ms <1 ms <1 ms 192.168.10.1 2 7 ms 7 ms 7 ms r1.escapenet.init7.net [82.197.167.89] 3 7 ms 7 ms 7 ms 82.197.174.1 4 8 ms 7 ms 7 ms r1.core.init7.net [213.144.128.1] 5 8 ms 8 ms 8 ms tix2-nap.netarch.akamai.com [194.42.48.48] 6 *
tracert i.dell.com
Tracing route to a569.g.akamai.net [80.67.84.74] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.10.1 2 7 ms 7 ms 7 ms r1.escapenet.init7.net [82.197.167.89] 3 7 ms 7 ms 7 ms 82.197.174.1 4 8 ms 7 ms 7 ms r1.core.init7.net [213.144.128.1] 5 8 ms 8 ms 8 ms tix2-nap.netarch.akamai.com [194.42.48.48] 6 * *
Freundliche Grüsse
Mike Kellenberger wrote:
was ok a few minutes ago, now the problem is back...
Access to dell.ch, ikea.com and sf.tv are now all fine from here (easynet).
/Per Jessen, Herrliberg
I've tested some connections I have access to with a pretty interesting result:
- Two BB accesses within AS8404, one got access to [1], the other one not! - One ADSL behind AS21494 works fine. - Upstream traffic over AS13030 works fine.
To me it seems like a large IP block on Akamai spread over several AS, rather than an routing issue.
Here some traces:
[AS8404 doesn't work] root@gnat:/home/dkamm# traceroute -I akamai.com traceroute to akamai.com (124.40.41.103), 30 hops max, 40 byte packets 1 gw.office.hostpoint (192.168.0.1) 0.303 ms 0.300 ms 0.301 ms 2 10.167.128.1 (10.167.128.1) 120.307 ms 120.408 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * us-was02a-rd1-pos-1-0.aorta.net (213.46.160.106) 114.573 ms 119.279 ms 8 213.46.190.10 (213.46.190.10) 200.485 ms 200.502 ms * 9 * * * 10 * * * 11 * * * 12 * * * 13 * 124.40.41.103 (124.40.41.103) 312.662 ms 316.452 ms
[AS8404 works] (09:40:28 AM) cal: antarctica:root # traceroute -I akamai.com traceroute: Warning: akamai.com has multiple addresses; using 212.23.33.16 traceroute to akamai.com (212.23.33.16), 64 hops max, 72 byte packets 1 10.167.128.1 (10.167.128.1) 8.226 ms 8.688 ms 6.696 ms 2 * * * 3 * * * 4 194.42.48.74 (194.42.48.74) 6.537 ms 6.785 ms 6.881 ms 5 PO6-0.zrh-jos-access-1.interoute.net (212.23.43.225) 16.112 ms 25.241 ms 16.107 ms 6 PO10-0.fra-006-core-1.interoute.net (212.23.43.214) 16.478 ms 84.129 ms 25.999 ms 7 Gi7-0-0.fra-006-access-2.interoute.net (212.23.42.138) 16.246 ms 24.443 ms 15.907 ms 8 212.23.33.16 (212.23.33.16) 19.111 ms 14.429 ms 19.147 ms
[AS21494 works] dani@turtle:~$ sudo traceroute -I akamai.com [sudo] password for dani: traceroute to akamai.com (84.53.136.81), 30 hops max, 40 byte packets 1 fritz.fonwlan.box (10.0.36.1) 0.855 ms 4.834 ms 4.838 ms 2 zh1-lns01-lo1.noc.green.ch (80.254.161.230) 8.915 ms 10.382 ms 12.629 ms 3 zh1-cor01-vlan200.noc.green.ch (80.254.161.49) 14.818 ms 16.788 ms 18.450 ms 4 gi2-2.213.core01.zrh01.atlas.cogentco.com (130.117.243.173) 20.958 ms 22.591 ms 24.788 ms 5 po6-0.core01.str01.atlas.cogentco.com (130.117.0.53) 75.911 ms 75.915 ms * 6 te1-4.ccr01.str01.atlas.cogentco.com (130.117.0.190) 35.711 ms 35.550 ms 37.915 ms 7 te7-1.mpd02.fra03.atlas.cogentco.com (130.117.3.81) 42.448 ms 14.337 ms 15.682 ms 8 te3-1.ccr01.ams03.atlas.cogentco.com (130.117.2.202) 25.273 ms 20.738 ms 22.565 ms 9 amsix-ams5.netarch.akamai.com (195.69.144.168) 25.149 ms 21.283 ms 23.363 ms 10 84.53.136.81 (84.53.136.81) 25.686 ms 27.271 ms 28.730 ms
[AS29097 works] root@ray:/home/dani# traceroute -I akamai.com traceroute to akamai.com (84.53.136.81), 30 hops max, 40 byte packets 1 pcore01-vl100.zrh01.hostpoint.ch (217.26.49.3) 10.322 ms 14.252 ms 14.386 ms 2 edge-02-0-2.zrh01.hostpoint.ch (217.26.48.3) 13.865 ms 14.036 ms 14.145 ms 3 gw-hostpoint.init7.net (82.197.163.17) 14.509 ms 14.654 ms 14.775 ms 4 r1.core.init7.net (213.144.128.1) 14.887 ms 15.017 ms 15.136 ms 5 r1ams.ce.init7.net (82.197.168.97) 24.252 ms 24.446 ms 24.563 ms 6 amsix-ams5.netarch.akamai.com (195.69.144.168) 24.692 ms 19.390 ms 19.849 ms 7 84.53.136.81 (84.53.136.81) 19.575 ms 19.739 ms 20.112 ms
Last hop of the one who doesn't work is within NTT in Japan.
HTH - Cheerz - Dan
[1]: I've tested sf.tv, microsoft.com, dell.ch and yahoo.com
could be some kind of dns issue as well
nslookup from here:
nslookup i.dell.com
Non-authoritative answer: Name: a569.g.akamai.net Addresses: 80.67.84.75, 80.67.84.74 Aliases: i.dell.com, img.dell-cidr.akadns.net img.dell.com.edgesuite.net
nslookup from ip-plus or any other online nslookup i could find:
Non-authoritative answer: Name: a569.g.akamai.net Addresses: 212.243.221.214, 212.243.221.208 Aliases: i.dell.com, img.dell-cidr.akadns.net img.dell.com.edgesuite.net
cleared all caches on our cache-only nameservers; not using forwarders; but still always get the same results back
I'm stumped...
Regards,
Mike
could be some kind of dns issue as well
[...]
cleared all caches on our cache-only nameservers; not using forwarders; but still always get the same results back
That's exactly how the Akamai DNS is supposed to work. You'll always get different results from different AS's as the Akamai DNS tries to find the nearest Akamai cache cluster using some BGP + DNS magic.
See: http://web.archive.org/web/20030302122757/http://www.cs.washington.edu/h omes/ratul/akamai.html
cheers, - Fabian
ok, didn't think of that, makes sense of course...
so it looks like some sort of problem between init7 and akamai after all
init7 is looking into it at this moment.
regards,
mike
8404 has some Akamai servers inhouse
-----Original Message----- From: swinog-bounces@lists.swinog.ch [mailto:swinog-bounces@lists.swinog.ch] On Behalf Of Daniel Kamm Sent: mardi, 29. janvier 2008 09:49 To: swinog@swinog.ch Subject: Re: AW: [swinog] Large IP Block at Akamai?
I've tested some connections I have access to with a pretty interesting result:
- Two BB accesses within AS8404, one got access to [1], the other one not! - One ADSL behind AS21494 works fine. - Upstream traffic over AS13030 works fine.
To me it seems like a large IP block on Akamai spread over several AS, rather than an routing issue.
Here some traces:
[AS8404 doesn't work] root@gnat:/home/dkamm# traceroute -I akamai.com traceroute to akamai.com (124.40.41.103), 30 hops max, 40 byte packets 1 gw.office.hostpoint (192.168.0.1) 0.303 ms 0.300 ms 0.301 ms 2 10.167.128.1 (10.167.128.1) 120.307 ms 120.408 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * us-was02a-rd1-pos-1-0.aorta.net (213.46.160.106) 114.573 ms 119.279 ms 8 213.46.190.10 (213.46.190.10) 200.485 ms 200.502 ms * 9 * * * 10 * * * 11 * * * 12 * * * 13 * 124.40.41.103 (124.40.41.103) 312.662 ms 316.452 ms
[AS8404 works] (09:40:28 AM) cal: antarctica:root # traceroute -I akamai.com traceroute: Warning: akamai.com has multiple addresses; using 212.23.33.16 traceroute to akamai.com (212.23.33.16), 64 hops max, 72 byte packets 1 10.167.128.1 (10.167.128.1) 8.226 ms 8.688 ms 6.696 ms 2 * * * 3 * * * 4 194.42.48.74 (194.42.48.74) 6.537 ms 6.785 ms 6.881 ms 5 PO6-0.zrh-jos-access-1.interoute.net (212.23.43.225) 16.112 ms 25.241 ms 16.107 ms 6 PO10-0.fra-006-core-1.interoute.net (212.23.43.214) 16.478 ms 84.129 ms 25.999 ms 7 Gi7-0-0.fra-006-access-2.interoute.net (212.23.42.138) 16.246 ms 24.443 ms 15.907 ms 8 212.23.33.16 (212.23.33.16) 19.111 ms 14.429 ms 19.147 ms
[AS21494 works] dani@turtle:~$ sudo traceroute -I akamai.com [sudo] password for dani: traceroute to akamai.com (84.53.136.81), 30 hops max, 40 byte packets 1 fritz.fonwlan.box (10.0.36.1) 0.855 ms 4.834 ms 4.838 ms 2 zh1-lns01-lo1.noc.green.ch (80.254.161.230) 8.915 ms 10.382 ms 12.629 ms 3 zh1-cor01-vlan200.noc.green.ch (80.254.161.49) 14.818 ms 16.788 ms 18.450 ms 4 gi2-2.213.core01.zrh01.atlas.cogentco.com (130.117.243.173) 20.958 ms 22.591 ms 24.788 ms 5 po6-0.core01.str01.atlas.cogentco.com (130.117.0.53) 75.911 ms 75.915 ms * 6 te1-4.ccr01.str01.atlas.cogentco.com (130.117.0.190) 35.711 ms 35.550 ms 37.915 ms 7 te7-1.mpd02.fra03.atlas.cogentco.com (130.117.3.81) 42.448 ms 14.337 ms 15.682 ms 8 te3-1.ccr01.ams03.atlas.cogentco.com (130.117.2.202) 25.273 ms 20.738 ms 22.565 ms 9 amsix-ams5.netarch.akamai.com (195.69.144.168) 25.149 ms 21.283 ms 23.363 ms 10 84.53.136.81 (84.53.136.81) 25.686 ms 27.271 ms 28.730 ms
[AS29097 works] root@ray:/home/dani# traceroute -I akamai.com traceroute to akamai.com (84.53.136.81), 30 hops max, 40 byte packets 1 pcore01-vl100.zrh01.hostpoint.ch (217.26.49.3) 10.322 ms 14.252 ms 14.386 ms 2 edge-02-0-2.zrh01.hostpoint.ch (217.26.48.3) 13.865 ms 14.036 ms 14.145 ms 3 gw-hostpoint.init7.net (82.197.163.17) 14.509 ms 14.654 ms 14.775 ms 4 r1.core.init7.net (213.144.128.1) 14.887 ms 15.017 ms 15.136 ms 5 r1ams.ce.init7.net (82.197.168.97) 24.252 ms 24.446 ms 24.563 ms 6 amsix-ams5.netarch.akamai.com (195.69.144.168) 24.692 ms 19.390 ms 19.849 ms 7 84.53.136.81 (84.53.136.81) 19.575 ms 19.739 ms 20.112 ms
Last hop of the one who doesn't work is within NTT in Japan.
HTH - Cheerz - Dan
[1]: I've tested sf.tv, microsoft.com, dell.ch and yahoo.com
_______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
On Tue, 2008-01-29 at 01:05 -0800, Christian Jouas wrote:
8404 has some Akamai servers inhouse
This is it!
Changed nameserver to AS8404 nameservers, Sites had been available again. So it seems that Akamai traffic is not allowed to cross AS8404 but has to be loaded from the Akamai servers within AS8404.
Is that a likeley setup or a configuration failure? Am I bound to change my resolvers?
Cheerz - Dan
Mike Kellenberger wrote:
Hi all
Anbody else having problems to reach large websites, such as www.microsoft.com or www.dell.com? Problems in or to the akamai network?
I've been unable to get to www.dell.ch since sometime yesterday at least.
/Per Jessen, Herrliberg
Hi Mike
Am Montag, 28. Januar 2008 17:20 schrieb Mike Kellenberger:
Anbody else having problems to reach large websites, such as www.microsoft.com or www.dell.com? Problems in or to the akamai network?
Trying from AS13030 (Init7) here...
I am also Init7 ADSL customer, and it looks similar from my side, reaching microsoft or dell as well as ebay.com or ikea.com is nearly impossible. I restarted my DSL-Modem and tried it on two Computers with different opearating systems, but it was still not working. I now switched to my Sunrise Backup-Link over EDGE, and now everything seesm to work fine again (although it is a bit slow), so there must be a problem in the init7 network.
Greetingd Peter
-
Adrian Senn -
Adrian Ulrich -
Christian Jouas -
Daniel Kamm -
Fabian Uebersax -
Fabian Wenk -
Mike Kellenberger -
Nicolas Strina -
Per Jessen -
Peter Rohrer -
Silvan Gebhardt -
Steven Glogger