Website monitoring for developers and ops teams
Uptime monitoring, alerts
and status pages
Pingara checks your site around the clock from outside your network, alerts you by email, Slack or Teams, and publishes a status page your customers can read. Free for one site.
Overall uptime
99.81%
Last 24 hours
Apdex score
0.93
Good
Active incidents
3
Currently investigating
Response time
1h 10m
MTTA 8m 41s
5 of 7 acknowledged
| Name | Status | Response 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 | - |
Blind spots
Catch the outages
your own browser hides
It has your site cached and its address already looked up, so you're the person least likely to see it break. Pingara checks from outside your network.
How to set up your first monitorIt 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.
Detection
Uptime checks that
confirm before they alert
A monitor changes status only after repeated failures, and on Pro only when enough regions agree.
| Name | Status | Response time |
|---|---|---|
| Checkout ServiceHTTP | Down | 5000 ms |
| Session StoreTCP | Degraded | 8 ms |
| Edge Gateway (Singapore)Ping | Unknown | 61 ms |
Confirm failures before any alert
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.Choose where checks run
Checks run from any of four regions:
- US East (N. Virginia)
- US West (Oregon)
- Europe (Ireland)
- Asia Pacific (Singapore)
Mark it unknown, not down
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.
Alerting
Send alerts to the
tools you already use
Email, Slack, Discord, Microsoft Teams, PagerDuty or a webhook, chosen per monitor. Set nothing up and you still get an email by default.
Incident started
Nov 3, 2026 11:29:21
Alert sent via email to 4 recipients
Nov 3, 2026 11:29:21
Alert sent via PagerDuty
Nov 3, 2026 11:29:26
Alert delivery via slack failed: webhook returned 404
Nov 3, 2026 11:29:29
Acknowledged byPRPriya Raman
Nov 3, 2026 11:33:33
Status changed to IdentifiedbyPRPriya Raman
Nov 3, 2026 11:33:51
AI incident report generatedbyPRPriya Raman
Nov 3, 2026 11:36:01
Choose alert types per monitor
Choose what you hear about and which channels get each one, per monitor. That covers a monitor going down, coming back, slowing down, or being paused.Get an email by default
Configure nothing at all and you still get an email. The fallback is on by default, and you have to switch it off yourself before a monitor can fail quietly.Test alerts before you need them
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.
Status pages
Publish a status page
your customers can read
Group monitors into sections like API and Web, and each section shows one status. Visitors can subscribe by email, and a page can be private.
Example Corp Status
Live availability for the Example Corp storefront and API.
Storefront Web
620ms99.83%Operational
90 days agoYesterday
Storefront
OperationalStorefront API
128ms99.98%Operational
90 days agoYesterday
Asset CDN
22ms99.98%Operational
90 days agoYesterday
Checkout
OutageCheckout Service
5000ms99.97%Outage
90 days agoYesterday
Session Store
1904ms99.98%Degraded
90 days agoYesterday
Global Infrastructure
OperationalEdge Gateway (Singapore)
61ms99.94%Operational
90 days agoYesterday
Incident History
November 3, 2026
27 minutes agoDuration: 26m
about 3 hours agoDuration: 3h 12m
November 1, 2026
2 days agoDuration: 38mResolved
October 23, 2026
11 days agoDuration: 3h 47mResolved
October 16, 2026
18 days agoDuration: 12mResolved
Group monitors into sections
Group your monitors into named sections (API, Web, Infrastructure, whatever makes sense to your customers) and each section shows one status, the worst of its members. Nobody has to parse fifteen individual rows to know if checkout is having a bad day.Show availability history
Daily-rollup availability history per monitor, right on the page. No separate report to pull.Let visitors subscribe, or go private
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.
Beyond uptime
Latency history, Apdex
and an API when you want them
None of this is in your way on day one, and all of it is there when you need it.
Browse the knowledge baseLatency overview
p50, p95, and p99 response times (ms)
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 REST API, with write access on Pro
Read monitors, checks, incidents and public status over authenticated REST on any plan. Pro keys can also write: create, change and pause monitors, and acknowledge incidents. Two API keys on Free, more on Pro.
Pricing
Start free.
Pro is $9 a month.
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.
Compare every limitFree
$0per month
- 1 monitor
- 5-minute check interval
- 7-day data retention
- 1 region
Pro
$9per month
- 50 monitors
- 30-second check interval
- 365-day data retention
- All 4 regions
Get started
Start monitoring
your first site
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.