Most uptime monitors quietly round your reality. They poll every 30 seconds — or every two minutes on a free plan — and then report outages in seconds, giving the illusion of precision. But you cannot report what you never measured. If you check once every 30 seconds, a 4-second outage is either invisible or smeared across a 30-second window.
The 30-second floor is a measurement problem
Instatus, the reference product in this space, floors at 30 seconds on its paid plans and two minutes on Free. That is fine for catching multi-minute outages. It is useless for the failures that actually erode trust: the brief, intermittent blips that your customers notice before your dashboard does.
PingInsight runs true 1-second checks. Every probe is millisecond-stamped, so when something breaks, we can say precisely when it started and when it ended.
Why exact-second timelines matter
- Incident response. A one-second detection loop means alerts fire while the incident is still small, not after it has cascaded.
- SLAs. "Down for 4.2 seconds" is a defensible, auditable number. "Down for about a minute" is a guess that always rounds against you.
- Trust. Showing exact downtime on a public status page signals that you actually measure what you claim.
Keeping it honest with quorum
Polling fast naively means more false positives. PingInsight confirms outages with multi-location quorum — requiring multiple regions or consecutive failures before declaring a monitor DOWN — keeping the false-positive rate under half a percent of declared outages.
If you have been living with the 30-second floor, see how much you have been missing. Start with our uptime monitoring feature page, or jump straight to pricing.