Real-time uptime monitoring + what we measure + how to be notified of incidents.
All systems operational
This page is updated manually by the founder when an incident is in progress. No automated status dashboard is currently in production. The list below shows the systems we monitor on our side via the worker /health endpoint + vendor dashboards; their state shown is the most-recent founder check (refreshed when an incident is reported or detected).
What we monitor
Website (wheretoemigrate.io)
HTTPS · 5 min interval · global
Up
Main API worker (wte-report)
/health endpoint · 5 min interval
Up
Quiz + checkout
/assess pageload · 15 min interval
Up
PDF generation (html2pdf)
third-party · monitored via /health
Up
Email delivery (Resend + Brevo)
vendor status page
Up
Database (DigitalOcean Postgres)
private endpoint · DO status page
Up
This page is updated manually. A live machine-checked status page is on the roadmap but not yet operational — or query https://wte-report.a-mira.workers.dev/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.