Web application
The application is reachable, but one or more local health checks failed.
Source: /api/health
A public launch-readiness surface backed by the same local health/config checks used by uptime probes. External status hosting remains an operational setup step.
One or more local health checks are failing.
Last local check
Apr 27, 2026, 8:11 AM UTC
Build
dbd93e61bd99297c2b10622255d8f5d26ae6acc0
Status routing
/status is the local fallback while status.midas-edge.com is still pending setup.
The application is reachable, but one or more local health checks failed.
Source: /api/health
The public health endpoint is reachable but reporting degraded local checks.
Source: /api/health
Healthy in 85 ms.
Source: Supabase connectivity probe
Plaid client configuration is present for brokerage linking.
Source: Central env configuration
Vertex AI production configuration or non-production direct Gemini fallback is incomplete.
Source: Central env configuration (Vertex AI production path; direct Gemini only outside production)
Stripe server or webhook configuration is incomplete; billing is not launch-ready.
Source: Central env configuration
QStash dispatch and signature verification configuration is present.
Source: Central env configuration
This checklist separates the app-owned fallback that is live now from external provider, DNS, and subscriber-notification work that still needs operational setup.
/status renders app-owned health and launch-readiness checks while external hosting is pending.
The global footer and security page direct users to the local status surface.
Provision probes with the existing uptime setup workflow after provider credentials and alert contacts are configured.
To make this surface available at status.midas-edge.com, configure the external status provider and DNS target described in the external uptime runbook. The component list above tracks local launch-readiness checks; provider monitor data appears after that external system exists.
Point the subdomain at the chosen status provider after the external page exists.
Enable public incident subscription channels in the external provider before launch.
Map monitors to provider components and require two consecutive failed checks before opening an incident.