Skip to main content
Real-time platform status is at status.getsly.ai. Bookmark it — if your integration is failing, check here first before assuming a bug on your side.

​
What the status page shows

  • Component status — API, dashboard, webhooks, settlement rails, KYC providers, sandbox
  • Ongoing incidents — with live updates and estimated time to resolution
  • Scheduled maintenance — planned with 7+ day notice
  • Historical uptime — 90-day rolling per component

​
Subscribe to updates

Three channels:
  • Email — any resolution or new-incident notification
  • Webhook — POST to your URL on status changes (useful for routing to your PagerDuty)
  • Slack — our public Slack app posts to your channel
Configure at status.getsly.ai/subscribe.

​
Uptime targets

ComponentSLA
Core API (/v1/*)99.95%
Dashboard99.9%
Webhooks99.9% for delivery attempts; 99.99% for queue retention
Sandbox99.0% (no SLA, best-effort)
Settlement railsInherits upstream provider SLAs
Enterprise contracts can negotiate higher per-component SLAs.

​
When your integration fails

Quick checklist before escalating:
  1. Check status.getsly.ai — platform incident?
  2. Inspect response request_id — include it in support tickets
  3. Read the code field — is this a known error category? See error codes
  4. Try in sandbox — same request in test environment; reproduces? Integration bug. Doesn’t reproduce? Environment-specific.
  5. Open a ticket — see support

​
Post-incident reports

Every Severity 1 and Severity 2 incident gets a public postmortem within 7 business days. You can read past ones at status.getsly.ai/history.

​
Degraded modes

Sly’s architecture gracefully degrades on certain failures rather than returning 500. Examples:
  • Settlement rail outage → transfers held in processing state, retried when rail recovers. Webhook transfer.delayed fires.
  • Quote provider outage → existing quotes honored; new quotes return 503.
  • KYC provider outage → account creation succeeds; verification deferred with pending status.
  • Dashboard outage → API unaffected. Dashboard is independent.

​
Rail-specific status

Individual settlement rails (USDC on Base, ACH, Pix, SPEI, cards) have separate status indicators. An incident on “ACH” doesn’t imply an incident on “USDC.”