[outages] HTTPv6 to rackspace.com

Fri Feb 12 14:05:38 EST 2016

Yeah we are not seeing any issues on this end.  I can pop something over to the team that handles that site but since this isn’t really a service disruption they will likely not look at it with great urgency.

Nolan Berry

Linux Systems Engineering

Rackspace DNS Engineering

________________________________
From: Outages <outages-bounces at outages.org> on behalf of Keith Stokes via Outages <outages at outages.org>
Sent: Friday, February 12, 2016 1:02 PM
To: Frank Bulk
Cc: outages at outages.org
Subject: Re: [outages] HTTPv6 to rackspace.com

I’m not seeing anything wrong with ICMP through Cox:

[keiths at nagios ~]$ ping6 www.rackspace.com<http://www.rackspace.com>
PING www.rackspace.com<http://www.rackspace.com>(2001:4801:1221:101:1c10:0:f5:116) 56 data bytes
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=1 ttl=53 time=42.6 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=2 ttl=53 time=42.1 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=3 ttl=53 time=45.0 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=4 ttl=53 time=50.0 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=5 ttl=53 time=41.1 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=6 ttl=53 time=42.2 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=7 ttl=53 time=41.3 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=8 ttl=53 time=41.4 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=9 ttl=53 time=40.9 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=10 ttl=53 time=41.7 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=11 ttl=53 time=42.3 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=12 ttl=53 time=40.7 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=13 ttl=53 time=42.2 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=14 ttl=53 time=40.9 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=15 ttl=53 time=48.3 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=16 ttl=53 time=43.9 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=17 ttl=53 time=42.6 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=18 ttl=53 time=44.6 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=19 ttl=53 time=56.3 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=20 ttl=53 time=41.8 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=21 ttl=53 time=47.9 ms
64 bytes from 2001:4801:1221:101:1c10:0:f5:116: icmp_seq=22 ttl=53 time=40.4 ms
^C
--- www.rackspace.com<http://www.rackspace.com> ping statistics ---
22 packets transmitted, 22 received, 0% packet loss, time 21665ms
rtt min/avg/max/mdev = 40.440/43.708/56.360/3.769 ms

On Feb 12, 2016, at 12:39 PM, Frank Bulk via Outages <outages at outages.org<mailto:outages at outages.org>> wrote:

Since 12:01 pm (U.S. Central) our monitoring system has seen HTTPv6 timeouts
(10 seconds) to http://www.rackspace.com.  I see no issues on downdetector,
twitter, or status.rackspace.com<http://status.rackspace.com>, but it's what I'm seeing.

Frank

root at nagios:/tmp# dig AAAA www.rackspace.com<http://www.rackspace.com> +short
wwwp.wip.rackspace.com<http://wwwp.wip.rackspace.com>.
2001:4801:1221:101:1c10:0:f5:116
root at nagios:/tmp#

root at nagios:/tmp# tcptraceroute6 www.rackspace.com<http://www.rackspace.com>
traceroute to www.rackspace.com<http://www.rackspace.com> (2001:4801:1221:101:1c10:0:f5:116) from
2607:fe28:0:1000::5, port 80, from port 46878, 30 hops max, 60 bytes packets
1  router-core.mtcnet.net<http://router-core.mtcnet.net> (2607:fe28:0:1000::1)  0.243 ms  0.200 ms  0.215
ms
2  sxct.spnc.mtcnet.net<http://sxct.spnc.mtcnet.net> (2607:fe28:11:1002::194)  0.265 ms  0.143 ms  0.252
ms
3  v6-premier.movl-mlx.fbnt.netins.net<http://v6-premier.movl-mlx.fbnt.netins.net> (2001:5f8:7f0a:1::1)  5.026 ms
4.951 ms  4.996 ms
4  v6-ins-kb1-te-12-2-3031.kmrr.netins.net<http://v6-ins-kb1-te-12-2-3031.kmrr.netins.net> (2001:5f8:2:2::1)  8.742 ms
8.502 ms  8.589 ms
5  v6-ins-kc1-et-9-3.kmrr.netins.net<http://v6-ins-kc1-et-9-3.kmrr.netins.net> (2001:5f8::28:1)  8.844 ms  9.122 ms
8.753 ms
6  2001:438:fffe::e99 (2001:438:fffe::e99)  13.985 ms  13.984 ms  13.963 ms
7  ae5.cr1.ord2.us.zip.zayo.com<http://ord2.us.zip.zayo.com> (2001:438:ffff::407d:1e59)  22.827 ms
22.788 ms  22.808 ms
8  ae9.mpr1.ord11.us.zip.zayo.com<http://ord11.us.zip.zayo.com> (2001:438:ffff::407d:186a)  22.414 ms
22.419 ms  22.410 ms
9  ae4.mpr1.ord5.us.zip.zayo.com<http://ord5.us.zip.zayo.com> (2001:438:ffff::407d:185e)  23.037 ms
23.496 ms  22.727 ms
10  * * *
11  2001:4801:800:dc1:cb:: (2001:4801:800:dc1:cb::)  26.583 ms  26.508 ms
26.925 ms
12  2001:4801:800:dc1:cb::1 (2001:4801:800:dc1:cb::1)  26.423 ms  26.736 ms
26.542 ms
13  2001:4801:800:cb:c2::1 (2001:4801:800:cb:c2::1)  24.903 ms  24.096 ms
24.082 ms
14  2001:4801:800:c2:401a:1:0:1 (2001:4801:800:c2:401a:1:0:1)  26.168 ms
26.109 ms  26.127 ms
15  2001:4801:1221:101:1c10:0:f5:116 (2001:4801:1221:101:1c10:0:f5:116)
26.837 ms [open]  27.032 ms  26.243 ms
root at nagios:/tmp#

NAGIOS log:
Service Ok[02-12-2016 12:27:41] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;HARD;2;HTTP OK: HTTP/1.1 200 OK - 73966 bytes in
0.626 second response time
Service Critical[02-12-2016 12:26:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;HARD;2;CRITICAL - Socket timeout after 10
seconds
Service Critical[02-12-2016 12:25:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:24:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;HARD;2;HTTP OK: HTTP/1.1 200 OK - 73998 bytes in
9.183 second response time
Service Critical[02-12-2016 12:22:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;HARD;2;CRITICAL - Socket timeout after 10
seconds
Service Critical[02-12-2016 12:21:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:18:41] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;HARD;2;HTTP OK: HTTP/1.1 200 OK - 73965 bytes in
2.579 second response time
Service Critical[02-12-2016 12:17:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;HARD;2;CRITICAL - Socket timeout after 10
seconds
Service Critical[02-12-2016 12:16:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:13:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 73965 bytes in
9.002 second response time
Service Critical[02-12-2016 12:12:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:11:41] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 73964 bytes in
0.847 second response time
Service Critical[02-12-2016 12:10:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:09:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 73990 bytes in
7.554 second response time
Service Critical[02-12-2016 12:08:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:06:41] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 73989 bytes in
2.260 second response time
Service Critical[02-12-2016 12:05:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds
Service Ok[02-12-2016 12:04:41] SERVICE ALERT:
www_rackspace_com;HTTPv6;OK;HARD;2;HTTP OK: HTTP/1.1 200 OK - 73989 bytes in
1.530 second response time
Service Critical[02-12-2016 12:02:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;HARD;2;CRITICAL - Socket timeout after 10
seconds
Service Critical[02-12-2016 12:01:51] SERVICE ALERT:
www_rackspace_com;HTTPv6;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10
seconds

_______________________________________________
Outages mailing list
Outages at outages.org<mailto:Outages at outages.org>
https://puck.nether.net/mailman/listinfo/outages

---

Keith Stokes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20160212/bce17413/attachment.htm>