How It Works
Monitoring that shows you the full picture.
Global probes, majority-vote incident detection, full request traces, and status pages that never go down.
Global infrastructure
7 locations, 4 continents
We check your services from probes distributed across the globe. Every probe runs independently, giving you a realistic picture of what your users experience from different regions.
Need EU-only monitoring? We can restrict checks to European probes only.
Active probes
Coming soon
Helsinki · London · Sydney · Mumbai · Johannesburg
Incident detection
Majority-of-probes voting
Every probe that checks your service casts a vote — pass or fail. We take the most recent result from each probe within a configurable lookback window and require a strict majority to change state. A single probe having network issues won't trigger a false alarm.
Your monitor only transitions to "down" when most probes across multiple continents agree something is wrong.
How voting works
Primary check fails from one probe location
All probes cast votes within the lookback window
Strict majority required to change monitor state
Alert fires only on confirmed state transition
Confirmation windows
Configure how long failures must persist before we mark a service as down — and how long recovery must persist before we mark it as back up. A 2-minute confirmation window means probes must report a sustained majority of failures for 2 full minutes before we alert you. Eliminates noise from brief network blips.
Check types
Three protocols. Full coverage.
Check intervals range from 30 seconds to 5 minutes depending on your plan, with configurable timeouts up to 10 seconds.
HTTP
Any method (GET, POST, PUT, etc.), custom headers, request bodies, expected status codes, and redirect following. Check an API health endpoint, verify a webhook returns 200, or confirm your login page loads.
TCP
Connect to any host and port. Optionally send data and verify the response. Works for databases, mail servers, game servers — anything with a TCP port.
DNS
Query specific nameservers for A, AAAA, CNAME, MX, NS, TXT, or SRV records and verify the response matches expected values. Catch DNS misconfigurations before your users do.
Status pages
Static HTML. Zero runtime dependencies.
When you create a status page, you pick which monitors to display and give each one a customer-friendly name. We generate a fully self-contained static HTML page — all CSS inlined, no JavaScript, no external dependencies — and deploy it to a global CDN.
Your status page updates automatically within seconds of a state change.
What each page shows
Why they never go down
Your status page is a static HTML file served from CDN edge nodes worldwide. It has zero runtime dependencies on Larm. There's no JavaScript making API calls, no database queries, no server-side rendering at request time. If our entire platform went offline, your status page would continue serving from the CDN cache exactly as it was last rendered.
Render pipeline
When a monitor changes state, we regenerate the HTML with fresh data — uptime percentages, response times, 90-day history — upload it to CDN storage, and purge the cache. After that, the HTML is a standalone artifact. It doesn't phone home, it doesn't need our servers, it doesn't load external scripts.
Data residency
Probes are global. Data stays in the EU.
Probes run globally to check your services from realistic locations, but all data processing and storage happens in the EU.