Service status
Live availability, incident history and scheduled maintenance for the Kindle Holdings platform.
Live status
Status page not yet connected.Live availability will be published at TBC: status page URL — e.g. an Instatus or Statuspage instance, hosted separately from this site so it stays up when we do not.
Until that exists this page must not display an uptime figure, and the “All systems operational” line in the site footer should be removed. A status page that is hard-coded to say everything is fine is worse than having none.
What we monitor
| Component | Covers |
|---|---|
| Web app | app.kindlehdgs.com, sign-in, issue and cycle views |
| API | REST and GraphQL endpoints |
| Webhooks | Outbound delivery and retry queue |
| Integrations | GitHub, GitLab and Slack sync workers |
| Transactional and digest delivery |
How we communicate
- An incident is opened within 15 minutes of detection, before we know the cause.
- Updates every 30 minutes while it is open, even when the update is that we still do not know.
- A written post-mortem within five business days for anything that degraded service for more than an hour, including what we are changing.
- Subscribe on the status page for email, RSS or Slack alerts.
Scheduled maintenance
Planned work that carries any risk of downtime is announced at least 72 hours ahead and scheduled between 14:00 and 18:00 UTC on a Saturday, which is the lowest-traffic window across our customer base. Most deploys need no window at all.