Cloud uptime monitoring for vendor SLAs
Track uptime for every cloud and SaaS vendor your stack depends on. 90-day rolling history, per-incident duration, CSV / JSON export for SLA reporting, vendor-evaluation conversations, and post-incident reviews.
5 monitors free forever · 90-day history on every plan
One provider, 90 days, at a glance. Every cell is one day tracked against the vendor's own status page.
What cloud uptime monitoring tells you
Cloud vendor marketing says 99.99%. Reality says "it depends on the region, and the last three months have been rough." Cloud uptime monitoring gives you the actual number — derived from the vendor's OWN reported incidents — so your SLA conversations and postmortems cite real data instead of trust.
Pingoru computes uptime per provider (or per region, if you scope your monitor tightly) using the incidents the vendor themselves posted on their public status page. Useful for:
- Vendor renewal negotiations — bring the numbers, not the narratives.
- Postmortems — cross-reference a customer outage with the vendor's own timeline.
- SLA credits — calculate your actual entitlement from the vendor's own admission.
- Architectural decisions — "which region should we deploy to" backed by three months of regional incident history rather than marketing docs.
90-day rolling window
Every provider tracked across a 90-day window on the free tier, 365 days on Premium. Uptime ratio, incident count, and total downtime all computed from the raw incident log.
Per-region uptime
Scope your monitor to a specific region (AWS us-east-1, Azure East US) and the uptime ratio reflects just that slice — directly meaningful to your workload's actual exposure.
CSV + JSON export
Every incident history is exportable as CSV or JSON. Drop it into a spreadsheet for a vendor-renewal deck, or into a reporting pipeline for automated SLA calculations.
Component-level detail
Per-incident, the affected component (EC2 us-east-1, Stripe Checkout, Slack Huddles) is captured — so "EC2 had a bad month" is a real claim you can make, not a global AWS number muddied by an unrelated region.
Fair across vendors
Every vendor's uptime uses the same methodology — minutes in non-operational state ÷ total minutes. Cross-vendor comparisons are apples-to-apples.
Public provider pages
Every one of our 6,116+ providers has
a public uptime page at pingoru.io/providers/<slug>.
Bookmark the ones you care about, share the link in your
vendor-selection docs.
Frequently asked
What's included in cloud uptime monitoring?
Three layers of signal per provider: • Real-time status — is the vendor's status page reporting an incident right now? • Incident history — every past incident with start, resolution, affected components, and duration. • Uptime percentage — rolling 90-day uptime ratio for reporting and vendor evaluation.
How is uptime calculated?
We calculate cloud-provider uptime from the vendor's own reported incidents on their public status page. For each 24-hour window we count the minutes any component was in a non-operational state (degraded / partial outage / major outage) and subtract from 1440. A provider with zero incidents in a day shows 100%; a provider with a 7-hour major outage shows ~70%.
Can I export uptime data for SLA reporting?
Yes — every provider's incident history exports to CSV or JSON via /api/reports/incidents. Includes start time, resolved time, impact, affected components, and narrative. Feed it into a spreadsheet or report generator for vendor-renewal conversations.
What counts as 'downtime' for a multi-region vendor like AWS?
By default we compute uptime at the provider level — any component in any region having an issue contributes to downtime for AWS as a whole. If you care about a specific region (say, just us-east-1), scope your monitor to that region and Pingoru reports uptime for that slice only. Makes the number directly meaningful to your workload.
Do you monitor uptime for my own endpoints too?
No — that's a different category of tool (the kind that pings your own URL every minute to confirm it responds). Pingoru only monitors the vendors you depend on, not your own app. Pair the two for full coverage.
Related: cloud monitoring (real-time incident focus), cloud status monitoring (status-page-first framing), SaaS monitoring (business-apps angle), root cause analysis (incident-triage angle).
The uptime number you can actually cite.
Free forever for 5 monitors. 90-day history included. No credit card.
Start monitoring free →