Re: 365 Datacenters Tampa AC Failure

2023-06-12 Thread James Ashton
Hello all, 
>From our side (365 Data Centers) We saw the issue start at a little after 6:30 
>PM yesterday. We had a component failure and we saw a rise in temperature. We 
>brought additional capacity online while we were working with our vendors on 
>getting replacement hardware. 
The hardware has now been replaced and the system is back online. 
This unit and others in this suite are on the block for replacement this year 
as we add cooling capacity to our various spaces within the Franklin Exchange 
building. 

On a side note, this was not related to the issue mentioned from earlier in the 
month. This was a straight component failure and replacement. 

Any customers impacted can reach out to the 365 Customer Service Center for 
details and documentation. 

Thank you, 
James Ashton 
VP Network Engineering 
365 Data Centers 





From: "NANOG mailing list"  
To: "George Herbert"  
Cc: "NANOG mailing list"  
Sent: Monday, June 12, 2023 8:03:10 PM 
Subject: Re: 365 Datacenters Tampa AC Failure 

Issue started a little after 2am, I was hard down till about 11:30am (servers 
did a high temp shutdown) 

On Jun 12, 2023 8:01 PM, Michael Spears  wrote: 



Yep there's issues over there. They had some compressors go down. Should be 
getting back to normal now... Hasn't been a good month for them in regards to 
cooling.. 

On Jun 12, 2023 7:15 PM, George Herbert  wrote: 

BQ_BEGIN


Oof. Get ready to replace all spinning media you may have there. 

-George 

Sent from my iPhone 

> On Jun 12, 2023, at 4:06 PM, Nick Olsen  wrote: 
> 
> 
> Just a heads up to anyone else colo'd at 365 TPA1/TAMSFLDE. Currently seeing 
> floor temps of ~105F as reported by equipment. Started yesterday at ~5:30PM 
> eastern. 2nd AC failure in the last 30 days. They have not sent any advisory 
> notices as of yet. 





BQ_END




Re: Colocation providers and ACL requests

2011-10-27 Thread James Ashton
Christopher,
 This is pretty common policy.  Not many datacenters of any size is going to 
act differently.  If you don't purchase this service then you will not get the 
service.

 They may be willing work work with you on black-holing problem IPs though.  
This is pretty common, but don't expect a filtering package without purchasing 
it.

James

- Original Message -
From: Christopher Pilkington c...@0x1.net
To: NANOG mailing list nanog@nanog.org
Sent: Tuesday, October 25, 2011 2:43:00 PM
Subject: Colocation providers and ACL requests

Is it common in the industry for a colocation provider, when requested to put 
an egress ACL facing us such as:

  deny udp any a.b.c.d/24 eq 80

…to refuse and tell us we must subscribe to their managed DDOS product?

-cjp





RE: the Intercage mess

2008-09-25 Thread James Ashton
No, but forcing them offline now that they are taking a new approach to
handling abuse is ridiculous.

Intercage are reaching out to the anti-abuse community and yet some
people on NANOG keep interfering with the cleanup process. How do you
expect them to clean up their network and return to normal operations
(with considerably less abuse) if it keeps being disconnected?

The shit isn't even there anymore. These kids have moved it elsewhere.
Intercage have learned their lesson, just leave them alone and let the
people who have *real* problems (e.g. me, Andrew Kirch of AHBL,
Spamhaus, Gadi, etc.) with Intercage deal with this.

If anyone has any issue with Atrivo/Intercage that still needs
rectification: please contact me or Andrew Kirch offlist and we will
bring it to their attention. We have contact with these people, and they
are listening and taking action to clean up their network.

If not, then please stop with this thread. It's not helpful, and it's
certaintly counter-productive.

William



William,
 This above email is a bit off. It sounds a bit like you feel that Nanog is 
your (Gadi/you/Andrew/Spamhaus) stick to force Intercage to fall in line. Not 
that they have been whacked with the stick you want the rest of us to leave 
them along so YOU can deal with it.   But it is NOT your place to deal with it 
any more than it is mine. It is a community issue dealt with by the community 
and if the community (I.E. those who have killed intercage's connectivity) 
choose to keep it that way as opposed to taking the chance that this company, 
with a LONG history, will continue to spew unwanted traffic, well...   That's 
not your call.

 It is not your place to tell someone else how to run their network and it is 
not your place to deal with the intercage issue on behalf of anyone else.


James