October 2015 - Outages - Outages Lists

Re: [outages] Outages Digest, Vol 89, Issue 37
by Samer Ziadeh 31 Oct '15

31 Oct '15

It was indeed the destination. I managed to get to the server and turned out it had crashed :) On Sat, Oct 31, 2015 at 12:00 PM, <outages-request(a)outages.org> wrote: > Send Outages mailing list submissions to > outages(a)outages.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://puck.nether.net/mailman/listinfo/outages > or, via email, send a message with subject or body 'help' to > outages-request(a)outages.org > > You can reach the person managing the list at > outages-owner(a)outages.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Outages digest..." > > > Today's Topics: > > 1. Routing issues? (Samer Ziadeh) > 2. Re: Routing issues? (Aubrey Wells) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 31 Oct 2015 10:13:57 -0400 > From: Samer Ziadeh <samerziadeh(a)gmail.com> > To: "outages(a)outages.org" <outages(a)outages.org> > Subject: [outages] Routing issues? > Message-ID: > <CACF-m_+np= > nS2DWxu_3JcEifKKs8_PyiYEPim4N+N5PLUUxTBw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > I'm getting routing issues to my server, when I traceroute, I eventually > get "!H" to one of the nodes, but when I traceroute the node itself it's > fine. I can't even ping or SSH into it, I keep getting network unreachable. > I'm also confused about # 10 and 11, as they are the same. > > Is that a Cogent IP? Anyone knows what's going on? > > traceroute to 184.75.220.218 (184.75.220.218), 64 hops max, 52 byte > packets > > 1 10.0.1.1 (10.0.1.1) 3.468 ms 1.898 ms 1.035 ms > > 2 7.11.164.237 (7.11.164.237) 15.989 ms 13.477 ms 14.213 ms > > 3 209.148.243.9 (209.148.243.9) 16.695 ms 15.316 ms 16.864 ms > > 4 69.63.248.233 (69.63.248.233) 14.564 ms 12.200 ms 24.710 ms > > 5 24.156.144.178 (24.156.144.178) 28.042 ms 29.279 ms 24.806 ms > > 6 * * * > > 7 be2217.ccr42.ord01.atlas.cogentco.com (154.54.24.205) 171.283 ms > 37.942 ms 50.327 ms > > 8 be2718.ccr22.cle04.atlas.cogentco.com (154.54.7.130) 120.499 ms > 39.208 ms > > be2185.ccr22.cle04.atlas.cogentco.com (154.54.43.178) 138.381 ms > > 9 be2597.ccr22.yyz02.atlas.cogentco.com (154.54.31.90) 176.050 ms > 132.849 ms 177.392 ms > > 10 38.104.251.246 (38.104.251.246) 177.557 ms 42.334 ms 135.418 ms > > 11 38.104.251.246 (38.104.251.246) 3048.770 ms !H 3046.702 ms !H > 3055.225 ms !H > > > > -- > - Samer >

1 0

Routing issues?
by Samer Ziadeh 31 Oct '15

31 Oct '15

I'm getting routing issues to my server, when I traceroute, I eventually get "!H" to one of the nodes, but when I traceroute the node itself it's fine. I can't even ping or SSH into it, I keep getting network unreachable. I'm also confused about # 10 and 11, as they are the same. Is that a Cogent IP? Anyone knows what's going on? traceroute to 184.75.220.218 (184.75.220.218), 64 hops max, 52 byte packets 1 10.0.1.1 (10.0.1.1) 3.468 ms 1.898 ms 1.035 ms 2 7.11.164.237 (7.11.164.237) 15.989 ms 13.477 ms 14.213 ms 3 209.148.243.9 (209.148.243.9) 16.695 ms 15.316 ms 16.864 ms 4 69.63.248.233 (69.63.248.233) 14.564 ms 12.200 ms 24.710 ms 5 24.156.144.178 (24.156.144.178) 28.042 ms 29.279 ms 24.806 ms 6 * * * 7 be2217.ccr42.ord01.atlas.cogentco.com (154.54.24.205) 171.283 ms 37.942 ms 50.327 ms 8 be2718.ccr22.cle04.atlas.cogentco.com (154.54.7.130) 120.499 ms 39.208 ms be2185.ccr22.cle04.atlas.cogentco.com (154.54.43.178) 138.381 ms 9 be2597.ccr22.yyz02.atlas.cogentco.com (154.54.31.90) 176.050 ms 132.849 ms 177.392 ms 10 38.104.251.246 (38.104.251.246) 177.557 ms 42.334 ms 135.418 ms 11 38.104.251.246 (38.104.251.246) 3048.770 ms !H 3046.702 ms !H 3055.225 ms !H -- - Samer

2 1

unable to reach tinyurl.com via Comcast Residental
by Matthew McGehrin 29 Oct '15

29 Oct '15

Hello. Since 3pm yesterday, I have been unable to reach tinyurl.com from my Comcast at home. I posted a similar message on DSLreports.com and other Comcast users were having the same issue as well. However, this domain seems to be accessible from other sources, just not on the Comcast Network. I have e-mailed support(a)tinyurl.com, still awaiting a response from them however. From my colocation, it seems to traverse over CogentCo without any issues oddly, just not at home. Comcast Home: Source: 50.151.0.126, Dest: 195.66.135.246 root@nas:~# traceroute tinyurl.com traceroute to tinyurl.com (195.66.135.246), 32 hops max, 60 byte packets 1 96.120.29.97 (96.120.29.97) 7.729 ms 7.632 ms 2 * * 3 * * 4 * * 5 * * 6 * * 7 * * Colocation: 3 te0-0-1-1.rcr12.b002281-5.ord03.atlas.cogentco.com (38.104.103.237) 2.609 ms 2.043 ms 4 be2461.ccr41.ord03.atlas.cogentco.com (154.54.29.237) 2.107 ms be2617.ccr22.ord03.atlas.cogentco.com (154.54.40.93) 2.586 ms 5 be2248.ccr42.ord01.atlas.cogentco.com (154.54.5.157) 2.426 ms be2216.ccr41.ord01.atlas.cogentco.com (154.54.24.201) 2.198 ms 6 be2185.ccr22.cle04.atlas.cogentco.com (154.54.43.178) 17.664 ms be2351.ccr21.cle04.atlas.cogentco.com (154.54.44.86) 17.803 ms 7 be2596.ccr21.yyz02.atlas.cogentco.com (154.54.31.54) 17.829 ms 17.586 ms 8 be2093.ccr22.ymq02.atlas.cogentco.com (154.54.44.106) 24.963 ms be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 25.192 ms 9 be2384.ccr21.lpl01.atlas.cogentco.com (154.54.44.138) 97.752 ms 98.013 ms 10 be2182.ccr41.ams03.atlas.cogentco.com (154.54.77.245) 101.671 ms 102.008 ms 11 be2520.rcr21.b015960-1.ams03.atlas.cogentco.com (130.117.3.102) 102.794 ms be2311.ccr21.ams04.atlas.cogentco.com (154.54.74.90) 104.029 ms 12 149.11.64.34 (149.11.64.34) 101.551 ms 149.11.38.106 (149.11.38.106) 101.126 ms 13 ae0-30.crt02-gsw.redhosting.nl (178.238.96.34) 101.198 ms deepmedia.redhosting.nl (89.184.160.166) 101.355 ms 14 ip-space.unicycle.net (195.66.135.246) 100.869 ms 101.052 ms Thanks

1 1

Level 3 intermittent packet loss in Dallas
by Dan White 28 Oct '15

28 Oct '15

We've opened a ticket with Level 3 (9896580) regarding intermittent packet loss affecting certain source/destination IP pairs, with certain pairs receiving 100% packet loss, and others passing traffic normally. For example, we were unable to ping 4.2.2.3, from a particular IP address, but could ping 4.2.2.2, and 4.2.2.4. We've disabled our Level 3 BGP session while we trouble shoot. This problem was causing some very strange trouble reports from our customers, such as certain sites not working, or working intermittently. -- Dan White

2 1

NANOG
by John Souvestre 26 Oct '15

26 Oct '15

I haven’t seen anything but a steady stream of spam on NANOG for the last 1.5 days or so. Is this what you are seeing? They can’t filter it? John John Souvestre - New Orleans LA

9 13

Re: [outages] NANOG
by John Sage 26 Oct '15

26 Oct '15

On 10/26/2015 06:45 AM, J. Oquendo wrote: > On Mon, 26 Oct 2015, John Sage via Outages wrote: > >> After the appropriate wgets and less'es those all seemed to point back to >> >> avazunic [dot] com >> >> which is registered in -- wait for it -- CN... >> > > So glad investigators are on the job. Luckily for us no > one would ever compromise a machine in another country > to pull off wetwork. CN it is! Or is it? yeah, think you're right. Not quite sure what I [wasn't] looking at. Early here. Caffeine hasn't quite kicked in yet... - John --

1 0

Outages.org spam!
by Jim Witherell 24 Oct '15

24 Oct '15

Think the guys managing the listserv are on top of it? Sent from Yahoo Mail on Android

7 6

Fw: new message
by George Herbert 24 Oct '15

24 Oct '15

Hey! New message, please read <http://americantrailermart.com/natural.php?n0re> George Herbert

1 0

Fw: new message
by outages-bounces＠outages.org 24 Oct '15

24 Oct '15

Hey! New message, please read <http://hanumanmandirchanakyapuri.com/common.php?778to> outages-bounces(a)outages.org

1 0

Fw: new message
by outages-bounces＠outages.org 24 Oct '15

24 Oct '15

Hey! New message, please read <http://lapeste.org/letters.php?z> outages-bounces(a)outages.org

1 0