March 2012 - Outages - Outages Lists

Amazon EC2
by Michael R. Self 26 Mar '12

26 Mar '12

We are seeing issues with our Amazon EC2 instances that appear to be networking related. Amazon has not updated their status dashboard (like they EVER do in a timely fashion, right?). Anybody else seeing packet loss or other EC2 issues in general that would lead on to the conclusion that Amazon is having AWS problems? Thank you, Mike. ____________________________________________ [cid:05E7E6FE-31D7-4AC8-889C-7AA2A68B282E] Michael R Self My PhoneFusion ONE number - 954.644.5000 (office/home/fax/mobile/SMS/VoIP) Disclaimer: If this email isn't for you, get rid of it.

7 6

Re: [outages] Anyone else seeing IPv6 issues going through Level3?
by Frank Bulk 17 Mar '12

17 Mar '12

Please share a target IP and a traceroute so others can test from their perspective. Frank -----Original Message----- From: outages-bounces(a)outages.org [mailto:outages-bounces@outages.org] On Behalf Of TJ Scott Sent: Saturday, March 17, 2012 11:03 AM To: outages(a)outages.org Subject: Re: [outages] Outages Digest, Vol 46, Issue 8 I'm seeing outage on level3 in Atlanta TJ Scott Sent from my iPhone On Mar 17, 2012, at 12:02 PM, "outages-request(a)outages.org" <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. Re: Anyone else seeing IPv6 issues going through Level3? > (Frank Bulk) > 2. Re: Anyone else seeing IPv6 issues going through Level3? > (Frank Bulk) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Mar 2012 18:50:11 -0500 > From: "Frank Bulk" <frnkblk(a)iname.com> > To: <outages(a)outages.org> > Subject: Re: [outages] Anyone else seeing IPv6 issues going through > Level3? > Message-ID: <00ff01cd03cf$868c07d0$93a41770$(a)iname.com> > Content-Type: text/plain; charset="us-ascii" > > Our upstream provider opened up a ticket with Level3 late this afternoon. > Hopefully it will be resolved, soon. > > Our upstream provider has three dual-stacked transit providers and they shut > down the Level3 IPv6 peering, but then we lost access to another third or so > of the sites. For example, ipv6.t-mobile.com is only visible to us from > Level3, same with www.globalcrossing.com. ipv6.cablelabs.com is with HE and > Level3 and we should be able to get HE via Sprint, but we lost visibility > anyways. > > Frank > > -----Original Message----- > From: outages-bounces(a)outages.org [mailto:outages-bounces@outages.org] On > Behalf Of Frank Bulk > Sent: Friday, March 16, 2012 8:05 AM > To: 'Teun Vink' > Cc: outages(a)outages.org > Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3? > > Thanks, Teun. > > Someone else pointed to me offlist that this could be just our prefix, > 2607:fe28::/32. I've already contacted our upstream provider who buys the > transit from Level3. > > Frank > > -----Original Message----- > From: Teun Vink [mailto:teun@teun.tv] > Sent: Friday, March 16, 2012 7:39 AM > To: Frank Bulk > Cc: outages(a)outages.org > Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3? > > On Fri, 2012-03-16 at 07:12 -0500, Frank Bulk wrote: >> I monitor over 30 IPv6 hosts, and starting around 1:54 am (Central) I >> couldn't access about a third of them. Here's the list of sites that I >> currently can't access: >> > > http://ring.nlnog.net promotime :) > > Just ran a few tests from 88 host in 78 ASN's, 24 countries: > >> ipv6_akamai_com_29 (2001:418:2401:9::8367:8929) > > $ ring-ping 2001:418:2401:9::8367:8929 > 2001:418:2401:9::8367:8929 - 87 servers: 119ms average > 2001:418:2401:9::8367:8929 - unreachable via: 1 server > >> ipv6_akamai_com_40 (2001:418:2401:9::8367:8940_ > > $ ring-ping 2001:418:2401:9::8367:8940 > 2001:418:2401:9::8367:8940 - 87 servers: 120ms average > 2001:418:2401:9::8367:8940 - unreachable via: 1 server > >> ipv6_cnn_com > > bit@bit01:~$ ring-http ipv6.cnn.com > unreachable via: 88 hosts > >> ipv6_google_com > > $ ring-http ipv6.google.com > unreachable via: 88 hosts > >> ipv6_sprint_com > > $ ring-http ipv6.sprint.com > 88 servers: OK > > > A ring-trace from all these hosts to 2001:418:2401:9::8367:8940 > https://ring.nlnog.net/paste/p/pv2jaodnosy8mget > > > regards, > Teun > > > > > _______________________________________________ > Outages mailing list > Outages(a)outages.org > https://puck.nether.net/mailman/listinfo/outages > >

2 2

Re: [outages] Outages Digest, Vol 46, Issue 8
by TJ Scott 17 Mar '12

17 Mar '12

I'm seeing outage on level3 in Atlanta TJ Scott Sent from my iPhone On Mar 17, 2012, at 12:02 PM, "outages-request(a)outages.org" <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. Re: Anyone else seeing IPv6 issues going through Level3? > (Frank Bulk) > 2. Re: Anyone else seeing IPv6 issues going through Level3? > (Frank Bulk) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Mar 2012 18:50:11 -0500 > From: "Frank Bulk" <frnkblk(a)iname.com> > To: <outages(a)outages.org> > Subject: Re: [outages] Anyone else seeing IPv6 issues going through > Level3? > Message-ID: <00ff01cd03cf$868c07d0$93a41770$(a)iname.com> > Content-Type: text/plain; charset="us-ascii" > > Our upstream provider opened up a ticket with Level3 late this afternoon. > Hopefully it will be resolved, soon. > > Our upstream provider has three dual-stacked transit providers and they shut > down the Level3 IPv6 peering, but then we lost access to another third or so > of the sites. For example, ipv6.t-mobile.com is only visible to us from > Level3, same with www.globalcrossing.com. ipv6.cablelabs.com is with HE and > Level3 and we should be able to get HE via Sprint, but we lost visibility > anyways. > > Frank > > -----Original Message----- > From: outages-bounces(a)outages.org [mailto:outages-bounces@outages.org] On > Behalf Of Frank Bulk > Sent: Friday, March 16, 2012 8:05 AM > To: 'Teun Vink' > Cc: outages(a)outages.org > Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3? > > Thanks, Teun. > > Someone else pointed to me offlist that this could be just our prefix, > 2607:fe28::/32. I've already contacted our upstream provider who buys the > transit from Level3. > > Frank > > -----Original Message----- > From: Teun Vink [mailto:teun@teun.tv] > Sent: Friday, March 16, 2012 7:39 AM > To: Frank Bulk > Cc: outages(a)outages.org > Subject: Re: [outages] Anyone else seeing IPv6 issues going through Level3? > > On Fri, 2012-03-16 at 07:12 -0500, Frank Bulk wrote: >> I monitor over 30 IPv6 hosts, and starting around 1:54 am (Central) I >> couldn't access about a third of them. Here's the list of sites that I >> currently can't access: >> > > http://ring.nlnog.net promotime :) > > Just ran a few tests from 88 host in 78 ASN's, 24 countries: > >> ipv6_akamai_com_29 (2001:418:2401:9::8367:8929) > > $ ring-ping 2001:418:2401:9::8367:8929 > 2001:418:2401:9::8367:8929 - 87 servers: 119ms average > 2001:418:2401:9::8367:8929 - unreachable via: 1 server > >> ipv6_akamai_com_40 (2001:418:2401:9::8367:8940_ > > $ ring-ping 2001:418:2401:9::8367:8940 > 2001:418:2401:9::8367:8940 - 87 servers: 120ms average > 2001:418:2401:9::8367:8940 - unreachable via: 1 server > >> ipv6_cnn_com > > bit@bit01:~$ ring-http ipv6.cnn.com > unreachable via: 88 hosts > >> ipv6_google_com > > $ ring-http ipv6.google.com > unreachable via: 88 hosts > >> ipv6_sprint_com > > $ ring-http ipv6.sprint.com > 88 servers: OK > > > A ring-trace from all these hosts to 2001:418:2401:9::8367:8940 > https://ring.nlnog.net/paste/p/pv2jaodnosy8mget > > > regards, > Teun > > > > > _______________________________________________ > Outages mailing list > Outages(a)outages.org > https://puck.nether.net/mailman/listinfo/outages > >

1 0

Anyone else seeing IPv6 issues going through Level3?
by Frank Bulk 16 Mar '12

16 Mar '12

I monitor over 30 IPv6 hosts, and starting around 1:54 am (Central) I couldn't access about a third of them. Here's the list of sites that I currently can't access: ipv6_akamai_com_29 (2001:418:2401:9::8367:8929) ipv6_akamai_com_40 (2001:418:2401:9::8367:8940_ ipv6_cnn_com ipv6_google_com ipv6_sprint_com www-v6_cisco_com www_charter_com www_facebook_com_b (2620:0:1c18:0:face:b00c:0:2) www_ipv6_cisco_com www_sprint_net www_sprintv6_net Here's a sample of traceroutes: nagios:/home/fbulk# tcptraceroute6 www.sprintv6.net traceroute to www.sprint.net (2600::) from 2607:fe28:0:1000::5, port 80, from port 58614, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.080 ms 1.550 ms 1.356 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.856 ms 1.738 ms 1.661 ms 3 sxct.movl.mtcnet.net (2607:fe28:11:1002::194) 2.064 ms 1.966 ms 1.311 ms 4 v6-siouxcenter.movl.153.netins.net (2001:5f8:7f06::9) 4.128 ms 3.417 ms 3.048 ms 5 v6-ins-kb1-te-13-2-220.kmrr.netins.net (2001:5f8:2:2::1) 9.347 ms 8.930 ms 8.606 ms 6 v6-ins-kc2-te-8-3.kmrr.netins.net (2001:5f8::11:1) 9.258 ms 8.897 ms 8.549 ms 7 v6-ins-dc1-et-8-1.desm.netins.net (2001:5f8::8:1) 10.902 ms 10.494 ms 10.268 ms 8 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 195.453 ms 232.440 ms 230.230 ms 9 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 17.244 ms 16.887 ms 16.524 ms 10 vl-4049.car1.Dallas1.Level3.net (2001:1900:4:1::379) 26.470 ms 26.076 ms 25.764 ms 11 vl-70.edge2.Dallas3.Level3.net (2001:1900:17:2::e) 26.664 ms 26.417 ms 26.058 ms 12 * * * 13 * * * 14 * * * nagios:/home/fbulk# tcptraceroute6 www.sprint.net traceroute to www.sprint.net (2600::) from 2607:fe28:0:1000::5, port 80, from port 55242, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.072 ms 1.533 ms 1.486 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.847 ms 1.862 ms 1.698 ms 3 sxct.movl.mtcnet.net (2607:fe28:11:1002::194) 2.187 ms 1.957 ms 1.220 ms 4 v6-siouxcenter.movl.153.netins.net (2001:5f8:7f06::9) 4.114 ms 3.318 ms 3.055 ms 5 v6-ins-kb1-te-13-2-220.kmrr.netins.net (2001:5f8:2:2::1) 9.291 ms 8.873 ms 8.612 ms 6 v6-ins-kc2-te-8-3.kmrr.netins.net (2001:5f8::11:1) 9.252 ms 8.907 ms 8.610 ms 7 v6-ins-dc1-et-8-1.desm.netins.net (2001:5f8::8:1) 10.926 ms 10.539 ms 10.221 ms 8 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 17.221 ms 16.776 ms 16.511 ms 9 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 17.159 ms 16.885 ms 16.518 ms 10 vl-4049.car1.Dallas1.Level3.net (2001:1900:4:1::379) 26.486 ms 26.074 ms 25.743 ms 11 vl-70.edge2.Dallas3.Level3.net (2001:1900:17:2::e) 26.751 ms 26.432 ms 26.132 ms 12 * * * 13 * * * 14 * * * nagios:/home/fbulk# tcptraceroute6 www.ipv6.cisco.com traceroute to www.ipv6.cisco.com (2001:420:80:1::5) from 2607:fe28:0:1000::5, port 80, from port 53137, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.131 ms 1.190 ms 1.849 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.628 ms 2.158 ms 1.554 ms 3 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 2.618 ms 1.810 ms 1.190 ms 4 v6-siouxcenter.sxcy.137.netins.net (2001:5f8:7f06::5) 3.621 ms 2.928 ms 2.638 ms 5 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 7.297 ms 6.957 ms 6.652 ms 6 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 9.145 ms 8.752 ms 8.447 ms 7 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 15.418 ms 15.064 ms 14.727 ms 8 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 15.492 ms 15.020 ms 14.721 ms 9 vl-4049.car1.Dallas1.Level3.net (2001:1900:4:1::379) 24.696 ms 24.282 ms 24.144 ms 10 vl-70.edge2.Dallas3.Level3.net (2001:1900:17:2::e) 24.738 ms 24.489 ms 24.148 ms 11 * * * 12 * * * 13 * * * (facebook) nagios:/home/fbulk# tcptraceroute6 2620:0:1c18:0:face:b00c:0:2 traceroute to 2620:0:1c18:0:face:b00c:0:2 (2620:0:1c18:0:face:b00c:0:2) from 2607:fe28:0:1000::5, port 80, from port 47528, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.066 ms 1.243 ms 1.960 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.626 ms 2.268 ms 1.307 ms 3 sxct.movl.mtcnet.net (2607:fe28:11:1002::194) 2.592 ms 1.874 ms 1.238 ms 4 v6-siouxcenter.movl.153.netins.net (2001:5f8:7f06::9) 4.018 ms 3.341 ms 2.994 ms 5 v6-ins-kb1-te-13-2-220.kmrr.netins.net (2001:5f8:2:2::1) 9.367 ms 8.873 ms 8.656 ms 6 v6-ins-kc2-te-8-3.kmrr.netins.net (2001:5f8::11:1) 9.285 ms 8.980 ms 8.529 ms 7 v6-ins-dc1-et-8-1.desm.netins.net (2001:5f8::8:1) 10.944 ms 10.493 ms 10.231 ms 8 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 17.559 ms 16.798 ms 16.514 ms 9 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 200.575 ms 233.140 ms 224.720 ms 10 vl-4049.car1.Dallas1.Level3.net (2001:1900:4:1::379) 26.312 ms 26.100 ms 25.774 ms 11 vl-4080.car2.Dallas1.Level3.net (2001:1900:4:1::82) 111.124 ms 131.324 ms 226.032 ms 12 vl-4061.car1.Atlanta2.Level3.net (2001:1900:4:1::96) 46.276 ms 45.963 ms 45.564 ms 13 vl-51.edge5.Atlanta2.Level3.net (2001:1900:1c:1::f) 45.928 ms 45.579 ms 45.292 ms 14 * * * 15 * * * 16 * * * nagios:/home/fbulk# tcptraceroute6 www.charter.com traceroute to www.charter.com (2607:f428:3:1:80:80:80:1) from 2607:fe28:0:1000::5, port 80, from port 44115, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.108 ms 1.280 ms 1.852 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.584 ms 2.204 ms 1.805 ms 3 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 2.515 ms 2.218 ms 1.197 ms 4 v6-siouxcenter.sxcy.137.netins.net (2001:5f8:7f06::5) 4.017 ms 2.944 ms 2.744 ms 5 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 7.451 ms 7.004 ms 6.764 ms 6 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 9.132 ms 8.831 ms 8.481 ms 7 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 184.676 ms 202.524 ms 203.065 ms 8 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 15.518 ms 15.134 ms 14.832 ms 9 vl-4049.car1.Dallas1.Level3.net (2001:1900:4:1::379) 65.261 ms 207.228 ms 41.498 ms 10 vl-80.edge2.Dallas3.Level3.net (2001:1900:17:3::e) 24.999 ms 56.325 ms 30.592 ms 11 CenturyTel-level3-10.dallas3.Level3.net (2001:1900:4:3::1c2) 25.072 ms 24.780 ms 24.480 ms 12 2001:428::205:171:202:195 (2001:428::205:171:202:195) 37.480 ms 37.165 ms 36.814 ms 13 * * * 14 * * * 15 * * * nagios:/home/fbulk# tcptraceroute6 ipv6.google.com traceroute to gx-in-x68.1e100.net (2001:4860:8002::68) from 2607:fe28:0:1000::5, port 80, from port 42606, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.041 ms 1.482 ms 1.418 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.870 ms 1.729 ms 1.665 ms 3 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 2.041 ms 1.994 ms 1.187 ms 4 v6-siouxcenter.sxcy.137.netins.net (2001:5f8:7f06::5) 3.778 ms 2.955 ms 2.669 ms 5 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 7.361 ms 7.053 ms 6.874 ms 6 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 9.146 ms 8.804 ms 8.407 ms 7 te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d) 69.291 ms 39.541 ms 15.380 ms 8 vl-11.car1.KansasCity1.Level3.net (2001:1900:4:1::37d) 15.399 ms 15.015 ms 14.720 ms 9 vl-4049.car1.Dallas1.Level3.net (2001:1900:4:1::379) 24.589 ms 24.209 ms 23.975 ms 10 vl-90.edge2.Dallas3.Level3.net (2001:1900:17:4::e) 24.698 ms 24.368 ms 24.078 ms 11 2001:1900:4:3::256 (2001:1900:4:3::256) 24.889 ms 24.411 ms 24.131 ms 12 2001:4860::1:0:57f (2001:4860::1:0:57f) 25.081 ms 24.648 ms 24.285 ms 13 2001:4860::8:0:2c9c (2001:4860::8:0:2c9c) 25.154 ms 24.816 ms 24.506 ms 14 * * * 15 * * *

2 5

EC2 east region
by Corey Quinn 15 Mar '12

15 Mar '12

Looks like AWS has taken a hit in East (Virginia). EC2 outages is what we're seeing here, no word yet on other services. Amazon has yet to confirm this, but Twitter is all… atwitter, about it. -- Corey / KB1JWQ

4 4

[ADMIN] wiki.outages.org Planned Maintenance tomorrow (3/9/12) from 10am to 11am PST.
by virendra rode 08 Mar '12

08 Mar '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Change Type: High___ Medium__ Low_X_ Type of Maintenance: Security update. Window Start: Tuesday 03/09/2012 10:00am PST Window End: Tuesday 03/09/2012 11:00am PST Service Impact: This maintenance is not expected to be service impacting. Schedule: The window for work is scheduled to begin at 10:00am tomorrow, Friday, March 09, and end at 11:00am PST (1 hrs). Should additional time be required, notice will be provided and the maintenance window will be expanded. Regression Planning: As with any maintenance, while highly unlikely, there is a possibility that something unexpected may occur during the maintenance process. Should any issues arise, all equipment will be placed back into standard operation and the maintenance will be postponed until the issue is resolved. Regression Instructions: Check for logs and reachability of the host. regards, admin team. Just like to make community aware that we have a planned maintenance for tonight (3/8/2012) starting 8pm PST. Window Start: 03/08/2012 - 8:00pm PST Window End: 03/08/2012 - 9:00pm PST We will be performing software maintenance on wiki.outages.org starting at 8:00pm tonight PST. However This re-route of traffic is being done a day prior to the change to make sure we have routing (ingress/egress) stability maintained during this change window. We plan to re-route the traffic back to LEVEL3 facing core after the upgrade window. We are expecting to re-route about 350mbps of traffic and wanted to give you a heads up. Our network engineering team will be on site performing this task on friday. Please let me know if you have any further questions. regards, /virendra -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAk9ZPkQACgkQ3HuimOHfh+FW7QEAhosTfH8rmaz39cxpbnoMxjxP AvMkMt4+oFN3tb0bdt4A/jD/9XzLjzXUNJXzXSnWxyNbVxJ0Kwt4vV5aq5jjvh+y =uzWC -----END PGP SIGNATURE-----

1 0

911 in Sarasota County, FL
by Kristian Kielhofner 07 Mar '12

07 Mar '12

Seems interesting: http://www.heraldtribune.com/article/20120307/BREAKING/120309642/0/sports?T… Anyone have any more details? -- Kristian Kielhofner

3 5

Paetec Issue
by J. Oquendo 07 Mar '12

07 Mar '12

Anyone have any issues using Paetec. We are getting a lot of dead air slash busy slash SIP WTH (should be a type!) coming out from the Albany/Buffalo/CT/NE regions. Anyone else? -- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ J. Oquendo SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT, RWSP, GREM "It takes 20 years to build a reputation and five minutes to ruin it. If you think about that, you'll do things differently." - Warren Buffett 42B0 5A53 6505 6638 44BB 3943 2BF7 D83F 210A 95AF http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2BF7D83F210A95AF

2 1

windstream outage?
by jason walter 06 Mar '12

06 Mar '12

There seems to be issues with Data and Voice services in florida. Anyone seeing the same issues..?

1 0

DreamHost down?
by Andy Ringsmuth 05 Mar '12

05 Mar '12

DreamHost appears to be down. www.dreamhost.com and associated domains. Mail affected as well. Can't ping them either. Unfortunately my e-mail is through them so I won't be able to see any responses to this. Here's my traceroute: Last login: Mon Mar 5 07:55:55 on console 618-Andy-Ringsmuth:~ andyring$ ping dreamhost.com PING dreamhost.com (208.97.187.204): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- dreamhost.com ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss 618-Andy-Ringsmuth:~ andyring$ traceroute dreamhost.com traceroute to dreamhost.com (208.97.187.204), 64 hops max, 52 byte packets 1 192.168.1.2 (192.168.1.2) 0.839 ms 0.229 ms 0.215 ms 2 208.82.104.193 (208.82.104.193) 0.714 ms 0.640 ms 0.588 ms 3 omh-edge-08.inet.qwest.net (65.116.176.185) 2.005 ms 2.240 ms 1.932 ms 4 chp-brdr-04.inet.qwest.net (67.14.8.234) 34.878 ms 21.132 ms 19.334 ms 5 te0-3-0-7.ccr22.ord03.atlas.cogentco.com (154.54.11.45) 24.035 ms 24.477 ms 24.683 ms 6 te0-5-0-1.ccr21.ord01.atlas.cogentco.com (154.54.43.229) 24.644 ms te0-0-0-1.ccr22.ord01.atlas.cogentco.com (154.54.1.97) 24.856 ms te0-3-0-0.ccr22.ord01.atlas.cogentco.com (154.54.5.1) 24.637 ms 7 te0-3-0-3.ccr21.mci01.atlas.cogentco.com (154.54.2.189) 45.331 ms te0-2-0-5.ccr21.mci01.atlas.cogentco.com (154.54.82.141) 45.237 ms te0-0-0-3.ccr22.mci01.atlas.cogentco.com (154.54.30.101) 45.872 ms 8 te0-3-0-1.ccr22.dfw01.atlas.cogentco.com (154.54.46.210) 50.593 ms te0-1-0-1.ccr21.dfw01.atlas.cogentco.com (154.54.5.169) 45.371 ms te0-0-0-2.ccr21.dfw01.atlas.cogentco.com (154.54.2.113) 45.784 ms 9 te0-0-0-3.ccr22.iah01.atlas.cogentco.com (154.54.24.25) 59.246 ms te0-0-0-3.ccr21.iah01.atlas.cogentco.com (154.54.5.205) 63.367 ms te0-1-0-1.ccr22.iah01.atlas.cogentco.com (154.54.5.138) 51.101 ms 10 te0-2-0-5.ccr21.lax01.atlas.cogentco.com (154.54.0.233) 69.451 ms te0-3-0-6.ccr22.lax01.atlas.cogentco.com (154.54.3.186) 69.189 ms te0-2-0-5.ccr22.lax01.atlas.cogentco.com (154.54.27.17) 69.259 ms 11 te4-4.ccr02.lax04.atlas.cogentco.com (154.54.1.10) 68.183 ms te3-8.ccr02.lax04.atlas.cogentco.com (154.54.24.70) 69.006 ms te4-8.ccr02.lax04.atlas.cogentco.com (154.54.6.242) 68.138 ms 12 38.104.210.174 (38.104.210.174) 69.554 ms 69.522 ms 70.024 ms 13 * * * 14 * * * 15 * * * 16 * * * ^C 618-Andy-Ringsmuth:~ andyring$ --- Andy Ringsmuth 7215 Dorchester Court Lincoln, NE 68521 (402) 304-0083 andyring(a)inebraska.com

6 5