One dashboard for every cloud and SaaS you depend on
Pingoru watches 6,116+ cloud and SaaS status pages in one unified view — AWS, Google Cloud, Azure, Stripe, Cloudflare, OpenAI, GitHub, Slack, Datadog, and thousands more. Stop hopping between status pages; watch them all in one place.
5 monitors free forever · No credit card
Your monitors list — every vendor you subscribe to, status rollup at a glance, with a link into the component list for each one.
6,116+ providers pre-seeded
Amazon Web ServicesPlus AWS × every region, GCP, Azure × every region, Twilio, Shopify, Zoom, Datadog, Supabase, Heroku, Atlassian, and thousands more in the full directory.
Add vendors by search
Type "stripe", "cloudflare", "us-east-1" — whatever your stack touches. No integration setup, no API keys, no per-vendor configuration. Monitors are live the moment you add them.
Component-level scoping
"AWS" is too broad — most of it isn't relevant to your app. Scope each monitor to the components you actually use: just EC2 us-east-1, just Stripe Checkout, just Slack huddles. Fewer pages, better signal.
Unified severity
Vendors use inconsistent labels — "warning" on one, "partial outage" on another. We normalise to a common severity scale (operational / degraded / partial outage / major outage) so cross-vendor sorting actually makes sense.
Alerts, not surveys
Every monitor is wired to the notifications pipeline: email, Slack, Discord, Teams, webhook. Incidents fire the moment the vendor posts them — median 3 minutes end-to-end.
Incidents + maintenance, one feed
Active outages, resolved incidents, in-progress maintenance, scheduled maintenance — all in one timeline, filterable by vendor, region, or severity. No tab-switching between feeds.
Team seats
Premium includes 10 team seats. Add teammates by email; they land in the same dashboard, with per-user notification preferences for any monitor on the account.
Every outage, every vendor, one feed
Each monitor has its own incident history, but the main incidents view cuts across all of them chronologically. Scan an hour of vendor activity in 10 seconds: which vendor, which service, how long.
Filter by severity to tune out the noise. Filter to a specific provider to get the single-vendor history view.
Looking for the tool-type-first framing? See our status page aggregator page — same product, explained from the "what kind of thing is this" angle rather than the dashboard angle.
Frequently asked
What's a status page aggregator?
A single dashboard that watches every cloud and SaaS vendor's public status page and shows incidents in one feed. Instead of clicking between AWS / Cloudflare / Stripe / GitHub / OpenAI to check who's broken, you watch one screen.
How many providers does Pingoru track?
6,116+ at launch and growing. Every AWS region × service combo, every GCP product, every Azure service (with per-region and per-service detail), plus the long tail of SaaS vendors — Stripe, OpenAI, Cloudflare, Slack, Zoom, Datadog, Shopify, and thousands more.
Can I request a provider that isn't in the catalog?
Yes — every provider page has a 'Request a provider' link. We typically onboard the request within 24 hours if it's a standard status-page format.
How often do you poll?
Every 5 minutes per provider. Median latency from vendor publishing an incident to alert firing on your monitor is ~3 minutes.
Stop tab-hopping between 6,116+ status pages.
Pingoru aggregates them all into one dashboard. Free for 5 monitors. $15/mo for 50.
Create your free account