AT&T. Layer 6-8 needed.

Mon Jul 27 03:03:57 UTC 2009

Perfectly reachable from AT&T in NY:

ny01-rtr#traceroute img.4chan.com

Type escape sequence to abort.
Tracing the route to img.4chan.com (208.73.210.27)

  1 12.94.163.57 8 msec 4 msec 4 msec
  2 cr1.n54ny.ip.att.net (12.122.131.238) [MPLS: Label 16370 Exp 0] 8 msec 8
msec 8 msec
  3 ggr4.n54ny.ip.att.net (12.122.131.25) 8 msec 8 msec 4 msec
  4 192.205.34.50 16 msec 4 msec 4 msec
  5 0.xe-5-0-3.XL4.NYC4.ALTER.NET (152.63.18.10) 36 msec 4 msec 8 msec
  6 0.so-6-0-0.XL2.LAX1.ALTER.NET (152.63.57.81) 76 msec 76 msec 76 msec
  7 POS7-0.GW4.LAX1.ALTER.NET (152.63.53.61) 76 msec 76 msec 76 msec
  8 oversee-gw.customer.alter.net (65.223.29.34) 76 msec 80 msec 80 msec
  9 208.73.208.10 80 msec 80 msec 76 msec
 10 img.4chan.com (208.73.210.27) 76 msec 76 msec 76 msec

Are you sure this isn't just a technical/routing issue versus a blocking
issue?  Seems like everyone's out to make a sensationalist story out of this
when it's unlikely that anyone's awake at AT&T on a Sunday afternoon who
could/would make such a change.

-Dave

On Sun, Jul 26, 2009 at 7:47 PM, jamie <j at arpa.com> wrote:

> img.4chan.org is the biggest site - I've already received six replies on
> top
> of the list-replies confirming (b/c they saw this problem mentioned on
> sites/blogs) filtering.
>
> technical information, traces, bgp views (esp. from singly-homed T
> customers), etc, encouraged
>
> -jamie
>
>
> >>
> > I don't see a below below.
> >
>