-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

| so it looks like some sort of problem between init7 and | akamai after all

DNS lookups for akamaized content (example used: members.spamcop.net) from a DNS server behind an Init7 DSL line (213.144.132.248/29) returns 80.67.84.74 and 80.67.84.83, both of which time out when connected on port 80.

Forwarding DNS requests through another DNS server located at Metanet (80.74.132.72/29) returns different IP addresses (212.243.221.208 and 212.243.221.214) which both work.

Traceroutes to 80.67.84.74/.83 time out at Akamai:

majestix:~ matthias$ traceroute 80.67.84.74 traceroute to 80.67.84.74 (80.67.84.74), 64 hops max, 40 byte packets ~ 1 router (192.168.1.254) 1.439 ms 1.069 ms 1.085 ms ~ 2 eth0.r1.mleisi.dsl.init7.net (213.144.132.249) 2.725 ms 2.645 ms 2.591 ms ~ 3 lo0.lns2.bbcs.init7.net (213.144.128.206) 8.108 ms 8.424 ms 8.019 ms ~ 4 r1.core.init7.net (213.144.128.1) 8.135 ms 8.331 ms 8.171 ms ~ 5 tix2-nap.netarch.akamai.com (194.42.48.48) 8.289 ms 8.659 ms 8.807 ms ~ 6 * * *

So it's most likely Akamai who has to fix things; affected would be everybody who gets directed to 80.67.84.<some> in the Akamai CDN.

- -- Matthias