Skip to main content
Pingara.
Uptime monitoring, free for one site — no credit card

Monitoring for the site you just shipped.

Nothing else is watching it. Pingara checks your site around the clock and tells you when it stops answering.

Start monitoring freeOpen the live demo

You are the worst possible monitor of your own site.

Your browser has your site cached, its DNS already resolved, a session cookie set, and possibly a service worker handing you a version of your app that no new visitor will ever get. When you check your own site, you are the one person on the internet most likely to see it working.

  • It works for you and fails for everyone else

    A connection ceiling, a pool that never drains, a request quota you only hit under load. One visitor is fine. Twenty at once is not.

  • A page that says OK while it's broken

    An error boundary rendering at 200. A shell that loads while the API behind it fails. Nothing about the status code says your product works.

  • Your DNS is the last to know

    A record deleted, a domain lapsed, a registrar change half-applied. Your own resolver has the old answer cached, so you keep loading the site while nobody else can.

  • Fine here, broken from somewhere else

    A routing change, a firewall rule, a provider incident in one region. Your connection is healthy. Your customers' isn't.

The outages that cost the most are the ones nobody reports. A signup form that breaks doesn't generate a support ticket. It loses the person who was about to become a customer, quietly, and they don't come back to tell you.

And certificates expire on a schedule nobody remembers. Pingara sends expiry warnings 30, 14 and 7 days ahead, on every plan including the free one. That warning is a notification and nothing more. It never opens an incident or pages anyone.

How to set up your first monitor →

This is the real dashboard, not a mockup.

Everything below renders with the same code your dashboard runs once you sign up — the monitor list, the latency chart, the incident timeline, and the public status page your customers would see. It's pointed at a fixed sample instead of a live account.

Nine monitors, three open incidents, one region gone dark.

Overall Uptime
99.78%
Last 24 hours
Apdex Score
0.93
Good
Active Incidents
3
Currently investigating
Response Time
1h 10m

MTTA 8m 41s

5 of 7 acknowledged

NameStatusResponse Time
Storefront APIHTTP
up
128 ms
Checkout ServiceHTTP
down
5000 ms
Session StoreTCP
degraded
8 ms
Storefront WebHTTP
up
620 ms
Asset CDNHTTP
up
22 ms
Edge Gateway (Singapore)Ping
unknown
61 ms
Staging APIHTTP
degraded
210 ms
Dev SandboxPing
paused
-
Recommendations APIHTTP
pending
-
Sample data. Open the full demo →What each panel means →

An alert you don't believe is worse than no alert.

The first time a tool wakes you at 3am for something that was never broken, you start ignoring it. Then the one that matters arrives to someone who has already stopped looking.

So Pingara never changes a monitor's status on one bad request. A region has to fail twice in a row before it votes at all. On Pro, where a monitor runs in more than one region, enough of those regions have to independently agree before anything reaches you — so one flaky network path between us and you can't page you on its own.

Checks run from four regions:

  • US East (N. Virginia)
  • US West (Oregon)
  • Europe (Ireland)
  • Asia Pacific (Singapore)

If every region assigned to a monitor goes dark at once, Pingara doesn't guess. It marks the monitor unknown and tells you plainly: this is our infrastructure problem, not a signal that your site is down.

Told where you'll actually see it.

  • Email
  • Slack
  • Discord
  • Microsoft Teams
  • PagerDuty
  • Webhook

Choose what you hear about — a monitor going down, coming back, slowing down, or being paused — and which channels get each one, per monitor.

Set nothing up at all and you still get an email. There is no configuration mistake that ends with nobody being told.

And you can prove it works before you need it. Fire a test incident from the dashboard and watch it arrive on the device you'll actually be holding.

A status page your customers can actually read.

Group your monitors into named sections (API, Web, Infrastructure, whatever makes sense to your customers) and each section shows one worst-of-its-members status chip. Nobody has to parse fifteen individual rows to know if checkout is having a bad day.

Daily-rollup availability history per monitor, right on the page. No separate report to pull.

Visitors subscribe by email with double opt-in, so no address gets incident notifications it didn't confirm. Need a page for internal use only? Make it private and it sits behind your team's login instead of the open internet.

Example Corp Status

Live availability for the Example Corp storefront and API.

Storefront Web
99.83%Operational
90 days agoYesterday

Storefront

Operational
Storefront API
99.98%Operational
90 days agoYesterday
Asset CDN
99.98%Operational
90 days agoYesterday

Checkout

Outage
Checkout Service
99.97%Outage
90 days agoYesterday
Session Store
99.98%Degraded
90 days agoYesterday

Global Infrastructure

Operational
Edge Gateway (Singapore)
99.94%Operational
90 days agoYesterday

Open both demos and you'll spot one monitor reading "Unknown" on the dashboard but "Operational" here. That's deliberate. Your status page shows visitors the last confirmed result for your service — our own infrastructure having a bad five minutes is our problem to explain to you, not yours to explain to them.

Incident History

August 27, 2026

identifiedCheckout Service(status_code)
27 minutes agoDuration: 26m
investigatingSession Store(performance_degradation)
about 3 hours agoDuration: 3h 12m

August 25, 2026

resolvedStorefront API(timeout)
2 days agoDuration: 38mResolved

August 16, 2026

resolvedStorefront Web(tls_error)
11 days agoDuration: 3h 47mResolved

August 9, 2026

resolvedStorefront API(dns_failure)
18 days agoDuration: 12mResolved

Sample data — the same public status-page components your customers would see.

When you want to go deeper.

None of this is in your way on day one, and all of it is there when you need it.

  • Latency history that outlives the data it came from

    Response time is recorded on every check and rolled up hourly and daily as p50, p95 and p99. Raw results age out on your plan's retention window. The rollups don't, so your history keeps going after the checks behind it are gone.

  • A score for whether it feels fast

    Apdex turns raw response times into one number between 0 and 1 by scoring each check against a threshold you set per monitor: fast enough, tolerable, or too slow. It's there to tell you the story afterwards. What actually pages you is a latency rule, confirmed the same way down and up are.

  • Escalation that knows when to stop (Pro)

    Set how long an incident can sit unacknowledged before the next notice goes out, how often to repeat, and a cap on total notices. It stops the moment someone acknowledges, the incident resolves, the monitor is paused, or a maintenance window is suppressing alerts.

  • A read-only API

    Monitors, checks, incidents and public status, over authenticated REST. Two API keys on Free, more on Pro.

Latency Overview
p50, p95, and p99 response times (ms)
Browse the knowledge base →

Start free. The paid plan is $9.

The free tier isn't a trial. It's free for as long as you want it, for one monitor in one region. Pro is a flat $9 a month for up to 50 monitors, all four regions with quorum, checks as fast as 30 seconds, escalation chains, and a year of history instead of a week.

Free

$0

per month

  • 1 monitor
  • 5-minute check interval
  • 7-day data retention
  • 1 region

Pro

$9

per month

  • 50 monitors
  • 30-second check interval
  • 365-day data retention
  • All 4 regions
Compare every limit →

Point it at one URL and see what it says.

No credit card, no sales call, no trial clock. Add one URL and Pingara starts checking it immediately. Stay on the free tier forever with one monitor in one region, or move to Pro for $9 a month for more monitors, more regions with quorum, and escalation.

Start monitoring free