[arch-dev-public] (Still) cannot connect to archlinux.org
As of yesterday, I (among others) am unable to connect to archlinux.org. A trace tells me that the problem is somewhere at cogent. This means I cannot do anything right now: [x86_64][09:18:30][root@artin ~]# tcptraceroute archlinux.org Selected device rwth, address 137.226.101.95, port 58868 for outgoing packets Tracing the path to archlinux.org (66.211.213.17) on TCP port 80 (http), 30 hops max 1 c3750-ww10-2.noc.RWTH-Aachen.DE (134.130.5.254) 41.334 ms 40.643 ms 41.082 ms 2 c6k-ww10.noc.RWTH-Aachen.DE (137.226.138.1) 41.656 ms 41.680 ms 42.513 ms 3 c6k-rwth.noc.RWTH-Aachen.DE (137.226.139.49) 41.965 ms 43.641 ms 51.844 ms 4 pfi-stone-1.noc.RWTH-Aachen.DE (134.130.9.243) 41.342 ms 42.467 ms 41.068 ms 5 n6k-xwin.noc.RWTH-Aachen.DE (134.130.9.225) 41.551 ms 46.496 ms 50.785 ms 6 xr-aac1-te1-3.x-win.dfn.de (188.1.43.109) 41.491 ms 48.075 ms 46.804 ms 7 zr-fra1-te0-0-0-3.x-win.dfn.de (80.81.192.222) 59.875 ms 45.793 ms 45.654 ms 8 decix.mpd01.fra03.atlas.cogentco.com (80.81.192.63) 108.447 ms 199.492 ms 222.729 ms 9 t7-2.mpd01.par02.atlas.cogentco.com (130.117.0.102) 128.717 ms 198.280 ms 215.676 ms 10 t7-1.mpd02.par01.atlas.cogentco.com (130.117.1.234) 58.085 ms 58.368 ms 60.158 ms 11 g0-0-0.core01.par01.atlas.cogentco.com (130.117.2.49) 69.687 ms 69.867 ms 69.860 ms 12 p14-0.core02.dca01.atlas.cogentco.com (66.28.4.206) 152.241 ms 159.736 ms 149.169 ms 13 t3-1.mpd01.dca01.atlas.cogentco.com (154.54.5.50) 150.661 ms 181.276 ms 157.748 ms 14 t8-3.mpd01.dca02.atlas.cogentco.com (154.54.6.198) 152.689 ms 159.701 ms 152.143 ms 15 t1-4.mpd01.iad01.atlas.cogentco.com (154.54.7.162) 156.777 ms 156.578 ms 161.400 ms 16 g2-0-0-3491.core01.iad01.atlas.cogentco.com (154.54.5.33) 137.817 ms 152.898 ms 150.242 ms 17 * * *
You could try TOR or something like that, until it gets figured out. I believe one of the team has filed a ticket with the ISP to find out if there is anything that can be done (the ISP would likely contact cogent). On 11/19/07, Thomas Bächler <thomas@archlinux.org> wrote:
As of yesterday, I (among others) am unable to connect to archlinux.org. A trace tells me that the problem is somewhere at cogent. This means I cannot do anything right now:
[x86_64][09:18:30][root@artin ~]# tcptraceroute archlinux.org Selected device rwth, address 137.226.101.95, port 58868 for outgoing packets Tracing the path to archlinux.org (66.211.213.17) on TCP port 80 (http), 30 hops max 1 c3750-ww10-2.noc.RWTH-Aachen.DE (134.130.5.254) 41.334 ms 40.643 ms 41.082 ms 2 c6k-ww10.noc.RWTH-Aachen.DE (137.226.138.1) 41.656 ms 41.680 ms 42.513 ms 3 c6k-rwth.noc.RWTH-Aachen.DE (137.226.139.49) 41.965 ms 43.641 ms 51.844 ms 4 pfi-stone-1.noc.RWTH-Aachen.DE (134.130.9.243) 41.342 ms 42.467 ms 41.068 ms 5 n6k-xwin.noc.RWTH-Aachen.DE (134.130.9.225) 41.551 ms 46.496 ms 50.785 ms 6 xr-aac1-te1-3.x-win.dfn.de (188.1.43.109) 41.491 ms 48.075 ms 46.804 ms 7 zr-fra1-te0-0-0-3.x-win.dfn.de (80.81.192.222) 59.875 ms 45.793 ms 45.654 ms 8 decix.mpd01.fra03.atlas.cogentco.com (80.81.192.63) 108.447 ms 199.492 ms 222.729 ms 9 t7-2.mpd01.par02.atlas.cogentco.com (130.117.0.102) 128.717 ms 198.280 ms 215.676 ms 10 t7-1.mpd02.par01.atlas.cogentco.com (130.117.1.234) 58.085 ms 58.368 ms 60.158 ms 11 g0-0-0.core01.par01.atlas.cogentco.com (130.117.2.49) 69.687 ms 69.867 ms 69.860 ms 12 p14-0.core02.dca01.atlas.cogentco.com (66.28.4.206) 152.241 ms 159.736 ms 149.169 ms 13 t3-1.mpd01.dca01.atlas.cogentco.com (154.54.5.50) 150.661 ms 181.276 ms 157.748 ms 14 t8-3.mpd01.dca02.atlas.cogentco.com (154.54.6.198) 152.689 ms 159.701 ms 152.143 ms 15 t1-4.mpd01.iad01.atlas.cogentco.com (154.54.7.162) 156.777 ms 156.578 ms 161.400 ms 16 g2-0-0-3491.core01.iad01.atlas.cogentco.com (154.54.5.33) 137.817 ms 152.898 ms 150.242 ms 17 * * *
_______________________________________________ arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
On Nov 19, 2007 2:35 AM, Thomas Bächler <thomas@archlinux.org> wrote:
As of yesterday, I (among others) am unable to connect to archlinux.org. A trace tells me that the problem is somewhere at cogent. This means I cannot do anything right now:
Thanks for the head's up. Dale has logged a ticket with cogent. Jan said somewhere else that cogent seems to only fix one route per day. No worries, consider it a nice little vacation 8)
On Tue, 2007-11-20 at 14:50 -0600, Aaron Griffin wrote:
On Nov 19, 2007 2:35 AM, Thomas Bächler <thomas@archlinux.org> wrote:
As of yesterday, I (among others) am unable to connect to archlinux.org. A trace tells me that the problem is somewhere at cogent. This means I cannot do anything right now:
Thanks for the head's up. Dale has logged a ticket with cogent. Jan said somewhere else that cogent seems to only fix one route per day.
No worries, consider it a nice little vacation 8)
I'm guessing that since his email is dated about 36 hours ago and was just delivered that his access just came back up :) Please provide me with inbound traceroutes of any additional netblocks with issues and I'll pass them to my support contact at Cogent. Dale
On Nov 20, 2007 2:53 PM, Dale Blount <dale@archlinux.org> wrote:
I'm guessing that since his email is dated about 36 hours ago and was just delivered that his access just came back up :)
Haha, I feel dumb now. I didn't parse the date 8)
Aaron Griffin schrieb:
On Nov 20, 2007 2:53 PM, Dale Blount <dale@archlinux.org> wrote:
I'm guessing that since his email is dated about 36 hours ago and was just delivered that his access just came back up :)
Haha, I feel dumb now. I didn't parse the date 8)
It is indeed funny, that this mail actually told me that I can now connect again. The smtp relay server I use for @archlinux.org is in the same network as I am, thus had the same problem that I had.
participants (4)
-
Aaron Griffin
-
Dale Blount
-
eliott
-
Thomas Bächler