System Status
Real-time health of SyndTrack and the services it depends on.
All systems operational
Every upstream dependency responded within the expected latency window.
Last checked 2026-09-13T20:01:57.746Z · refreshes every 30 seconds
| Dependency | Status | Latency |
|---|---|---|
Application Next.js server rendering and API routes | Operational | 581 ms |
Database (Supabase) Primary data store for deals, funds, and documents | Operational | 561 ms |
Payments (Stripe) Subscription billing and checkout | Operational | 289 ms |
Email (Resend) Transactional alerts and portal notifications | Operational | 218 ms |
AI (Anthropic Claude) Document parsing and deal scoring | Operational | 514 ms |
Rate limiting (Upstash) Distributed rate limits, idempotency, and webhook dedup | Operational | 177 ms |
Database schema Tables and columns the application depends on | Operational | 531 ms |
Config sanity Production launch configuration | Operational | 0 ms |
Error reporting Sentry capture for backend and frontend errors | Operational | 0 ms |
Scheduled jobs Reminders, digests, and nightly maintenance | Operational | 582 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.