A healthy status confirms only that selected hosted components responded during recorded checks. Configure an independent provider against /api/uptime for out-of-band monitoring; regional routing and untested dependencies may still hide an outage.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
Observed availability
Current checks, 30-day success rates, latency and incident evidence for the hosted service.
Current status
| Component | Checks | Success | Average | Slowest | Last success |
|---|
Checks run on page refresh and, at most every five minutes, during public site traffic.
| Time | Component | Release | Source |
|---|---|---|---|
| No failed checks were recorded in the current 30-day window. | |||
| Date | Component | Checks | Successful |
|---|
Independent monitoring
Configure an independent uptime provider to request /api/uptime. It returns HTTP 200 only when the application and database respond, and HTTP 503 when the deep check fails.
The endpoint is ready for an external monitor. No third-party monitoring account is connected by this website.