The status page aggregator for engineering teams

A tool that watches every vendor's public status page for you and tells you when something breaks. Instead of manually checking status.aws.amazon.com, status.stripe.com, status.cloudflare.com, etc — or trying to set up RSS feeds for each one — an aggregator does the watching for you and funnels everything into one dashboard and one alert stream.

Most vendor status pages publish a machine-readable feed alongside the human-readable page. Pingoru reads those feeds every 5 minutes and compares each response to the previous one to spot what changed. For vendors with custom status pages we read the page directly and translate it using purpose-built code for that vendor.

You can — and some people do — but the RSS approach has three problems: • RSS readers can't filter to specific services, so you get every AWS notification even if you only use EC2 in us-east-1. • RSS feeds drop older items after a few days, and the 'resolved' update often arrives without the original 'opened' update still attached. • There's no cross-vendor timeline view — each feed is its own silo. An aggregator solves all three: per-service filters, full event history, one feed across every vendor.

Pretty much all of them: • The big clouds (AWS, GCP, Azure) — every region, every product, with purpose-built code for each one's specific format. • Big SaaS players with their own feeds — Microsoft 365, Salesforce, Apple, PlayStation, Heroku, and ~30 others. • Thousands of standard SaaS status pages — Stripe, OpenAI, Cloudflare, Slack, Zoom, Datadog, Shopify, and the long tail. • Generic RSS and plain-HTML fallbacks for the rare bespoke page. If a vendor publishes any kind of status page on the public internet, Pingoru probably already watches it.

Yes — any status page we can reach, we can read. Add the URL via the "Request a provider" form and we'll onboard it within 24 hours. Useful for monitoring your own internal tooling or, for parent companies, watching subsidiary brands.

Median 3 minutes, 95th percentile 6 minutes. We check every 5 minutes per provider, and the time between us spotting a change and your alert going out is typically under 30 seconds. We also catch edits made to existing incidents and add them to the timeline, rather than silently overwriting what we had.