Skip to main content
A public status page is coming soon. Until then, this page covers how Sly communicates incidents and where to check for disruption.

​
Where to check during an issue

  1. Dashboard — app.getsly.ai — in-product incident banner, and Settings → Status shows current component health for your tenant.
  2. Email — we notify all tenant admins for Sev 1 and Sev 2 incidents via the address on your account.
  3. Enterprise plans — named CSM + optional dedicated Slack Connect channel for real-time updates.
When the public status page ships (planned alongside v1.0 GA), it’ll live at status.getsly.ai with:
  • Component-level status (API, dashboard, webhooks, settlement rails, KYC providers, sandbox)
  • Live incident updates + estimated time to resolution
  • Scheduled maintenance with 7+ day notice
  • Historical uptime per component
  • Subscribe for email / webhook / Slack notifications

​
Uptime targets

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

​
When your integration fails

Quick checklist before escalating:
  1. Check the dashboard for a tenant-level incident banner
  2. Inspect response request_id — include it in support emails
  3. Read the code field — is this a known category? See error codes
  4. Try in sandbox — same request in test environment. Reproduces? Integration bug. Doesn’t reproduce? Environment-specific.
  5. Email support with the request_id — see support

​
Post-incident reports

Every Sev 1 and Sev 2 incident gets a public postmortem within 7 business days, emailed to all tenant admins and posted to the changelog. Once the public status page is live, it’ll also appear there.

​
Degraded modes

Sly’s architecture gracefully degrades rather than returning 500 where possible:
  • 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 (USDC on Base, ACH, Pix, SPEI, cards) is tracked separately inside the dashboard. An incident on “ACH” doesn’t imply an incident on “USDC.”