SLA monitoring
When a vendor breaks their SLA, have the receipts.
Independent, time-stamped uptime evidence for every cloud and SaaS provider in your stack. Pingoru watches 6,116+ official status pages so when an outage hits, you have the four facts every service-credit claim asks for: when it started, when it ended, what was affected, and how long it lasted.
Free forever for 5 monitors. No credit card.
Vendor SLAs are easy to write. Hard to enforce.
The vendor controls the record.
Status-page incidents can be edited, downgraded, or deleted after the fact. By the time you're filing a credit claim, the original timeline may have softened.
Credit windows expire fast.
Most enterprise SLAs require credit claims within 30-90 days of the breach. Without an independent record, last quarter's outages quietly fall off the table.
Multi-vendor stacks are opaque.
When AWS, Stripe, and your CDN all had a bad week, which one cost you the most? Without per-vendor history, you can't make a case to any of them.
The receipts
Every incident, captured the moment it's posted.
Pingoru polls every status page every 5 minutes. The instant a vendor opens an incident, we capture start time, components affected, severity, and the running update thread. When the vendor marks it resolved, the duration is locked in — and the record is yours to keep.
- Time-stamped at our infrastructure — independent of the vendor
- Permanent shareable link to every incident, ready to paste into a ticket
- 12 months of history on Premium ($15/mo) — covers quarterly and annual SLA windows
- Per-component drill-down so you can prove a region-specific outage
Who uses SLA monitoring?
Procurement & Vendor Management
Show up to renewal negotiations with twelve months of incident data per vendor. Real downtime numbers shift the conversation from list-price to value-delivered.
Engineering Leadership
Your internal SLOs are only as good as the vendor SLAs underneath them. Track upstream breaches in the same dashboard so a 99.9% endpoint goal isn't undermined by a 99.5% dependency.
Customer Success & Support
When a customer escalation traces back to a vendor outage, the timeline is already in your hands. No scramble to screenshot the status page after the vendor has revised it.
FinOps & Compliance
Service credits add up across a multi-vendor stack — the average enterprise leaves $20-50k on the table each year by missing claim windows. Treat every breach as a recoverable line item.
How it works
- 1
Add the vendors in your stack.
Pick from 6,116+ providers. Filter to specific components if you only depend on, say, EC2 us-east-1 or Stripe Checkout.
- 2
Pingoru watches every status page, every 5 minutes.
The official status page is the source. We capture every incident as it's posted, with full update history and component-level detail.
- 3
Get notified the moment a breach starts.
Email, Slack, Discord, Teams, or webhook. Knowing about the outage in 5 minutes — not 5 hours later from a customer escalation — is itself worth the price.
- 4
Pull the receipts when you need them.
Per-incident permalinks with start, end, duration, and component breakdown. Paste into a service-credit form, a vendor support ticket, or a quarterly review deck.
SLA monitoring FAQ
- What is SLA monitoring?
- SLA (Service-Level Agreement) monitoring is the practice of independently tracking whether your cloud and SaaS vendors are actually meeting the uptime promises in their contracts. Rather than relying on the vendor's own dashboards (which can be revised after the fact), Pingoru captures every incident the moment it's posted on the official status page — start time, duration, components affected, severity — and archives it for a year so you have third-party evidence when an SLA breach happens.
- How does Pingoru help me claim service credits?
- Most vendor SLAs include service credits — but you have to prove the breach. Pingoru is the receipt: every incident is captured from the official status page within minutes, time-stamped at our infrastructure, and kept for 12 months on Premium. When a major outage happens you can pull up the exact start time, resolved time, total duration, and which components were affected — the four facts every credit-request form asks for.
- Can I track SLAs across multiple vendors at once?
- Yes. Add a monitor for every vendor in your stack — AWS, Cloudflare, Stripe, OpenAI, GitHub, Datadog, Snowflake, whatever you depend on. Each one is tracked independently with its own incident history, so you can spot which vendors are repeat offenders against their SLA and which ones genuinely deliver four-nines.
- How fast does Pingoru detect a breach?
- Pingoru polls every status page every 5 minutes, so a typical incident hits your inbox 5-10 minutes after the vendor posts it — often before your customers notice. The incident timeline is built up live as the vendor adds updates, so by the time the resolved-at marker lands you already have the full record.
- How much history do I get for SLA evidence?
- 30 days on Free, 12 months on Premium ($15/month). 12 months matters: most enterprise SLAs are quarterly or annual, and credit-claim windows often expire 30-90 days after the breach. Having a year of evidence on hand means you never miss a window.
- Can I export incident records?
- Every incident page is permanent and shareable — link to it from your support ticket or paste the URL into a credit-claim email. Each incident has the started_at, resolved_at, duration, component, severity, and full update timeline that vendors typically request.
- Does this replace internal uptime monitoring?
- No — it complements it. Internal tools (Pingdom, UptimeRobot) watch *your* endpoints. Pingoru watches the vendors *behind* your endpoints. Pair them: when your endpoint dies and a vendor SLA broke at the same minute, you have proof the failure cascaded from upstream.
- Is there a free plan?
- Yes — Free forever for 5 monitors, 30 days of incident history, and email + webhook alerts. Premium ($15/month) lifts those to 50 monitors, 12 months of history, and every integration. Most teams start with Free to spot-check key vendors and upgrade when they realize they're claiming credits more often than expected.
Stop guessing about vendor uptime.
Get the receipts. Free forever for 5 monitors — upgrade to 12 months of history when you're ready to start claiming credits.