Recurly's Backup Mess Takes Days to Clean Up

Posted by samzenpus on Monday September 10, 2012 @06:58AM from the best-practices dept.

A cascading hardware outage struck subscription payment provider Recurly last week, and that started a long example in how not to manage critical infrastructure. From the article: "Last Monday, the payment provider suffered an intermittent hardware failure, which prevented the company from processing either payments or refunds. The company says it serves over 1,000 customers, including Adobe, BrightCove, and Fox News Radio, processing recurring payments for subscriptions. By Friday, the company still hadn’t completely straightened out the mess, providing updates to customers using payment gateways such as Authorize.net and LinkPoint/First Data."

3 of 21 comments (clear)

Min score:

Reason:

Sort:

Reminds me of Authorize.net by Mr.+Kinky · 2012-09-10 06:58 · Score: 4, Funny

This case reminds me of our payment processor Authorize.net in 2009, when a fire took down the whole network and infrastructure for many days. It was only solved when one of the guys over at Authorize.net literally
1. Re:Reminds me of Authorize.net by MetalliQaZ · 2012-09-10 07:00 · Score: 5, Funny
  
  He would have finished the story but he had a cascading hardware failure that took out his network...
  
  --
  "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
I would've been leery of... by Anonymous Coward · 2012-09-10 07:23 · Score: 5, Funny

...a service provider named Recurly in the first place.
Same goes for any provider named Relarry, Remoe or Reshemp either for that matter.