Live, point-in-time checks
Current service status
This page checks the hosted Social Fanout API from your browser. It separates application liveness from runtime dependency readiness so a green response says exactly what was measured—and nothing more.
API liveness
Checking…
Waiting for /health.
Confirms that the Social Fanout application process is responding.
Open raw /health response →Runtime readiness
Checking…
Waiting for /health/ready.
Confirms the configured runtime stores and required schema checks are responding. Errors are intentionally sanitized.
Open raw /health/ready response →Not checked yet.
What these checks do not prove
- Provider availability is separate. A social network can be unavailable, rate-limited, or awaiting app approval while the Social Fanout runtime remains ready.
- Account access is separate. Each connection still depends on the permissions and state of that customer-owned social account.
- This is not an uptime percentage or SLA. These are fresh point-in-time checks; this page does not calculate historical availability.
- A successful publish has its own receipt. Use the dashboard or job endpoint to inspect the destination-specific outcome for an individual request.
Something looks wrong?
Send the time, affected endpoint or provider, and a Social Fanout job ID when available. Do not email API keys, OAuth tokens, passwords, or customer content.
Report a service issue