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] [EMAIL PROTECTED]:/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] [EMAIL PROTECTED]:~$ 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] [EMAIL PROTECTED]:/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
RE: AW: [swinog] Large IP Block at Akamai?
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 ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
RE: AW: [swinog] Large IP Block at Akamai?
8404 has some Akamai servers inhouse -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Kamm Sent: mardi, 29. janvier 2008 09:49 To: [EMAIL PROTECTED] 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] [EMAIL PROTECTED]:/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] [EMAIL PROTECTED]:~$ 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] [EMAIL PROTECTED]:/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 ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
AW: [swinog] Large IP Block at Akamai?
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 -- Mike Kellenberger [EMAIL PROTECTED] Escapenet - the Web Company Tel +41 52 235 0700 http://www.escapenet.ch Skype mikek70atwork -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Daniel Kamm Gesendet: Dienstag, 29. Januar 2008 09:49 An: [EMAIL PROTECTED] Betreff: [Spam] 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] [EMAIL PROTECTED]:/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] [EMAIL PROTECTED]:~$ 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] [EMAIL PROTECTED]:/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 ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
RE: AW: [swinog] Large IP Block at Akamai?
On Tue, 2008-01-29 at 01:05 -0800, Christian Jouas wrote: 8404 has some Akamai servers inhouse And we are using our own name servers which are not behind 8404 access network. That could be the reason. Stdby... - Dan ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
