Status
Live status lives on its own domain
Deliberately. A status page hosted inside the app it reports on is useless exactly when you need it, so ours runs on separate infrastructure at status.stacked.app.
What is monitored
Not just “the site is up”. Each connector is checked independently, because the failure you actually care about is one platform refusing posts while everything else is fine.
Per-connector checks
- YouTube postingReported on status.stacked.app
- Instagram postingReported on status.stacked.app
- TikTok postingReported on status.stacked.app
- X postingReported on status.stacked.app
- LinkedIn postingReported on status.stacked.app
- Threads postingReported on status.stacked.app
- Bluesky postingReported on status.stacked.app
- Pinterest postingReported on status.stacked.app
- Facebook postingReported on status.stacked.app
- Discord postingReported on status.stacked.app
Also monitored
- App and marketing site availability, from four regions.
- Draft generation latency, with the 8-second budget as the alert threshold.
- The media pipeline: transcode, transcription, render.
- Scheduled job execution, so a queue that silently stops running raises an alarm.
- Webhook delivery for API customers.
During an incident
The status page updates first, then a banner appears in the app on the affected screens. Drafts keep generating throughout — only the outbound step pauses.
When a platform is at fault
We quote the platform’s own message verbatim rather than translating it, because the exact wording is what you need if you have to appeal to them.
Afterwards
Anything user-visible gets a short write-up on the status page and, if it lost anyone work, an email. No "some users may have experienced".
Something broken that status.stacked.app says is fine? Email support@stacked.app or check why a post failed.