AroodMe
Status
Live service health, monitors, and where to reach us when something is broken.
Live health
Our liveness endpoint /api/health returns 200 with a JSON heartbeat whenever the application server is up and serving requests. It deliberately does not touch Supabase or Stripe — those are checked by a protected deep-probe used by our uptime monitors.
If /api/health isn't responding, the public site is down. Email support@aroodme.com and we'll follow up with an incident timeline.
What we monitor
- Landing page (
/) - Owner sign-in (
/login) - Liveness (
/api/health) - Deep health — Supabase + Stripe-key validation behind a header secret
- A pinned live pack page (
/p/<id>)
These probes run on a 1-minute cadence (5 minutes for the deep ones). Alerts route to our on-call channel; investigation usually starts within minutes.
Incident contact
We do not currently publish a streaming status page (Statuspage / Better Stack public). During an incident, the fastest path is:
- Email support@aroodme.com with what you're trying to do.
- Partner restaurants: email partners@aroodme.com for payout or staff-access issues so the right person sees it first.
- Security incidents: security@aroodme.com — two-business-day response window.
A public status page will be linked from here once we have enough live customer traffic to justify the noise. Until then, /api/health is the source of truth.