System Status
Real-time health of SyndTrack and the services it depends on.
Service disruption
At least one dependency is unreachable or failing. Some features may not work until this clears.
Last checked 2026-06-15T08:15:16.041Z · refreshes every 30 seconds
| Dependency | Status | Latency |
|---|---|---|
Application Next.js server rendering and API routes | Operational | 897 ms |
Database (Supabase) Primary data store for deals, funds, and documents | Operational | 853 ms |
Payments (Stripe) Subscription billing and checkout | Operational | 150 ms |
Email (Resend) Transactional alerts and portal notifications | Operational | 170 ms |
AI (Anthropic Claude) Document parsing and deal scoring | Down AI unavailable | 0 ms |
Config sanity Production launch configuration | Down Configuration unavailable | 0 ms |
What these checks mean
Each dependency is probed in parallel with a 3-second per-check timeout. We record the round-trip latency and bucket it into one of three states:
- Operational — responded in under 1.5 seconds.
- Degraded — responded between 1.5 and 3 seconds. Service is up but slow. Thresholds are calibrated for normal Vercel serverless cold- start variance.
- Down — did not respond within 3 seconds, returned a 5xx, or rejected our credentials.
This page is a snapshot from your current region; real users in other regions may see different latencies. For machine-readable output, see /api/status.