[outages] Outages Digest, Vol 89, Issue 37

Samer Ziadeh samerziadeh at gmail.com
Sat Oct 31 12:02:33 EDT 2015


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 at outages.org> wrote:

> Send Outages mailing list submissions to
>         outages at 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 at outages.org
>
> You can reach the person managing the list at
>         outages-owner at 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 at gmail.com>
> To: "outages at outages.org" <outages at outages.org>
> Subject: [outages] Routing issues?
> Message-ID:
>         <CACF-m_+np=
> nS2DWxu_3JcEifKKs8_PyiYEPim4N+N5PLUUxTBw at 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
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://puck.nether.net/pipermail/outages/attachments/20151031/77bc60d2/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Sat, 31 Oct 2015 10:26:40 -0400
> From: Aubrey Wells <awells at digiumcloud.com>
> To: Samer Ziadeh <samerziadeh at gmail.com>
> Cc: "outages at outages.org" <outages at outages.org>
> Subject: Re: [outages] Routing issues?
> Message-ID:
>         <
> CAJ+z88oSvZZHt9m3J_XapK5Rz6GWb_sSpQ1ETQEVTkJ9Wy7xuA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> The !H is traceroute telling you that 38.104.251.246 reported that the
> destination IP is unreachable. This means that 38.104.251.246 is the router
> one hop up from your destination IP but its not able to resolve a MAC
> address for the IP, IE: your machine is not responding to ARP requests.
>
> My traceroute takes a completely different path through AT&T and then GTT.
> Your destination IP is advertised out of ASN 32489 which has GTT as an
> upstream so I'd say the issue is with either GTT, your hosting provider, or
> your server itself. Since I have GTT/nLayer as an upstream and am not
> having any problems with them at the moment, and I can sucessfully
> traceroute to an IP adjacent to yours (184.75.220.217) I'd wager the most
> likely source of the trouble is your server itself. You might want to
> contact your hosting provider's support desk and have them check on it.
>
>
> ---------------------
> Aubrey Wells
> Manager, Network Operations
> Digium Cloud Services
> Main: 888.305.3850
> Support: 877.344.4861 or http://www.digium.com/en/support
> <
> http://www.digium.com/en/support?elq=65516445a5964d3597e25eaf566bc2cf&elqCampaignId=
> >
>
> On Sat, Oct 31, 2015 at 10:13 AM, Samer Ziadeh via Outages <
> outages at outages.org> wrote:
>
> > 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
> >
> > _______________________________________________
> > Outages mailing list
> > Outages at outages.org
> > https://puck.nether.net/mailman/listinfo/outages
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://puck.nether.net/pipermail/outages/attachments/20151031/350922cc/attachment-0001.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
> ------------------------------
>
> End of Outages Digest, Vol 89, Issue 37
> ***************************************
>



-- 
- Samer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20151031/88469bfe/attachment.htm>


More information about the Outages mailing list