Test your connectivity for World IPv6 Day

[ben at newnet.co.uk]

Hello,

Newnet, recieve prefix 2a00:19e8::/32 (where 2a00:19e8:20:1::aa and therfor AAAA www.ipv6matrix.org resides) from 
AS31493 (TWENTYTWENTYMEDIA)

    Network          Next Hop            Metric LocPrf Weight Path
*> 2a00:19e8::/32   2a01:178:500::6          0   1000    450 31493 i

In Newnet's defence this is a valid path in out BGP table, however this customer appears to not have a valid 
route/firewall once this is traffic is passed to them.
Newnet will not be blocking any traffic to the range 2a00:19e8::/32

Have you tried contacting Twenty Twenty Media?
Hope this helps

Regards
ben wilkinson
newnet plc

On 07/10/11 12:17, Jeroen Massar wrote:
> On 2011-10-07 12:39 , Olivier MJ Crepin-Leblond wrote:
>> Hello all,
>>
>> I am the Sys$admin @ www.ipv6matrix.org  and remind you of the
>> discussion 4 months ago about routing to www.ipv6matrix.org which went
>> wrong at our upstream providers on IPv6 day (8th June).
>> Well, either we must be very unlucky with our upstream providers, or the
>> IPv6 network is still far from production status, but here we go again,
>> since Sunday 7 September 2011, approx 21:00 UTC routing's gone wrong
>> again at our upsteam.
>
> Did you consider contacting your upstream?
>
>>   8  2a01:178:9191:3::17  141.502 ms  142.150 ms  141.355 ms
>>   9  2a01:178:500::6  142.529 ms  142.409 ms  142.002 ms
>> 10  2a01:178:500::6  142.364 ms !A  147.545 ms !A  144.714 ms !A
>
> Seems somebody is (A)dministratively denying your packets. That somebody
> seems to be the NewNet your mentioned before though.
>
>> From GRH it also seems that next to 9191 (NewNet) you have 8426 (Clara)
> as your upstreams. As such the traceroute you showed goes over the
> latter, while the inbound goes over NewNet.
>
> Only thing you can do is talk to your upstream to resolve this.
>
> Or a quick fix: don't announce your prefix over NewNet...
>
> Greets,
>   Jeroen
>