Same from Germany, I can't reach download.laptop.org.
$ traceroute download.laptop.org
traceroute to pedal.laptop.org (18.85.2.148), 64 hops max, 52 byte packets
1 host.local (192.168.178.1) 1.051 ms 1.579 ms 0.976 ms
2 rdsl-mgdb-de01.nw.mediaways.net (213.20.59.129) 21.702 ms 22.358 ms
21.432 ms
3 xmws-mgdb-de01-gigaet-6-5.nw.mediaways.net (62.53.167.194) 22.644 ms
21.636 ms 21.658 ms
4 rmws-mgdb-de01-chan-2.nw.mediaways.net (213.20.150.17) 21.829 ms 22.569
ms 21.626 ms
5 rmwc-brln-de01-so-3-2-3-0.nw.mediaways.net (213.20.150.5) 24.350 ms
23.026 ms 24.119 ms
6 xe0-1-0-0-grtparix1.red.telefonica-wholesale.net.10.16.84.in-addr.arpa
(84.16.10.1) 44.480 ms
so1-3-0-0-grtparix1.red.telefonica-wholesale.net.10.16.84.in-addr.arpa
(84.16.10.213) 43.885 ms 45.233 ms
7 cogent-1-0-0-grtparix1.red.telefonica-wholesale.net (213.140.52.134)
146.137 ms 115.263 ms
cogent-7-3-0-grtparix1.red.telefonica-wholesale.net (213.140.52.210)
203.648 ms
8 te0-3-0-7.ccr21.par01.atlas.cogentco.com (154.54.39.73) 44.993 ms 44.295
ms 44.372 ms
9 te1-1.mag02.par01.atlas.cogentco.com (130.117.49.82) 204.130 ms
te7-1.mag02.par01.atlas.cogentco.com (130.117.3.238) 120.512 ms
te2-1.mag02.par01.atlas.cogentco.com (154.54.38.174) 160.504 ms
10 * * *
11 * * *
12 * * *
- Bert -
On 04.07.2011, at 01:17, Kevin Gordon wrote:
> Ed:
>
> Thanks for posting this.
>
> That would most likely explain why I cant get to download.laptop.org, ( which
> for me resolves to 18.85.2.148) but can get to build.laptop.org (which
> resloves to 18.85.2.147 for me). I time out from hop 9 on down to hop 30
> where it stops. Hop 8 (last one to respond) is from is a cogentco IP
> address, 154.54.40.174
>
> For the build.laptop.org, the tracert once it leaves cogent goes to
> 38.104.186.186, then to B24-RTR-3-BACKBONE.MIT.EDU. However there are two
> more hops within atlas.cogentco.com (te0-2-0-2.ccr21.bos01, and
> te0-1-0-0.ccr2.bos01) so it also may be a cogentco.com routing error.
>
> Cheers
>
> KG
>>
>> PS: I'll cross-post to devel, as I had mentioned my issue there too. Any
>> workaround?
>>
>> KG
>>
>> On Sun, Jul 3, 2011 at 5:11 PM, Ed McNierney <[email protected]> wrote:
>> That's an interesting report. I don't expect your ISP is Verizon FIOS, is
>> it?
>>
>> Could you send me (no to the whole list - it's not interesting or on-topic)
>> a traceroute from your machine to lists.laptop.org? There is nothing wrong
>> with lists.laptop.org and it hasn't been down for days - it's fine. But
>> there has been a problem routing to it since about a week ago. I originally
>> suspected it was a problem specific to me at home, where I use Verizon FIOS,
>> but then found that another Verizon FIOS user in Eastern Massachusetts had
>> the exact same symptom (you can route to 18.85.2.147 but not to
>> 18.85.2.148). So we've suspected it is a Verizon routing problem, and it
>> would be helpful to either confirm or disprove that theory with your data.
>> Thanks.
>>
>> - Ed
>>
>>
>> On Jul 3, 2011, at 4:57 PM, Yioryos Asprobounitis wrote:
>>
>> > Few days now lists.laptop.org is down.
>> > So it looks more than a temp glitch or update.
>> > Anybody has any info on the matter and when it may come back up?
_______________________________________________
Devel mailing list
[email protected]
http://lists.laptop.org/listinfo/devel
