Scheduled Database maintenance Sunday 02:00 UTC.Read More
Started 09:14 UTC. This page updates the moment the on-call engineer posts, with no editorial pass in between.
We are investigating elevated error rates on the API across all regions.
Probes run from six regions against the public endpoint, not from inside our own network. Uptime is the trailing ninety days.
Shown here because a rate limit you hit looks exactly like an outage. Check this before you open a ticket.
Usage
Last 30 Days
Work we know about, in the order it lands. Each window is placed in the quietest hour for the regions it touches, and it is released early whenever the work finishes early.
Up to 4 minutes of write unavailability during the failover.
No downtime. Existing sessions stay valid throughout.
No downtime, brief failover in two edge regions.
Every window is announced at least seven days ahead. If one is moved or cancelled, the change is posted here before it reaches your inbox.
Every incident gets a write-up within five working days, including the ones nobody noticed. Open any month to read it.
An online migration acquired a lock the planner did not predict, blocking writes to the ingest table. Events were buffered rather than dropped and drained within the hour. Migrations now run behind a lock timeout and a canary write.
One email when an incident opens, one when it resolves, and nothing in between. Scheduled maintenance goes out a week ahead.
Join 18,400 Readers From Product Teams Everywhere
Palisade Status
status@palisade.dev
Why the teams shipping fastest are the ones running the least exciting stack, plus three migrations worth copying.
© 2026 Palisade, Inc. All rights reserved.
All Systems Operational