Cross-provider incidents dashboard
See every active and recent incident across 6,116+ cloud and SaaS providers in one timeline. Down to the specific service, with the full story, severity, and duration — scan all your providers in 30 seconds.
5 monitors free forever · No credit card
Real incidents from GitHub, AWS, Stripe, Cloudflare, and OpenAI. All five of these landed in the Pingoru feed within 5 minutes of the vendor publishing them.
One feed, every provider
Mixing vendor status pages is tedious. Pingoru normalises GitHub, AWS, Stripe, Cloudflare, Azure, Google Cloud, Datadog, and the long tail of SaaS status pages into a single chronological feed. Filter by severity, provider, or component.
Per-incident update timeline
Every vendor update — "investigating", "identified", "monitoring", "resolved" — captured with its timestamp and narrative body. See the full post-mortem thread without hunting through status-page history.
Component-level links
"Elevated errors on EC2 us-east-1" is useful — "Elevated errors on the component you subscribed to" is actionable. Each incident carries the list of affected components so you can answer "does this hit me?" in one glance.
Active + historical
The incidents view toggles between Active (still open), Recent (past 30 days), and History (full archive). Export any window as JSON or CSV for SLA reports, postmortems, or vendor evaluations.
Alerts that match
Every incident row is hooked into the same notification pipeline as your monitors. Email, Slack, Discord, or webhook — you see the incident here, and your team sees it everywhere you've told us to tell them.
Five-minute checks
We check every provider every five minutes. The first check after a vendor marks an incident open is the first time the incident appears in your feed — typically a few minutes ahead of user-report-driven tools.
Drill in on any incident
Click any row and the full update stream expands — every status transition (investigating → identified → monitoring → resolved), every narrative update, every timestamp, attached to the exact components the vendor flagged as affected.
Each entry is stored with its own timestamp and content hash, so in-place edits by the vendor land as new timeline entries instead of silently overwriting the earlier narrative.
Frequently asked
How is the Pingoru incidents view different from reading status pages directly?
Status pages are vendor-scoped and paginated separately. Ours is cross-provider — you see GitHub, AWS, Stripe, Cloudflare, and every other vendor in your stack in one feed, sorted by recency. You can filter to just the providers you monitor, or just the ones with active incidents, or just a specific severity.
Do you capture the full update timeline per incident?
Yes — every status update the vendor posts lands as a timeline entry with its timestamp, severity, and narrative body. Re-edits to existing updates are captured as new timeline entries so you see the full sequence, not just the latest version.
What does 'service-level detail' mean?
Most vendor status pages break themselves down into specific services — 'EC2 us-east-1', 'Stripe Checkout', 'Slack Huddles'. Our incidents view links each incident to the exact services it affects, so you can answer 'does this affect me?' without reading the whole story.
How fast does an incident appear?
Within one 5-minute check cycle of the vendor posting it. For most SaaS vendors we pick up the incident the moment it's published and have it in your feed before most monitoring tools have noticed.
Can I export or archive the incident history?
Yes — per-provider JSON and CSV export is available today. Useful for SLA reports, postmortems, and vendor evaluations when renegotiating contracts.
Stop finding out from your users.
One dashboard for every cloud and SaaS provider your stack depends on. Free forever for 5 monitors.
Start monitoring free →