<div dir="ltr">It was indeed the destination. I managed to get to the server and turned out it had crashed :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 31, 2015 at 12:00 PM, <span dir="ltr"><<a href="mailto:outages-request@outages.org" target="_blank">outages-request@outages.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Outages mailing list submissions to<br>
<a href="mailto:outages@outages.org">outages@outages.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:outages-request@outages.org">outages-request@outages.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:outages-owner@outages.org">outages-owner@outages.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Outages digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Routing issues? (Samer Ziadeh)<br>
2. Re: Routing issues? (Aubrey Wells)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 31 Oct 2015 10:13:57 -0400<br>
From: Samer Ziadeh <<a href="mailto:samerziadeh@gmail.com">samerziadeh@gmail.com</a>><br>
To: "<a href="mailto:outages@outages.org">outages@outages.org</a>" <<a href="mailto:outages@outages.org">outages@outages.org</a>><br>
Subject: [outages] Routing issues?<br>
Message-ID:<br>
<CACF-m_+np=<a href="mailto:nS2DWxu_3JcEifKKs8_PyiYEPim4N%2BN5PLUUxTBw@mail.gmail.com">nS2DWxu_3JcEifKKs8_PyiYEPim4N+N5PLUUxTBw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I'm getting routing issues to my server, when I traceroute, I eventually<br>
get "!H" to one of the nodes, but when I traceroute the node itself it's<br>
fine. I can't even ping or SSH into it, I keep getting network unreachable.<br>
I'm also confused about # 10 and 11, as they are the same.<br>
<br>
Is that a Cogent IP? Anyone knows what's going on?<br>
<br>
traceroute to <a href="tel:184.75.220.218" value="+18475220218">184.75.220.218</a> <a href="tel:%28184.75.220.218" value="+18475220218">(184.75.220.218</a>), 64 hops max, 52 byte packets<br>
<br>
1 10.0.1.1 (10.0.1.1) 3.468 ms 1.898 ms 1.035 ms<br>
<br>
2 7.11.164.237 (7.11.164.237) 15.989 ms 13.477 ms 14.213 ms<br>
<br>
3 209.148.243.9 (209.148.243.9) 16.695 ms 15.316 ms 16.864 ms<br>
<br>
4 69.63.248.233 (69.63.248.233) 14.564 ms 12.200 ms 24.710 ms<br>
<br>
5 24.156.144.178 (24.156.144.178) 28.042 ms 29.279 ms 24.806 ms<br>
<br>
6 * * *<br>
<br>
7 <a href="http://be2217.ccr42.ord01.atlas.cogentco.com" rel="noreferrer" target="_blank">be2217.ccr42.ord01.atlas.cogentco.com</a> (154.54.24.205) 171.283 ms<br>
37.942 ms 50.327 ms<br>
<br>
8 <a href="http://be2718.ccr22.cle04.atlas.cogentco.com" rel="noreferrer" target="_blank">be2718.ccr22.cle04.atlas.cogentco.com</a> (154.54.7.130) 120.499 ms<br>
39.208 ms<br>
<br>
<a href="http://be2185.ccr22.cle04.atlas.cogentco.com" rel="noreferrer" target="_blank">be2185.ccr22.cle04.atlas.cogentco.com</a> (154.54.43.178) 138.381 ms<br>
<br>
9 <a href="http://be2597.ccr22.yyz02.atlas.cogentco.com" rel="noreferrer" target="_blank">be2597.ccr22.yyz02.atlas.cogentco.com</a> (154.54.31.90) 176.050 ms<br>
132.849 ms 177.392 ms<br>
<br>
10 38.104.251.246 (38.104.251.246) 177.557 ms 42.334 ms 135.418 ms<br>
<br>
11 38.104.251.246 (38.104.251.246) 3048.770 ms !H 3046.702 ms !H<br>
3055.225 ms !H<br>
<br>
<br>
<br>
--<br>
- Samer<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/outages/attachments/20151031/77bc60d2/attachment-0001.html" rel="noreferrer" target="_blank">https://puck.nether.net/pipermail/outages/attachments/20151031/77bc60d2/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 31 Oct 2015 10:26:40 -0400<br>
From: Aubrey Wells <<a href="mailto:awells@digiumcloud.com">awells@digiumcloud.com</a>><br>
To: Samer Ziadeh <<a href="mailto:samerziadeh@gmail.com">samerziadeh@gmail.com</a>><br>
Cc: "<a href="mailto:outages@outages.org">outages@outages.org</a>" <<a href="mailto:outages@outages.org">outages@outages.org</a>><br>
Subject: Re: [outages] Routing issues?<br>
Message-ID:<br>
<<a href="mailto:CAJ%2Bz88oSvZZHt9m3J_XapK5Rz6GWb_sSpQ1ETQEVTkJ9Wy7xuA@mail.gmail.com">CAJ+z88oSvZZHt9m3J_XapK5Rz6GWb_sSpQ1ETQEVTkJ9Wy7xuA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
The !H is traceroute telling you that 38.104.251.246 reported that the<br>
destination IP is unreachable. This means that 38.104.251.246 is the router<br>
one hop up from your destination IP but its not able to resolve a MAC<br>
address for the IP, IE: your machine is not responding to ARP requests.<br>
<br>
My traceroute takes a completely different path through AT&T and then GTT.<br>
Your destination IP is advertised out of ASN 32489 which has GTT as an<br>
upstream so I'd say the issue is with either GTT, your hosting provider, or<br>
your server itself. Since I have GTT/nLayer as an upstream and am not<br>
having any problems with them at the moment, and I can sucessfully<br>
traceroute to an IP adjacent to yours (184.75.220.217) I'd wager the most<br>
likely source of the trouble is your server itself. You might want to<br>
contact your hosting provider's support desk and have them check on it.<br>
<br>
<br>
---------------------<br>
Aubrey Wells<br>
Manager, Network Operations<br>
Digium Cloud Services<br>
Main: 888.305.3850<br>
Support: 877.344.4861 or <a href="http://www.digium.com/en/support" rel="noreferrer" target="_blank">http://www.digium.com/en/support</a><br>
<<a href="http://www.digium.com/en/support?elq=65516445a5964d3597e25eaf566bc2cf&elqCampaignId=" rel="noreferrer" target="_blank">http://www.digium.com/en/support?elq=65516445a5964d3597e25eaf566bc2cf&elqCampaignId=</a>><br>
<br>
On Sat, Oct 31, 2015 at 10:13 AM, Samer Ziadeh via Outages <<br>
<a href="mailto:outages@outages.org">outages@outages.org</a>> wrote:<br>
<br>
> I'm getting routing issues to my server, when I traceroute, I eventually<br>
> get "!H" to one of the nodes, but when I traceroute the node itself it's<br>
> fine. I can't even ping or SSH into it, I keep getting network unreachable.<br>
> I'm also confused about # 10 and 11, as they are the same.<br>
><br>
> Is that a Cogent IP? Anyone knows what's going on?<br>
><br>
> traceroute to <a href="tel:184.75.220.218" value="+18475220218">184.75.220.218</a> <a href="tel:%28184.75.220.218" value="+18475220218">(184.75.220.218</a>), 64 hops max, 52 byte packets<br>
><br>
> 1 10.0.1.1 (10.0.1.1) 3.468 ms 1.898 ms 1.035 ms<br>
><br>
> 2 7.11.164.237 (7.11.164.237) 15.989 ms 13.477 ms 14.213 ms<br>
><br>
> 3 209.148.243.9 (209.148.243.9) 16.695 ms 15.316 ms 16.864 ms<br>
><br>
> 4 69.63.248.233 (69.63.248.233) 14.564 ms 12.200 ms 24.710 ms<br>
><br>
> 5 24.156.144.178 (24.156.144.178) 28.042 ms 29.279 ms 24.806 ms<br>
><br>
> 6 * * *<br>
><br>
> 7 <a href="http://be2217.ccr42.ord01.atlas.cogentco.com" rel="noreferrer" target="_blank">be2217.ccr42.ord01.atlas.cogentco.com</a> (154.54.24.205) 171.283 ms<br>
> 37.942 ms 50.327 ms<br>
><br>
> 8 <a href="http://be2718.ccr22.cle04.atlas.cogentco.com" rel="noreferrer" target="_blank">be2718.ccr22.cle04.atlas.cogentco.com</a> (154.54.7.130) 120.499 ms<br>
> 39.208 ms<br>
><br>
> <a href="http://be2185.ccr22.cle04.atlas.cogentco.com" rel="noreferrer" target="_blank">be2185.ccr22.cle04.atlas.cogentco.com</a> (154.54.43.178) 138.381 ms<br>
><br>
> 9 <a href="http://be2597.ccr22.yyz02.atlas.cogentco.com" rel="noreferrer" target="_blank">be2597.ccr22.yyz02.atlas.cogentco.com</a> (154.54.31.90) 176.050 ms<br>
> 132.849 ms 177.392 ms<br>
><br>
> 10 38.104.251.246 (38.104.251.246) 177.557 ms 42.334 ms 135.418 ms<br>
><br>
> 11 38.104.251.246 (38.104.251.246) 3048.770 ms !H 3046.702 ms !H<br>
> 3055.225 ms !H<br>
><br>
><br>
><br>
> --<br>
> - Samer<br>
><br>
> _______________________________________________<br>
> Outages mailing list<br>
> <a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/outages/attachments/20151031/350922cc/attachment-0001.html" rel="noreferrer" target="_blank">https://puck.nether.net/pipermail/outages/attachments/20151031/350922cc/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Outages Digest, Vol 89, Issue 37<br>
***************************************<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">- Samer</div>
</div>