NTT to Level3 routing issue in NYC?
http://www.us.ntt.net/support/looking-glass/ *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2 Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) But it seems to work fine from Ashburn *Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2 Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
No issues with our NYC location. We are in the Financial District... On Wed, Nov 23, 2016 at 12:17 PM, Ca By via Outages <outages@outages.org> wrote:
http://www.us.ntt.net/support/looking-glass/
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
But it seems to work fine from Ashburn
*Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Michael Snyder Technical Lead | Infrastructure XO Group Inc. (NYSE: XOXO) P (512) 498-3365 <512-498-3365> / C (512) 574-5747 <512-574-5747> [image: https://www.facebook.com/XOGroupInc] <https://www.facebook.com/XOGroupInc>[image: https://twitter.com/xogroupinc] <https://twitter.com/xogroupinc>[image: https://instagram.com/xogroupinc/] <https://instagram.com/xogroupinc/>
The A resolver responds when testing from NTT New York *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.1 Sending 5, 100-byte ICMP Echos to 4.2.2.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms B resolver is still down *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2 Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) On Wed, Nov 23, 2016 at 1:20 PM, Michael Snyder via Outages < outages@outages.org> wrote:
No issues with our NYC location. We are in the Financial District...
On Wed, Nov 23, 2016 at 12:17 PM, Ca By via Outages <outages@outages.org> wrote:
http://www.us.ntt.net/support/looking-glass/
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
But it seems to work fine from Ashburn
*Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
--
Michael Snyder
Technical Lead | Infrastructure
XO Group Inc. (NYSE: XOXO)
P (512) 498-3365 <512-498-3365> / C (512) 574-5747 <512-574-5747>
[image: https://www.facebook.com/XOGroupInc] <https://www.facebook.com/XOGroupInc>[image: https://twitter.com/xogroupinc] <https://twitter.com/xogroupinc>[image: https://instagram.com/xogroupinc/] <https://instagram.com/xogroupinc/>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Dylan Page DigitalOcean Platform Support Specialist @digitalocean
Must be a hashing issue if 1 works but 2 does not on peering between Level3 and NTT.... Other NYC looking glass show both 1 and 2 up. http://imgur.com/a/Z6JiM On Wed, Nov 23, 2016 at 10:31 AM, Dylan Page <dpage@digitalocean.com> wrote:
The A resolver responds when testing from NTT New York
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.1
Sending 5, 100-byte ICMP Echos to 4.2.2.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
B resolver is still down
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
On Wed, Nov 23, 2016 at 1:20 PM, Michael Snyder via Outages < outages@outages.org> wrote:
No issues with our NYC location. We are in the Financial District...
On Wed, Nov 23, 2016 at 12:17 PM, Ca By via Outages <outages@outages.org> wrote:
http://www.us.ntt.net/support/looking-glass/
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
But it seems to work fine from Ashburn
*Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
--
Michael Snyder
Technical Lead | Infrastructure
XO Group Inc. (NYSE: XOXO)
P (512) 498-3365 <512-498-3365> / C (512) 574-5747 <512-574-5747>
[image: https://www.facebook.com/XOGroupInc] <https://www.facebook.com/XOGroupInc>[image: https://twitter.com/xogroupinc] <https://twitter.com/xogroupinc>[image: https://instagram.com/xogroupinc/] <https://instagram.com/xogroupinc/>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Dylan Page DigitalOcean Platform Support Specialist @digitalocean
Must have been a temp. issue. Working from me from 60 Hudson and from their LG as well. *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2 Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) On Wed, Nov 23, 2016 at 1:17 PM, Ca By via Outages <outages@outages.org> wrote:
http://www.us.ntt.net/support/looking-glass/
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
But it seems to work fine from Ashburn
*Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails: *Query Results:* *Router: *Atlanta, GA - US *Command:* ping 45.31.x.x Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) -- *Doug Roberts* Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) <http://cytranet.com> CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. On Wed, Nov 23, 2016 at 12:17 PM, Ca By via Outages <outages@outages.org> wrote:
http://www.us.ntt.net/support/looking-glass/
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
But it seems to work fine from Ashburn
*Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
From NY: root@homer.my.net> ping source 165.254.XX.XX 45.31.217.222 PING 45.31.217.222 (45.31.217.222): 56 data bytes 64 bytes from 45.31.217.222: icmp_seq=0 ttl=53 time=43.286 ms 64 bytes from 45.31.217.222: icmp_seq=0 ttl=53 time=44.087 ms (DUP!) 64 bytes from 45.31.217.222: icmp_seq=1 ttl=53 time=43.114 ms 64 bytes from 45.31.217.222: icmp_seq=1 ttl=53 time=43.446 ms (DUP!) 64 bytes from 45.31.217.222: icmp_seq=2 ttl=53 time=43.118 ms 64 bytes from 45.31.217.222: icmp_seq=2 ttl=53 time=43.421 ms (DUP!) 64 bytes from 45.31.217.222: icmp_seq=3 ttl=53 time=43.100 ms 64 bytes from 45.31.217.222: icmp_seq=3 ttl=53 time=43.418 ms (DUP!) 64 bytes from 45.31.217.222: icmp_seq=4 ttl=53 time=43.103 ms 64 bytes from 45.31.217.222: icmp_seq=4 ttl=53 time=43.397 ms (DUP!)
On Wed, Nov 23, 2016 at 1:33 PM, Doug Roberts via Outages < outages@outages.org> wrote:
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails:
*Query Results:* *Router: *Atlanta, GA - US *Command:* ping 45.31.x.x
Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
-- *Doug Roberts* Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) <http://cytranet.com> CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
On Wed, Nov 23, 2016 at 12:17 PM, Ca By via Outages <outages@outages.org> wrote:
http://www.us.ntt.net/support/looking-glass/
*Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
But it seems to work fine from Ashburn
*Query Results:* *Router: *Ashburn, VA - US *Command:* ping 4.2.2.2
Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On Nov 23, 2016, at 1:33 PM, Doug Roberts via Outages <outages@outages.org> wrote:
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails:
Query Results: Router: Atlanta, GA - US Command: ping 45.31.x.x
Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Do you have details? I’m showing atlas working fine measuring things, but others have asked me as well about issues, so continuing to look. https://atlas.ripe.net/measurements/6939072/#!probes More details of brokenness would be helpful either to me or to the NTT NOC. - Jared
Here's what I see from here: https://puu.sh/ss76o/27b9de01e6.png -- *Doug Roberts* Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) <http://cytranet.com> CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. On Wed, Nov 23, 2016 at 1:03 PM, Jared Mauch <jared@puck.nether.net> wrote:
On Nov 23, 2016, at 1:33 PM, Doug Roberts via Outages < outages@outages.org> wrote:
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails:
Query Results: Router: Atlanta, GA - US Command: ping 45.31.x.x
Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Do you have details?
I’m showing atlas working fine measuring things, but others have asked me as well about issues, so continuing to look.
https://atlas.ripe.net/measurements/6939072/#!probes
More details of brokenness would be helpful either to me or to the NTT NOC.
- Jared
I see that going to AT&T not Level3, let me keep looking, eg: r02.atlnga05.us.bb-re1> traceroute 107.207.236.1 traceroute to 107.207.236.1 (107.207.236.1), 30 hops max, 40 byte packets 1 ge-100-0-0-1.r04.atlnga05.us.bb.gin.ntt.net (129.250.4.88) 1.027 ms 0.807 ms 0.760 ms 2 192.205.36.157 (192.205.36.157) 4.377 ms 2.789 ms 3.655 ms 3 cr2.attga.ip.att.net (12.122.117.122) 11.292 ms 27.985 ms 10.449 ms MPLS Label=24148 CoS=0 TTL=1 S=1 4 12.122.163.69 (12.122.163.69) 10.736 ms 11.141 ms 12.007 ms 5 *^C {master} - Jared
On Nov 23, 2016, at 2:08 PM, Doug Roberts <robertsdoug@gmail.com> wrote:
Here's what I see from here:
https://puu.sh/ss76o/27b9de01e6.png
-- Doug Roberts Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX)
CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
On Wed, Nov 23, 2016 at 1:03 PM, Jared Mauch <jared@puck.nether.net> wrote:
On Nov 23, 2016, at 1:33 PM, Doug Roberts via Outages <outages@outages.org> wrote:
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails:
Query Results: Router: Atlanta, GA - US Command: ping 45.31.x.x
Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Do you have details?
I’m showing atlas working fine measuring things, but others have asked me as well about issues, so continuing to look.
https://atlas.ripe.net/measurements/6939072/#!probes
More details of brokenness would be helpful either to me or to the NTT NOC.
- Jared
Hi Doug, On Wed, Nov 23, 2016 at 01:08:19PM -0600, Doug Roberts via Outages wrote:
Here's what I see from here:
I can't ping that IP address from anywhere outside AT&T, so this is not NTT specific. Used the NLNOG RING to do the measurement: https://ring.nlnog.net/participants/ job@master01:~$ ring-ping -v 107.202.236.1 noris01: timeout redpilllinpro01: timeout vshn01: timeout leaseweb04: timeout nexiu01: timeout citynetwork01: timeout linode04: timeout claranet04: timeout itps01: timeout prolocation01: timeout cambrium01: timeout poppr01: timeout openminds01: timeout inotel01: timeout glesys01: timeout hosteurope01: timeout riseup01: timeout altibox01: timeout solido02: timeout kinber01: timeout queryfoundry01: timeout hostvirtual01: timeout switchco01: timeout icanndns02: timeout keklolwtf01: timeout webair01: timeout digitalocean03: timeout mythicbeasts01: timeout lwlcom01: timeout heanet01: timeout 23media01: timeout suomi01: timeout netability01: timeout speakup01: timeout afilias01: timeout kpn01: timeout hosting90systems01: timeout nforce01: timeout proserve01: timeout trueinternet01: timeout comcast01: timeout seeweb01: timeout atw01: timeout iabg01: timeout 20c01: timeout bchnetwork01: timeout amsio01: timeout dhiraagu01: timeout beanfield01: timeout gwu01: timeout Kind regards, Job
-- *Doug Roberts* Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) <http://cytranet.com> CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
your footer makes no sense, this is a public mailing list.
What about 45.31.217.222? It seems to respond from everywhere except NTT: https://puu.sh/ss7RV/82cedcec8e.png The footer is corporate placed :p. -- *Doug Roberts* Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) <http://cytranet.com> CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. On Wed, Nov 23, 2016 at 1:13 PM, Job Snijders <job@instituut.net> wrote:
Hi Doug,
On Wed, Nov 23, 2016 at 01:08:19PM -0600, Doug Roberts via Outages wrote:
Here's what I see from here:
I can't ping that IP address from anywhere outside AT&T, so this is not NTT specific.
Used the NLNOG RING to do the measurement: https://ring.nlnog.net/ participants/
job@master01:~$ ring-ping -v 107.202.236.1 noris01: timeout redpilllinpro01: timeout vshn01: timeout leaseweb04: timeout nexiu01: timeout citynetwork01: timeout linode04: timeout claranet04: timeout itps01: timeout prolocation01: timeout cambrium01: timeout poppr01: timeout openminds01: timeout inotel01: timeout glesys01: timeout hosteurope01: timeout riseup01: timeout altibox01: timeout solido02: timeout kinber01: timeout queryfoundry01: timeout hostvirtual01: timeout switchco01: timeout icanndns02: timeout keklolwtf01: timeout webair01: timeout digitalocean03: timeout mythicbeasts01: timeout lwlcom01: timeout heanet01: timeout 23media01: timeout suomi01: timeout netability01: timeout speakup01: timeout afilias01: timeout kpn01: timeout hosting90systems01: timeout nforce01: timeout proserve01: timeout trueinternet01: timeout comcast01: timeout seeweb01: timeout atw01: timeout iabg01: timeout 20c01: timeout bchnetwork01: timeout amsio01: timeout dhiraagu01: timeout beanfield01: timeout gwu01: timeout
Kind regards,
Job
-- *Doug Roberts* Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) <http://cytranet.com> CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
your footer makes no sense, this is a public mailing list.
On Wed, Nov 23, 2016 at 01:19:13PM -0600, Doug Roberts wrote:
What about 45.31.217.222? It seems to respond from everywhere except NTT: https://puu.sh/ss7RV/82cedcec8e.png
double bang for your buck in some cases! :-) job@ntt02.ring.nlnog.net:~$ ping 45.31.217.222 PING 45.31.217.222 (45.31.217.222) 56(84) bytes of data. 64 bytes from 45.31.217.222: icmp_req=1 ttl=51 time=128 ms 64 bytes from 45.31.217.222: icmp_req=1 ttl=51 time=128 ms (DUP!) 64 bytes from 45.31.217.222: icmp_req=2 ttl=51 time=128 ms 64 bytes from 45.31.217.222: icmp_req=2 ttl=51 time=128 ms (DUP!) ^C --- 45.31.217.222 ping statistics --- 2 packets transmitted, 2 received, +2 duplicates, 0% packet loss, time 999ms rtt min/avg/max/mdev = 128.434/128.668/128.947/0.484 ms job@ntt02.ring.nlnog.net:~$ or in new york: RP/0/RP0/CPU0:r07.nycmny01.us.bb#ping 45.31.217.222 source 129.250.0.143 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 43/43/44 ms RP/0/RP0/CPU0:r07.nycmny01.us.bb# Kind regards, Job
Yeah, so totally unreachable from any of the ATLAS probes, but measurement is still running. https://atlas.ripe.net/measurements/6939080/#!probes - Jared
On Nov 23, 2016, at 2:08 PM, Doug Roberts <robertsdoug@gmail.com> wrote:
Here's what I see from here:
https://puu.sh/ss76o/27b9de01e6.png
-- Doug Roberts Doug@DougR.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX)
CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended for the addressee(s) named in this message. This communication may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not disclose the contents or take any action in reliance upon the information contained in this communication or any attachments. Do not deliver, distribute or copy this message and/or any attachments and, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
On Wed, Nov 23, 2016 at 1:03 PM, Jared Mauch <jared@puck.nether.net> wrote:
On Nov 23, 2016, at 1:33 PM, Doug Roberts via Outages <outages@outages.org> wrote:
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails:
Query Results: Router: Atlanta, GA - US Command: ping 45.31.x.x
Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Do you have details?
I’m showing atlas working fine measuring things, but others have asked me as well about issues, so continuing to look.
https://atlas.ripe.net/measurements/6939072/#!probes
More details of brokenness would be helpful either to me or to the NTT NOC.
- Jared
participants (7)
-
Ca By -
Doug Roberts -
Dovid Bender -
Dylan Page -
Jared Mauch -
Job Snijders -
Michael Snyder