OpenPingGet early access

Everything your product depends on, watched from outside.

Including the parts that fail quietly: a lost tool, a fallback model, worse answers.

What it watches

How a failure is confirmed

One failed check is not an outage. When a run fails, two other regions try again at once. It is Down only when two of the three fail.

The two-of-three ruleA check from Mumbai fails. Frankfurt and Virginia retry at once. If one of them also fails, two of three have failed: the monitor is Down and an alert goes out. If both pass, nothing is sent.1 · A run fails2 · Two regions retry3 · Two of three decideMumbaiFailedFrankfurtFailedVirginiaPassedDown2 of 3 failed.One alert goes out.Had Frankfurt passed too, it would be 1 of 3: no alert, and the blip stays in the history.

Flapping folds into one alert: a monitor that flips more than 4 times in an hour sends one message.

How it behaves

  1. Up and right. Every AI check asks two questions: did it answer, and was the answer right?
  2. Calm alerts. A second region confirms before anyone is alerted, and one cause makes one incident.
  3. Explain everything. Every alert says what failed, where, since when, and what changed just before.

See it on your own product

Paste a URL on the home page. No account needed for the first look.

Planned, not in the first release: browser journeys, private probes in your network, imports and a GitHub app.