Status
System Status
Real, live checks against this deployment's core services — not a static page.
Checked 10/28/2026, 10:33:30 PM
Core services
Configured integrations
Whether each optional integration is configured on this deployment. An integration shown as "Not configured" simply hasn't had its credentials set — it isn't an outage.
How to read this
What each state actually means
Operational
The service responded correctly when this page loaded. Checks run on request rather than on a cache, so this reflects the moment you opened it.
Not configured
No credentials are set for this integration on this deployment. Expected for any provider you haven't connected — not an error.
Unavailable
The service is configured but did not respond as expected. If this is a publishing dependency, queued posts will wait rather than fail outright.
When something breaks
Your posts are queued, not lost
Publishing runs through a job queue precisely so an outage delays work rather than destroying it.
Scheduled posts wait their turn
A post whose publish time passes during an outage is not skipped. It stays queued and goes out once the dependency recovers, rather than being silently dropped.
Transient failures retry themselves
Network blips and rate limits are retried automatically with backoff, so short interruptions usually resolve without anyone noticing or intervening.
Nothing publishes twice
Every publish is keyed against its schedule, so a retry after a recovery cannot post the same content to a live account a second time.
Genuine failures surface
When a post truly cannot be delivered, it is marked failed with a plain-language reason and, where retrying would help, a retry option — never left to fail quietly.
Scope
What this page does not cover
These checks report on Landio's own services and on whether each integration is configured and reachable from here. They cannot report on the health of the social platforms themselves — if a network's own API is degraded, publishing to it may fail while everything on this page still reads healthy.
A check marked as not configured is not a fault. It means that integration has no credentials on this deployment, which is expected for any provider you haven't set up.