Service status¶
Live status of the CredWatch platform.
Status page¶
- Live dashboard: status.cred-watch.com (coming soon)
- Incident history: same page, scroll down
- Subscribe to updates: email or RSS (links at the top of the status page)
We post on the status page for:
- Portal outages (login, dashboard, findings)
- API outages (
/api/v1/*returning 5xx broadly) - Scanner outages (no scans firing on schedule, or all scans erroring)
- Email/alert delivery outages
- Planned maintenance (announced ≥24h ahead)
We don't post on the status page for:
- Individual customer issues (use bug reports)
- GitHub or third-party API outages affecting individual scans (those show up as errored scans for the duration)
Checking yourself¶
If you're seeing odd behaviour and want to check before emailing us:
| Symptom | Quick check |
|---|---|
| Portal won't load | Visit /health. HTTP 200 = platform up. 503 = DB or Redis down. |
| API returning 5xx | Same /health check. |
| Scans aren't firing | Check Scans page — is the "Next scan ETA" sensible? If "scheduler not responding" badge shows, that's our problem. |
| Alerts not arriving | Check Profile → Alert emails — is your address still listed? Check spam folder for the first time. |
| Specific finding missing remediation card | This is per-pattern. Email us — likely a pattern we haven't added playbooks for yet. |
Incident response¶
When we hit a real incident:
- Status page goes red within 5–10 minutes of detection.
- Active subscribers get an email.
- We post updates every 30 minutes (or when state changes).
- After resolution, a post-mortem is published on the status page within 5 business days for any S1/S2 incident.
Past major incidents¶
(This section will populate as the service operates. We commit to leaving incident history visible permanently — no "scrubbing" of past outages.)
SLAs¶
| Plan | Uptime target | Alert delivery SLA | Support response |
|---|---|---|---|
| Free | best-effort | best-effort | community (no guaranteed response) |
| Starter | 99.5% | best-effort | 48h business response |
| Growth | 99.9% | best-effort | 48h business response |
| Enterprise | 99.95% contractual | contractual SLA | dedicated CSM + contractual SLA |
Uptime is measured as portal + API + scheduler aliveness over a rolling 30-day window. Planned maintenance windows (announced ≥24h ahead) don't count against the budget.
If you can't reach the status page itself (DNS or routing issue our side), the next-best signal is whether app.cred-watch.com is reachable. If both are down, email [email protected] — we'll respond from a separate mail relay.