Someone just pointed out that I dumbassedly tracerouted to img.4chan.com, which is a linkfarm.
img.4chan.org is also reachable from AT&T in NY: Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 207.126.64.182, timeout is 2 seconds: .!..! Success rate is 40 percent (2/5), round-trip min/avg/max = 164/196/228 ms ny01-rtr# Type escape sequence to abort. Tracing the route to img.4chan.org (207.126.64.182) 1 12.94.163.57 8 msec 4 msec 4 msec 2 cr1.n54ny.ip.att.net (12.122.131.238) [MPLS: Label 16377 Exp 0] 8 msec 8 msec 8 msec 3 ggr7.n54ny.ip.att.net (12.122.131.97) 8 msec 4 msec 8 msec 4 192.205.35.10 8 msec 4 msec 4 msec 5 cr1-tengig-0-8-3-0.NewYork.savvis.net (204.70.198.13) 4 msec 8 msec 4 msec 6 cr1-pos-0-3-2-3.dallas.savvis.net (204.70.192.82) 48 msec 44 msec 44 msec 7 * * * 8 er1-te-3-1.dallasequinix.savvis.net (204.70.204.149) 48 msec 44 msec 44 msec 9 208.175.175.22 164 msec 172 msec 120 msec 10 unknown.xeex.net (216.152.253.26) 48 msec 48 msec 48 msec However, it's equally as unhealthy from Comcast: --- img.4chan.org ping statistics --- 110 packets transmitted, 77 packets received, 30% packet loss round-trip min/avg/max/stddev = 62.635/233.576/639.919/96.254 ms So, enough with the conspiracy theories already. On Sun, Jul 26, 2009 at 8:03 PM, David Temkin <dav...@gmail.com> wrote: > 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...@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. >> > >> > >
