API liveness
A liveness probe confirms the API can reach its database on a dedicated probe connection, separate from the connection pool that serves customer requests — so a busy pool cannot be mistaken for a dead process.
SkedCast status
SkedCast does not run a public real-time status page or publish a historical uptime percentage yet. This page describes how reliability actually works today, instead of inventing a number nobody is tracking.
What SkedCast status actually gets checked
Background worker heartbeat
The worker that actually publishes scheduled posts rewrites a heartbeat every few seconds. A missed heartbeat is what would surface a stalled worker before a customer notices a post that should have gone out did not.
Queue broker configuration
The job queue’s eviction policy is checked directly rather than assumed from how it was launched, because a silently misconfigured broker can quietly drop queued publish jobs.
During an incident
There is no incident subscription or automated status feed today. If something is not working, the real path is support — a person reads it, not a bot behind a status widget. Fixes that ship land in the changelog “Fixed” category afterward, dated and unedited.
Security and infrastructure practices
For the deeper technical picture — tenant isolation, encryption, access control and the responsible disclosure process — see the security page.
Status FAQ
- Is there a public status page with historical uptime percentages?
- Not yet. Publishing an uptime number implies months of tracked history behind it, and inventing one would be worse than not having a status page at all. This page describes the real checks that exist instead.
- How would I find out about an ongoing incident?
- Through support, directly. There is no subscribable incident feed or status-page service wired up yet — if something breaks, reaching support is the real path to an answer right now.
- What actually gets monitored?
- API liveness against the database, the background worker’s heartbeat (the process that publishes scheduled posts), and the job queue’s configuration — the same signals engineering watches, described honestly rather than summarized into a green checkmark with no substance behind it.
- Are fixed incidents documented anywhere?
- Real fixes are recorded after the fact in the changelog’s "Fixed" category, dated and unedited — the closest thing to an incident history that exists today.
- Will a real public status page be built?
- It is a reasonable thing to build later. This page exists so the honest current answer is written down rather than a status widget showing a number nobody is actually tracking.
- Does "no public status page" mean reliability is not taken seriously?
- No — it means the public-facing status page has not been built yet, which is a different gap than not monitoring at all. The security page documents the infrastructure and access-control practices in more depth.
Ready to broadcast everywhere?
Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.