Status API

The data behind status.aperturesyndicate.com. Anonymous. Useful for a status badge in your app, or to tell your users "it's not us" when one of our services is down.

text

Base URL   https://status.aperturesyndicate.com/api

Method	Endpoint
`GET`	`/status`	Every service right now, incidents, maintenance, summary
`GET`	`/status/history?service=<id>&hours=24`	One service's timeline; `hours` is `24`, `72` or `168`

Live status

json

{
  "live": [{
    "serviceId": "as-resonance-api",
    "name": "Resonance API",
    "plane": "core",
    "publicUrl": "https://resonance-api.aperturesyndicate.com",
    "status": "up",
    "latencyMs": 145,
    "checkedAt": "2026-10-29T08:24:09.380Z",
    "external": { "status": "up", "latencyMs": 166, "checkedAt": "…" }
  }],
  "incidents": [],
  "maintenance": [],
  "summary": { "total": 22, "upCount": 22, "degradedCount": 0, "downCount": 0, "avgLatencyMs": 162, "checkedAt": "…" }
}

status is up, degraded or down.

status is measured from inside our network; external is the same service probed from outside, as a user reaches it. When they disagree, the outside view is the one your users feel.

The service ids for the APIs on these pages: as-auth (sign-in), as-ai (ASAI), as-resonance-api (catalogue), as-synx (registry).

History

bash

curl "https://status.aperturesyndicate.com/api/status/history?service=as-auth&hours=24"

json

{
  "serviceId": "as-auth",
  "name": "Sign In & Accounts",
  "hours": 24,
  "bucketMinutes": 15,
  "buckets": [{ "bucket": "2026-10-28T08:15:00.000Z", "avgLatency": 237, "peakLatency": 237, "status": "up", "samples": 1 }]
}

Buckets are 15 minutes for 24 hours, 30 for 72, 60 for 168; latencies are in milliseconds. An unknown service answers 400 with {"error":"unknown_service"}.

BackSYNX registry