Status
The public status route (status_json_url in site/config.json) is not served by the api yet; this page documents the data model the status page renders.
The status page shows whether each platform is working right now and how it has behaved over the last 90 days. It is fed by canaries: a real request to each built endpoint, made through the public API on a schedule, using a known stable example. Endpoints that are stable are checked hourly, beta ones every three hours, and any endpoint that fails is checked again every 15 minutes until it recovers.
A canary failure is classified by whose problem it is: the platform's, ours, a moved example, or a misconfigured canary. Only the first two count as downtime.
The status document#
The page renders one JSON document, available at https://api.socialscrape.io/v1/status. No key is needed and it contains no internal detail: an endpoint id, a state, a time and a latency.
{
"generated_at": "2026-10-29T15:00:00Z",
"overall": "operational",
"last_sweep": { "finished_at": "2026-10-29T14:52:10Z", "ran": 40, "failed": 0 },
"platforms": [
{
"platform": "twitch",
"status": "operational",
"endpoints_total": 5,
"endpoints_failing": 0,
"uptime_pct_90d": null,
"daily": [],
"endpoints": [
{ "id": "twitch.profile", "status": "operational", "checked_at": "2026-10-29T14:51:02Z", "latency_ms": 640 }
]
}
]
}The values in this example are illustrative.
| Field | Meaning |
|---|---|
overall | The worst platform status: operational, degraded, partial_outage, major_outage, or no_data when nothing has been checked yet. |
last_sweep | When the last round of canaries finished, how many ran and how many failed. |
platforms[].status | By the share of that platform's endpoints that are failing: none is operational, under a third degraded, a third to two thirds partial_outage, more major_outage. |
platforms[].uptime_pct_90d | Share of canary runs that succeeded over 90 days; null with no data. |
platforms[].daily | One entry per day with data, oldest first: date and uptime_pct. |
platforms[].endpoints[] | Each checked endpoint: id, status (operational or failing), checked_at and latency_ms. |
The machine-readable definition is status.schema.json.
Incidents#
Outages and degradations that need a human explanation are posted as incidents, kept as a list of records next to the canary data. An incident has a title, an impact (none, minor, major or critical), the platforms it touched, a status that moves from investigating through identified and monitoring to resolved, and a timeline of dated updates. The definition is incidents.schema.json.
No incidents have been recorded.
When something looks wrong#
Check this page first. If your problem is not here, write to [email protected] with the request_id from the response. Errors that say upstream_* mean the platform or our fetching failed and are free; retry them as described in Errors.