Service status
Real-time health of every customer-facing HalalCrypto service. Probes run from independent CI runners every 5 minutes; 90 days of history is shown per service. If something looks wrong here, our team has already seen it.
Status pending
Last probe 0s ago
Live heartbeat · /api/health · 60s cadence · 0 samples
Marketing site
gethalalcrypto.com — landing pages, blog, SEO content
Latest probe — Probe pending first run
API health
Internal /api/health endpoint — liveness for app routes
Latest probe — Probe pending first run
Trading bot worker
Production droplet 165.22.249.146 — ICMP keepalive
Latest probe — Probe pending first run
Checkout & billing
Subscription checkout flow availability
Latest probe — Probe pending first run
Recent deploys
No deploy history captured yet. The status probe will list the latest production deploy workflow runs here after the next scheduled snapshot.
Recent incidents
No incidents in the last 90days. We'll log every incident here — including resolved ones — for full transparency.
What we monitor — and how
- Marketing site HTTP GET against
gethalalcrypto.com/— body must return 200 with non-empty content. Latency over 2 s flags as degraded. - API health HTTP GET against
/api/health— must return 200 with{ "ok": true }. - Trading bot worker ICMP echo to the production droplet (165.22.249.146). Three consecutive failed pings flag an outage.
- Checkout & billing HTTP GET against
/checkout— must return 200. Failures here block new customer acquisition, so this probe pages on-call immediately.
Get notified
Email-only. We'll send one short message when an incident opens and another when it's resolved. No marketing.
Snapshot data is fetched live from /status.json on this page load. The probe runner writes that file every 5 minutes via a scheduled GitHub Action.