without notification and there doesn't seem to be
any threshold or policy in place for when they do that.
Thanks,
-Drew
-Original Message-
From: Naveen Nathan [mailto:nav...@lastninja.net]
Sent: Wednesday, September 12, 2012 2:44 AM
To: nanog@nanog.org
Subject: Re: Heads-Up: Go
> we do not know what happened. we have an apology, not an explanation or
> reasonable post mortem. all else is conjecturbation.
Agreed. And as Chris and Kyle pointed out, there is no indication
that the problems were present in the BGP DFT, and the issues could've
occured over iBGP. I completel
we do not know what happened. we have an apology, not an explanation or
reasonable post mortem. all else is conjecturbation.
randy
(Arrive at the intended destination, that is)
On Tue, Sep 11, 2012 at 9:18 PM, Kyle Creyts wrote:
> +1
>
> Announcing a prefix doesn't mean that the traffic to those IPs found
> within shall ever arrive.
>
> On Tue, Sep 11, 2012 at 8:43 PM, Christopher Morrow
> wrote:
>> On Tue, Sep 11, 2012 at
+1
Announcing a prefix doesn't mean that the traffic to those IPs found
within shall ever arrive.
On Tue, Sep 11, 2012 at 8:43 PM, Christopher Morrow
wrote:
> On Tue, Sep 11, 2012 at 11:16 PM, Naveen Nathan wrote:
>>> Well, mostly I'm taking GoDaddy at their word that this was not a DoS
>>> at
On Tue, Sep 11, 2012 at 11:16 PM, Naveen Nathan wrote:
>> Well, mostly I'm taking GoDaddy at their word that this was not a DoS attack.
>>
>> I also believe it was related to BGP, and am happy to get more info. But we
>> are discussing Anonymous vs. Self-inflicted wound here.
>
> I'm skeptical,
> Well, mostly I'm taking GoDaddy at their word that this was not a DoS attack.
>
> I also believe it was related to BGP, and am happy to get more info. But we
> are discussing Anonymous vs. Self-inflicted wound here.
I'm skeptical, BGPlay (http://bgplay.routeviews.org/) doesn't show any
withd
On Tue, Sep 11, 2012 at 6:04 PM, ryanL wrote:
> when patrick is referring to "taking their word for it", he's referring to a
> post on outages@ by godaddy's network engineering manager that stated "bgp,
> and more details to follow".
"more" is the operating word here.
> i tend to align with patr
On Sep 11, 2012, at 17:04 , ryanL wrote:
> when patrick is referring to "taking their word for it", he's referring to a
> post on outages@ by godaddy's network engineering manager that stated "bgp,
> and more details to follow".
Well, mostly I'm taking GoDaddy at their word that this was not a
when patrick is referring to "taking their word for it", he's referring to
a post on outages@ by godaddy's network engineering manager that stated
"bgp, and more details to follow".
i tend to align with patrick's thought. i'm also interested to see the
details, which they are really under no oblig
The blog says 99.999% uptime, but I'm guessing this "outage" lasted
more them 5.4930002 minutes and they probably had other issues
during the year.
On 11 September 2012 21:53, Rubens Kuhl wrote:
>
> > No large flows reported to the affected NSes, tweets were suspicious at
> > best, other a
> No large flows reported to the affected NSes, tweets were suspicious at best,
> other anon-ops denied the attack was them, and GoDaddy admitted internal
> error.
>
> I'm going to take GoDaddy at their word, and give them major kudos for owning
> up to the mistake - in public.
That doesn't mea
On Sep 11, 2012, at 16:04 , Christopher Morrow wrote:
> On Tue, Sep 11, 2012 at 3:47 PM, Damian Menscher wrote:
>>
>> Summary: 30 minutes late on the start time, and off by well over an hour on
>> the stop time.
>
> even a broken clock is right 2x/day?
> nostrodamus was eventually right a few t
On Tue, Sep 11, 2012 at 3:47 PM, Damian Menscher wrote:
>
> Summary: 30 minutes late on the start time, and off by well over an hour on
> the stop time.
even a broken clock is right 2x/day?
nostrodamus was eventually right a few times?
'If you're cold, shoot until you get hot, then keep shooting!
ey said they would stop
> ironic?"
>
> -Original Message-
> From: William Herrin [mailto:b...@herrin.us]
> Sent: Tuesday, September 11, 2012 1:16 PM
> To: Kyle Creyts
> Cc: nanog@nanog.org
> Subject: Re: Heads-Up: GoDaddy Broke the Interwebs...
>
> On Tue, Sep 11, 2012
Cc: nanog@nanog.org
Subject: Re: Heads-Up: GoDaddy Broke the Interwebs...
On Tue, Sep 11, 2012 at 1:54 PM, Kyle Creyts wrote:
> http://www.godaddy.com/newscenter/release-view.aspx?news_item_id=410
"many of our customers experienced intermittent service outages"
Must be that new
On Tue, Sep 11, 2012 at 03:15:55PM -0400, William Herrin wrote:
> On Tue, Sep 11, 2012 at 1:54 PM, Kyle Creyts wrote:
> > http://www.godaddy.com/newscenter/release-view.aspx?news_item_id=410
>
> "many of our customers experienced intermittent service outages"
>
> Must be that new definition of t
On Tue, Sep 11, 2012 at 1:54 PM, Kyle Creyts wrote:
> http://www.godaddy.com/newscenter/release-view.aspx?news_item_id=410
"many of our customers experienced intermittent service outages"
Must be that new definition of the word "intermittent." The one
roughly synonymous with "total."
-Bill
--
o: Operations Dallas
> Cc: nanog@nanog.org
> Subject: Re: Heads-Up: GoDaddy Broke the Interwebs...
>
> No DDoS or Anonymous attack appears to have been involved.
>
> On Tue, Sep 11, 2012 at 10:54 AM, Kyle Creyts
> wrote:
>> http://www.godaddy.com/newscenter/rele
Now it's CNN
/Jason
-Original Message-
From: Kyle Creyts [mailto:kyle.cre...@gmail.com]
Sent: Tuesday, September 11, 2012 1:55 PM
To: Operations Dallas
Cc: nanog@nanog.org
Subject: Re: Heads-Up: GoDaddy Broke the Interwebs...
No DDoS or Anonymous attack appears to have been inv
e on routergod.com from Dance Patrick regarding
>> anycast DNS..
>> ~oliver
>>
>> Sent via DynaTAC. Please forgive spelling and grammar.
>>
>> -Original Message-
>> From: bill.ing...@t-systems.com
>> Date: Mon, 10 Sep 2012 19:13:
ing and grammar.
>
> -Original Message-
> From: bill.ing...@t-systems.com
> Date: Mon, 10 Sep 2012 19:13:27
> To: ;
> Subject: RE: Heads-Up: GoDaddy Broke the Interwebs...
>
>
> Looks like this may be a DDoS attack from Anonymous:
>
> http://techcrunch.com/2012/0
: Heads-Up: GoDaddy Broke the Interwebs...
For the last ~15 minutes I've been receiving complaints about DNS issues.
GoDaddy DNS is apparently b0rked. I'm also seeing a lot of tweets about their
hosting and VPS being down. I'm unable to access the control panel for one of
my cu
nonymous:
>
>
> http://techcrunch.com/2012/09/10/godaddy-outage-takes-down-millions-of-sites/
>
>
> -Original Message-
> From: Aaron C. de Bruyn [mailto:aa...@heyaaron.com]
> Sent: Monday, September 10, 2012 1:07 PM
> To: NANOG mailing list
> Subject: Heads-Up:
> From: Aaron C. de Bruyn [mailto:aa...@heyaaron.com]
> Sent: Monday, September 10, 2012 1:07 PM
> To: NANOG mailing list
> Subject: Heads-Up: GoDaddy Broke the Interwebs...
>
> For the last ~15 minutes I've been receiving complaints about DNS issues.
> GoDaddy DNS is
: GoDaddy Broke the Interwebs...
For the last ~15 minutes I've been receiving complaints about DNS issues.
GoDaddy DNS is apparently b0rked. I'm also seeing a lot of tweets about their
hosting and VPS being down. I'm unable to access the control panel for one of
my customer accounts.
-A
On Mon, Sep 10, 2012 at 2:07 PM, Aaron C. de Bruyn wrote:
> For the last ~15 minutes I've been receiving complaints about DNS
> issues. GoDaddy DNS is apparently b0rked. I'm also seeing a lot of
> tweets about their hosting and VPS being down. I'm unable to access
> the control panel for one of
Wow. Their own site is even down.
On Sep 10, 2012, at 2:07 PM, "Aaron C. de Bruyn" wrote:
> For the last ~15 minutes I've been receiving complaints about DNS
> issues. GoDaddy DNS is apparently b0rked. I'm also seeing a lot of
> tweets about their hosting and VPS being down. I'm unable to acc
For the last ~15 minutes I've been receiving complaints about DNS
issues. GoDaddy DNS is apparently b0rked. I'm also seeing a lot of
tweets about their hosting and VPS being down. I'm unable to access
the control panel for one of my customer accounts.
-A
29 matches
Mail list logo
