Uptime

Live status of every RMS Nordic service. Auto-refreshes every 30 seconds.

Last check: checking…   ·   Refresh now

Production

Development

---

How the check works

Each service is probed with fetch(url, {mode: 'no-cors', cache: 'no-store'}) from your browser. A response (any response, including 4xx or 5xx) marks the service up. A network error, DNS failure, or TLS failure marks it down. The mode: 'no-cors' flag means we don't actually see the response body - we just measure whether the TCP connect + TLS handshake + HTTP turnaround completes.

The latency shown is the time from fetch() start to promise resolution, rounded to whole milliseconds. It includes DNS, TLS handshake, request, and response on the very first check; subsequent checks reuse the connection so they're faster.

This page is client-side only - no server-side polling, no database. Reloading the page restarts the check.