API errors during maintenance operation

What to do

• Check whether your product depends on Keeper. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-04-01 01:40 UTC and 2026-03-31 03:00 UTC may need a replay.

• Subscribe to Keeper's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=keeper works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Keeper 1

1. resolvedMar 31, 2026, 3:00 AM UTC

   On March 30 at 8:00 PM PST, Keeper performed a scheduled minor upgrade to our multi-region AWS RDS clusters as part of routine maintenance. The upgrade itself completed in approximately 3 minutes, followed by a standard application restart process that took about 15 minutes. While this process is typically non-disruptive, recent changes to service health checks caused unexpected customer impact during the restart window. This maintenance was not communicated in advance due to an internal miscommunication and the expectation of no impact. We apologize for the disruption and are taking steps to ensure all future maintenance—regardless of expected impact—is communicated ahead of time, as well as reviewing our health check configurations to prevent similar issues.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.