Elevated API Errors

Incident Report for Shippo

Postmortem

RedisToGo Outage Postmortem

Incident summary

On May 13 2015, our Redis provider RedisToGo experienced numerous service interruptions and drastic increase in latency throughout the day. This in turn caused system-wide interruptions on Shippo's end that affected rating and label purchase.

See http://status.redistogo.com/incidents/x1c77zxt14m9 for RedisToGo's incident history. During the downtime, we have migrated over to another provider.

What we are doing about it

  • We have immediately switched Redis providers. We have furthermore established a backup service to immediately switch providers in case of new downtimes.
  • We are (and have already been) working on a system-wide migration to not depend on external services like RedisToGo for all of our components. This migration is still in progress.
Posted 10 years ago. May 14, 2015 - 15:22 UTC

Resolved

Issue has been resolved.
Posted 10 years ago. May 13, 2015 - 23:28 UTC

Monitoring

The system is operational again and we are closely monitoring for further issues.
Posted 10 years ago. May 13, 2015 - 23:08 UTC

Investigating

We're experiencing an elevated level of API errors and are currently looking into the issue.
Posted 10 years ago. May 13, 2015 - 22:23 UTC