The Observatory is SohoPay’s public status and health dashboard: no login, no API key. Use it to answer “is it me or is it SohoPay?” before you open a debugger, and to feed your own monitoring via the /health and /status endpoints.

System health

Live network activity

Debugging heuristic: if the Observatory is green and your integration is failing, the problem is almost certainly on your side — start with Troubleshooting and the Live Feed. If the Observatory shows an incident, subscribe to updates and wait rather than shipping a “fix”.

Alerts

The Observatory’s alerts panel carries three kinds of notices:
  • Current incidents — open incidents with severity, impact, and timestamped updates until resolution.
  • Scheduled maintenance — the Sunday 02:00–02:30 UTC window and any exceptional maintenance, announced 1 week ahead per the SLA.
  • Deprecations — API versions or fields scheduled for removal, with sunset dates. Check this before pinning SDK versions long-term.

API access: /health and /status

Both endpoints are unauthenticated and safe to wire into your own uptime monitors. GET /health — coarse API liveness:
Response
GET /status — component-level detail, matching what the Observatory renders:
Response
Sandbox equivalents live at https://api-sandbox.sohopay.xyz/v1/health and /status.
Poll at 5–10 second intervals, no faster. These endpoints are unauthenticated but not unmetered — aggressive polling from one IP gets rate-limited like any other traffic. For settlement state of your payments, use webhooks instead of polling /status.

Next steps

Live Feed

Drop from network-level health to individual transactions.

SLA & Disaster Recovery

What the uptime target commits to and what happens during outages.

Troubleshooting

What to check when the Observatory is green but your calls fail.