[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Backports.org



17  completel.155M.DOR002.versatel.de (62.214.64.122)  166 ms  165 ms
166 ms
18  fe4-0-0-20.bbr2.ess.completel.de (195.167.210.18)  264 ms  293 ms
231 ms
19  POS9-1-0.bbr1.ber.completel.de (195.167.211.13)  177 ms  177 ms  177
ms
20  ge4-0-0-10.bbr2.ber.completel.de (195.167.209.130)  204 ms  177 ms
177 ms
21  POS9-1-0.bbr2.nue.completel.de (195.167.211.10)  186 ms  185 ms  185
ms
22  fe4-0-0-10.bbr1.nue.completel.de (195.167.210.129)  184 ms  184 ms
184 ms
23  backports.services.n-ix.net (194.8.57.10)  186 ms  184 ms  183 ms

	I'm able to reach it through my verio.net -> komtel.net -> versatel.de ->
completel.de route here at work. I haven't tried from home which goes
through another provider route.

	Regards,
	Jeremy

On Mon, Dec 08, 2003 at 01:50:38PM -0700, Nate Duehr wrote:
> Mike Dresser wrote:
> >Anyone know what is going on with www.backports.org?
> >
> >I can get at it from a few rare hosts, but from most of the hosts I've
> >tried it simply times out.  Traceroute reveals it dies in the
> >eurorings.net, and from another host i-p-x.de
> >
> >I had to use google's cache to get a peek at the mirror listing in order
> >to find replacement deb lines that worked.
> >
> >Mike
> 
> $ traceroute 194.8.57.10
> traceroute to 194.8.57.10 (194.8.57.10), 30 hops max, 38 byte packets
>  1  199.239.11.254 (199.239.11.254)  2.297 ms  1.067 ms  1.061 ms
>  2  172.16.50.122 (172.16.50.122)  19.875 ms  8.485 ms  27.871 ms
>  3  216.183.120.154 (216.183.120.154)  22.035 ms  34.127 ms  5.123 ms
>  4  ibr0003-vlan-1.den03.inflow.net (216.183.96.3)  5.382 ms  7.090 ms 
>  5.634 ms
>  5  dvr-edge-03.inet.qwest.net (63.237.112.161)  35.734 ms *  230.727 ms
>  6  dia-core-02.inet.qwest.net (205.171.10.77)  209.510 ms  245.280 ms *
>  7  dia-core-01.inet.qwest.net (205.171.142.1)  8.621 ms  7.160 ms 
> 94.783 ms
>  8  kcm-core-01.inet.qwest.net (205.171.8.138)  55.412 ms  18.505 ms 
> 17.491 ms
>  9  kcm-core-03.inet.qwest.net (205.171.29.122)  17.557 ms  17.805 ms 
> 17.143 ms
> 10  ewr-core-01.inet.qwest.net (205.171.8.186)  49.495 ms  56.657 ms 
> 49.528 ms
> 11  ewr-brdr-02.inet.qwest.net (205.171.17.126)  61.147 ms  49.638 ms 
> 78.943 ms
> 12  ledn-rou-1001.NL.eurorings.net (134.222.254.1)  138.362 ms  138.326 
> ms  139.598 ms
> 13  ffm-s1-rou-1001.DE.eurorings.net (134.222.230.14)  144.339 ms 
> 144.669 ms  144.529 ms
> 14  nbg-s1-rou-1071.DE.eurorings.net (134.222.227.30)  151.816 ms 
> 151.368 ms  179.337 ms
> 15  * * *
> 16  * * *
> 
> Dies from my work connection.  Very slow (350+ms) from Denver, Colorado 
> InterNAP/pnap connection on one of my home boxes.  The above traceroute 
> shows the work connection.
> 
> I didn't mess with looking at any of the routing looking glass servers 
> anywhwere to see who's announcing what/where...
> 
> Nate, nate@natetech.com
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact 
> listmaster@lists.debian.org
> 

Attachment: signature.asc
Description: Digital signature


Reply to: