• Resolved beggers

    (@beggers)


    I tried to post this on your support site and got the message “something went wrong”. I’ve gotten this error more than once lately. This is from a link posted on Twitter (from the Shareaholic button on my site at vegasnews.com)

    bit.ly/2pvPfrT

    This page isn’t working
    ir.shareaholic.com took too long to respond.
    HTTP ERROR 504

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author shareaholic

    (@shareaholic)

    Our shortening service is currently operating in a degraded state (since ~4am EST). Our team is working on fixing the problem. Our sincere apologies for this.

    Plugin Author shareaholic

    (@shareaholic)

    All links should be working again. Again, sincere apologies for the downtime. It would have been taken care of much sooner if it didn’t hit us at 4am our time.

    goodereader

    (@goodereader)

    it seems to be down again

    Plugin Author shareaholic

    (@shareaholic)

    We’re currently facing an outage with Amazon Web Services. We’re working on it right now with the Amazon team. They’re on it. We appreciate your patience!

    Plugin Author shareaholic

    (@shareaholic)

    **All systems are back online** Thank you so much for your patience.

    There was no downtime in data/analytics collection, nor most other services including Related Posts. Share API was affected, however as was Shareaholic.com. We worked with Amazon through the night on the issue — thank you to them.

    The downtime was caused due to a bug in MySQL and Amazon’s hosted database service. A key Database server and its hot backup, both failed due to the bug. The perfect storm. The hot backup is also replicated and hosted across multiple data centers, so even if one whole data center goes down we have redundancy.

    To recover, we had to recover from a backup and to the exact time the failure occurred to avoid any data loss, which took a while to get through given our volume.

    We have followed all of Amazon’s best practices and we still had downtime. This was literally, almost worst case scenario, other than a nuke hitting Amazon data centers.

    We’re working on a plan with Amazon’s team to ensure this doesn’t happen again, including separately, making the Share API resilient to complete database unavailability.

    Again, thank you for your patience. We work hard to earn your trust and know how important this is.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.