Skip to content

STATUS · PROBED EVERY 5 MIN

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

p50

Marketing site

gethalalcrypto.com — landing pages, blog, SEO content

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

Latest probe — Probe pending first run

API health

Internal /api/health endpoint — liveness for app routes

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

Latest probe — Probe pending first run

Trading bot worker

Halal trading bot — heartbeat freshness (origin hidden)

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

Latest probe — Probe pending first run

Bot orchestrator

Meta-agent orchestrator — heartbeat freshness (origin hidden)

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

Latest probe — Probe pending first run

NowPayments webhook

Inbound NowPayments webhook receipt freshness

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

Latest probe — Probe pending first run

Halal screener API

Public halal-screener endpoint availability

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

Latest probe — Probe pending first run

Checkout & billing

Subscription checkout flow availability

Unknown
24h7d90d100.00%
90 days ago100.000% uptimeToday

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  Heartbeat freshness check against /api/heartbeat/bot — the bot pushes a signed heartbeat every minute. If we don't see one for 5 minutes the service flags as outage. The bot's origin is intentionally not published here.
  • Bot orchestrator  Heartbeat freshness check against /api/heartbeat/orchestrator — same pattern. Origin not published.
  • NowPayments webhook  We track the timestamp of the last successfully-processed NowPayments webhook. If we go more than 24h without one, this probe flags degraded; over 72h flags outage.
  • Halal screener API  HTTP GET against /api/screener/health — must return 200.
  • 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.