Outside-in checks
Monitored from vantages that fail independently of your stack — real outside signal, not a self-report.
Reliability Early access
Check your endpoints on the interval you choose from independent vantage points, with per-phase timing that tells you where the slowness actually is.
— Thomas' attractor · a chaotic flow · drag to spin
How it works
Define a monitor — URL, interval, what a healthy response looks like. We run it from vantage points that fail independently of your stack, and record per-phase timing, so an outage or a slowdown is caught from the outside, the way your users see it.
What you get
Monitored from vantages that fail independently of your stack — real outside signal, not a self-report.
See exactly which phase — DNS, connect, TLS, time-to-first-byte — got slow.
A failing monitor can open an incident and page — Uptime and On-Call share one spine.
Reuse the same checks as components on a public status page.
Pricing
Priced per monitor by check interval, times the number of vantages — tighter checks and more vantages cost a little more. Free during early access.
Metered, and free while we open it up.
Part of the Reliability family — see the whole suite.
See how Longbridge pricesPart of the platform
Every Longbridge product shares one Org, one Console, and one bill — so adding the next one is a toggle, not another vendor to onboard.
See the whole platformTry it
lbr uptime monitors create \
--url https://api.acme.com/health \
--interval 60s --vantages 3 The honest part
Start in the Console — or read the docs first. It's your call.