Know in seconds whether an outage is yours or theirs
Most sites depend on services someone else runs: a payment provider, an email service, a CDN, a login provider, an address lookup, a maps API. When one of them fails, your checkout or signup fails with it — and the first question in the incident is always the same: is it us or them? Every minute spent answering it is a minute not spent on the fix, or on telling customers what is going on.
Pingsured can check those services next to your own, so the answer is on the same dashboard.
Status pages that publish JSON
Many providers run a status page that also offers a machine-readable summary. A JSON check reads it:
| JSONPath | Operator | Value |
|---|---|---|
$.status.indicator | equals | none |
Look for a link labelled API or JSON on the provider's status page; the path depends on the system they use. A check like this turns the provider's own announcement into an alert you receive, instead of a page you have to remember to open.
The endpoints you actually call
A status page is only as good as the provider's honesty and speed. Where the provider has a public endpoint — a health URL, a public API that needs no account, the script your pages load from their CDN — check it directly:
- the status code, with the response time charted alongside;
- for a JSON API, the field that shows it worked;
- for a script or stylesheet you load from their CDN, that it answers
200, from each of the locations your visitors are in.
Why check your providers with Pingsured
- "Us or them" answered in seconds. Your own checks and your providers' side by side, on one timeline.
- Their outage, your alert channel. Email, the app or a webhook into your incident tool — the same way you hear about your own systems.
- From several locations. A provider that fails in one region only is easy to miss from your office.
- A history to point to. The ping's history shows when and from where a provider failed, so a conversation about its reliability can start from data rather than memory.
Limits worth knowing
- Checks send
GETorHEADand cannot log in through a form, so endpoints that need a full sign-in flow are out of reach. A long-lived API key in a request header works. - Only check what a provider makes public, or what your contract allows. Each ping sends one request at the interval you set, identified by its User-Agent.