Real-time health of every customer-facing HalalCrypto service. This page fetches a runtime snapshot first, then uses scheduled status history as fallback context. 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
Halal trading bot — heartbeat freshness (origin hidden)
Latest probe — Probe pending first run
Bot orchestrator
Meta-agent orchestrator — heartbeat freshness (origin hidden)
Latest probe — Probe pending first run
NowPayments webhook
Inbound NowPayments webhook receipt freshness
Latest probe — Probe pending first run
Halal screener API
Public halal-screener endpoint availability
Latest probe — Probe pending first run
Checkout & billing
Subscription checkout flow availability
Latest probe — Probe pending first run
No deploy history captured yet. The status probe will list the latest production deploy workflow runs here after the next scheduled snapshot.
No incidents in the last 90days. We'll log every incident here — including resolved ones — for full transparency.
gethalalcrypto.com/ — body must return 200 with non-empty content. Latency over 2 s flags as degraded./api/health — must return 200 with { "ok": true }./api/heartbeat/bot — when the bot is wired, it pushes a signed heartbeat. A missing first check-in is shown as telemetry pending; a previously wired heartbeat that goes stale flags as outage. The bot's origin is intentionally not published here./api/heartbeat/orchestrator — same signed-heartbeat pattern. Missing first check-in is telemetry pending; stale configured heartbeats still flag outage. Origin not published./api/screener/health — must return 200./checkout — must return 200. Failures here block new customer acquisition, so this probe pages on-call immediately.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 /api/status/snapshot on this page load. If the runtime snapshot is unavailable, the page falls back to /status.json history written by the scheduled status workflow.