Everything Pingoru does, in six screens
Status pages from 8,000+ cloud and SaaS vendors, read every five to ten minutes, turned into one dashboard and one alert stream for the vendors you depend on.
Every vendor you depend on, on one screen
Add AWS, Cloudflare, Stripe and the rest by searching 8,000+ status pages. Each row shows live status, the components you care about and when we last checked.
One timeline when several vendors break at once
Every incident from every vendor you watch, newest first, with the vendor's own updates. The view to keep open during a bad afternoon.
Alerts where your team already works
Email, Slack, Discord, Microsoft Teams, PagerDuty or a signed webhook. Set it up once per notification group and every vendor in the group follows.
Only the components you use
Watch EC2 in us-east-1, not all of AWS. Alerts fire on the parts of a vendor your product touches, and nothing else.
Maintenance on a calendar
Scheduled windows from every vendor you watch on one monthly grid, so deploys and migrations can avoid them.
Ask your AI assistant
Point Claude, Cursor or any MCP client at the public endpoint and ask whether a vendor is down. No key is needed for live status; a Pro key adds your own monitors and alerts. Set it up.
{ "mcpServers": {
"pingoru": { "url": "https://pingoru.io/api/mcp-public/" }
} }Free for 3 vendors. Pro is $5 a month for 50.
Pro adds 10 team seats, a year of incident history, unlimited notifications and the MCP key. No card to start.
Questions
Which features are free?
3 monitors, 1 seat, 10 notifications per month, email alerts, the native Slack app (with the /pingoru slash command), generic signed webhooks, component-level filtering, the maintenance calendar, CSV + JSON exports of the last 30 days, and access to every provider's public page on pingoru.io. Pro ($5/mo) is for teams: 50 monitors, 10 team seats, 1-year incident history (for postmortems and SLA reports), the native Discord integration, an MCP key for your own monitors, unlimited notifications, and priority support.
Do I need to install anything? An agent, SDK, or code change?
No. Pingoru runs entirely in your browser. There's nothing to deploy and no code change to ship. Alerts are sent from our infrastructure to your email or webhook; we have zero access to your stack beyond what's in vendor status pages (which are public).
How up-to-date is the data?
We check each provider's status page every five to ten minutes. For most SaaS vendors we read their public feed directly and translate it into your dashboard view. We've built our own readers for the bigger players that publish in their own format: AWS, Google Cloud, Azure, Microsoft 365, Adobe's five clouds, Salesforce, Google Workspace, Apple, Firebase, PagerDuty, Zendesk, Heroku, GitLab, and Meta. New providers get added automatically as they appear on the public web.
What exactly is a "monitor"?
A monitor is one provider plus an optional service filter, plus your alert preferences. You can point two monitors at the same provider with different filters. For example, one set to EC2 us-east-1 that alerts on anything, and one set to EC2 eu-west-1 that only alerts on major outages.
How are webhooks signed?
Every webhook ships with an `X-Pingoru-Signature-256` header. It's an HMAC-SHA256 of the JSON body, signed with a per-webhook secret we generate when you set it up. Verify it on your end to reject forged requests. The exact header format and a sample verifier in your language of choice are shown in the app when you create a webhook.
Can I use Pingoru for status monitoring of my own product?
No. Pingoru is for watching the providers you depend on (AWS, Stripe, GitHub, OpenAI, and so on), not for publishing your own status page. If publishing your own status page is what you need, there are plenty of tools for that and we're not one of them. Plenty of customers use both: a publish-your-own tool for their own page, and Pingoru to watch the ~30 SaaS tools that page depends on.
Why not just subscribe to each vendor's own email list?
You can. But you'll get one email thread per vendor, different formats, different severity conventions, and no filtering. Pingoru gives you one chronological feed across every provider, sent to whichever destination you want (email, Slack, Discord, Teams, PagerDuty), with filters so minor updates on a vendor you barely use don't drown out the one service that's broken.
What data is exported?
Incident exports include every recorded incident in your monitor set over the chosen date range: provider, monitor, title, impact, status, start time, resolved time, duration, affected components, and every update posted on the incident. CSV is one row per incident (updates as a JSON-encoded column); JSON preserves the nested update thread. Free plan covers the last 30 days; Pro covers the full year.
Is there an API?
Yes. A public REST API needs no key (OpenAPI at pingoru.io/api/agent/openapi-public.json), and the public MCP endpoint lets Claude, Cursor and other assistants read live status. Pro adds an MCP key for your own monitors and alerts, plus signed webhooks and CSV or JSON exports for everything else.