Live uptime from our automated 5-minute monitor + what we measure + how to be notified of incidents.
Checking live status…
Loading live status from our automated monitor…
What we monitor
Website (wheretoemigrate.io)
HTTPS · automated check every 5 min · global
Checking…
Main API worker (wte-report)
/health endpoint (all bindings) · automated check every 5 min
Checking…
PDF generation (html2pdf)
No separate provider result in the public uptime feed
Checking…
Email delivery — Resend
No separate provider result in the public uptime feed; email acceptance does not prove delivery
Checking…
Quiz + checkout
Not independently automated — no dedicated check exists yet; the pageload isn't polled
Not automated
Database (Supabase)
No separate database result in the public uptime feed — see the Supabase status page for provider incidents
Not automated
The rows above marked Checking… / Up / Down are pulled live, client-side, from our self-hosted uptime monitor (a Cloudflare Worker cron that pings the site + API every 5 minutes and writes the result to KV) each time you load this page. Rows marked Not automated are not currently checked by any automated process — that's honest, not a placeholder. You can also query https://api.wheretoemigrate.io/health directly.
How to be notified of incidents
Subscribe to incident emails: send an email to hello@wheretoemigrate.io with subject "Subscribe to incident notifications". We email when an incident is in progress + when it resolves.
Service outages are also posted to our changelog with a category tag incident.
Critical incidents affecting paid customer deliverables (PDF not delivered, payment processed but not fulfilled) are emailed directly to affected buyers.
Recent incidents
Recent incidents documented in our changelog:
2026-05-15 → 2026-05-18 (3 days) — Inbound email routing rules silently disabled at zone level; mail to hello@/privacy@/press@/security@ was dropped. Detected during Trust audit 2026-05-18; fixed same day via API. Founder direct outreach for any inbound during the window not possible (no audit trail before fix).
2026-05-05 — Stripe live API key exposed briefly in chat session during a system audit; rotated within the hour. No customer-data impact.
2026-04 → ongoing pause — Instantly B2B cold campaigns paused after 0-conversion analysis revealed identical-body deliverability issue; not a customer-facing outage. (Logged in /changelog.)
Past incidents
We will log all customer-affecting incidents here with: start time, end time, what happened, what we did, what we changed to prevent recurrence.
Format used for future incident write-ups
Date range, scope (what was affected), root cause, customer impact (if any), what was changed to prevent recurrence. Cross-referenced from /changelog.