Pingi watches your websites, APIs and services around the clock. When something breaks, it confirms the failure from a second region before it ever alerts you — then keeps your team informed from the first failure to full recovery.
A simulation of Pingi's real engine: scheduled checks from four regions, a failure threshold, cross-region verification, incident, alerts, confirmed recovery.
The same panel you'll see for every monitor in your workspace — current status, response time, recent checks and where each check ran from.
Illustrative product view — figures shown are for demonstration only.
One workspace for uptime, incidents, alerts and status — built for teams who need to know first.
Check any HTTP or HTTPS endpoint on your own schedule, with custom methods and expected status codes.
A state machine tracks every monitor's health and confirms real outages from a second region before alerting.
Email, Slack, Discord, Telegram, SMS and webhooks — alert the right people the moment something changes.
A branded, public page that shows your real uptime and incident history — nothing fabricated.
Invite your team with owner, admin, member and viewer roles, scoped to your workspace.
A full REST API with scoped tokens, so you can manage monitors and incidents from your own tools.
Every HTTPS monitor's certificate is checked for expiry, validity and hostname match.
Every meaningful action in your workspace is recorded, so you always know what changed.
Nothing is reported until it's confirmed, and nothing is resolved until recovery is confirmed too.
A check fails and crosses your failure threshold.
Confirmed from a second region — never on a single failed check alone.
Your configured channels are alerted the moment it's confirmed.
A passing check starts a recovery verification of its own.
Marked resolved only once recovery is confirmed too.
A clean, branded page that shows exactly what your monitors show internally — real uptime, real incidents, updated automatically.
A full REST API sits behind every screen in Pingi — the dashboard doesn't have any special access the API doesn't.
# List monitors in your workspace curl https://app.pingi.io/api/v1/monitors \ -H "Authorization: Bearer pingi_••••••••••••••••" → 200 OK { "data": [ { "id": "01m3b...rsc", "name": "Checkout API", "status": "ok", "regions": ["fra", "lon"] } ] } $
No certifications to claim — just the concrete measures already built into Pingi.
Every record belongs to one workspace; policies check permissions inside that workspace, never across it.
Targets are resolved once and pinned to that address, so a check can never be redirected to a private network.
Tokens carry explicit abilities and can never exceed the permissions of the person who created them.
Meaningful changes in your workspace are recorded with who did what, and when.
Webhook URLs, tokens and other channel credentials are encrypted at rest and never re-displayed.
Stripe events are verified by signature, replay-guarded, and applied at most once.
Simple, fixed pricing — pick the plan that fits how much you need to watch.
Add your first website, and Pingi starts checking it automatically — no credit card required.
