Api Isw Status

ISW status with Redis cache (45s) + last-known-good fallback.

2026-07-05: under nightly cron pool-exhaustion the bounded fetch times out and we serve LKG instead of 500/504 (the false-down this fix targets). ISW updates only 13-19 UTC, so 45s staleness / day-old LKG is safe. Monitor (UptimeRobot) hits the 45s cache almost always -> never touches the DB pool.

get/api/v2/isw/status

Request

  • Base URL: https://orcalayer.com (the document declares no server; this is the origin it was published from)
  • URL: https://orcalayer.com/api/v2/isw/status
  • Auth: none declared

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.