Pingoru in one page

Everything Pingoru does

Cross-provider status aggregation, incident timeline, scheduled maintenance calendar, and routed notifications across 6,000+ providers in one dashboard.

Start monitoring free → See pricing

5 monitors free forever · No credit card

6,000+
Cloud & SaaS providers
AWS, Stripe, GitHub, OpenAI, Slack…
Every 5 min
We check each status page
You hear about outages within minutes
One dashboard
Every outage in one place
No more juggling 20 status-page tabs
Email + Slack
Alerts where you already are
Plus Discord, Teams, PagerDuty, webhook
MCP PRO NEW

Plug Pingoru into your AI assistant

Pro accounts get an MCP (Model Context Protocol) endpoint that plugs into Claude Desktop, Claude Code, Cursor, Cline, Zed, or Goose. Your assistant can ask "is GitHub down?" or "any AWS issues this week?" and get a real answer in under two seconds, across all 6,000+ providers we track plus your own monitors.

  • Read-only by design. Claude can't pause monitors, ack incidents, or change anything through MCP.
  • Nine tools. Provider status, component status, incident history, search, your monitors, your active alerts, and more.
  • 500 calls/month included on Pro · 30/min burst protection per key. Per-account overrides on request for heavier workflows.
  • Works with every MCP client. Copy-paste configs in your dashboard for the popular tools, or BYO with the raw URL plus Bearer token.
Deep dive: Pingoru MCP →
Claude Desktop · Pingoru MCP
you
Slack & Discord NEW

Alerts in the channel where your team already lives

Slack and Discord both work natively. Slack gets a one-click "Add to Slack" install with rich Block Kit alerts plus the /pingoru slash command for ad-hoc status checks. Discord uses paste-the-URL setup (no OAuth needed) and posts rich embed messages with the same status-pill / affected- components shape.

  • Slack: native app, OAuth install, Block Kit messages, /pingoru slash command for typo-tolerant lookups
  • Discord: embed alerts in any channel; just generate a webhook URL in Discord's settings, paste it into Pingoru
  • Free with every account on either platform. Install on as many workspaces and channels as you need.
  • Severity routing. Attach different Slack/Discord channels to different notification groups so #ops-critical only sees major outages.

Slack deep dive → Discord setup →

Pingoru APP 9:51 AM
🟠 OpenAI — Partial Outage
Elevated error rates affecting ChatGPT and API responses
Affected: ChatGPT, API, Dashboard
Started: Today 5:25 PM
View incident Provider page
Embeddable widget NEW

Show your customers what your stack depends on

A live status badge for your site. When your payments processor goes down or your auth provider degrades, visitors see it immediately — and understand the issue is upstream, not your code. Two lines of HTML, free on every plan.

  • Two-line install. A div with your widget id, a script tag, done. Renders in under 200ms after first paint.
  • Pick what shows. Choose which monitors appear in the widget; narrow further to specific components per monitor.
  • Three layouts (Full / Compact / Minimal) and three themes (Auto / Light / Dark). Auto follows the host site's color-scheme.
  • Real backlinks for your stack page. Script-embed renders DOM inside your page; search engines see the rendered status info as part of your content.
Widget deep dive →

Sub-processor status

! Partial outage in progress
  • Amazon Web Services
    3 active incidents
    Partial outage
  • Cloudflare
    1 active incident
    Partial outage
  • Stripe
    Up
  • Anthropic
    1 active incident
    Up
  • GitHub
    Up
Status data by Pingoru →
Catalog

6,000+ providers, auto-updated

Every AWS region. Every Azure region. Every GCP product. Microsoft 365 per-service. Adobe's five clouds. Plus thousands of SaaS vendors: Stripe, OpenAI, GitHub, Cloudflare, Zoom, HubSpot, Okta, Twilio, Sendgrid, the works. Add one in two clicks. No setup.

  • The big clouds covered properly. AWS, Google Cloud, Azure, Microsoft 365, Adobe, Salesforce, Google Workspace, GitHub, Apple, Firebase, PagerDuty, Zendesk, Heroku, GitLab, Meta. Each one read with code we wrote specifically for it.
  • Thousands of SaaS vendors. Stripe, OpenAI, Cloudflare, Slack, Zoom, Datadog, Shopify, and the long tail. If they have a public status page, we read it.
  • Down to the service. Monitor just "EC2 us-east-1" or "Stripe Checkout", not the whole provider.
  • New providers added automatically as they appear on the public web. No gate-keeping, no waitlist.
Browse the catalog →
Dashboard

One dashboard for every provider you depend on

Add the providers your app depends on. Filter each one to the specific service you care about. See live status across all of them in one grid. Filter by "has issues" when you only want to see the things that are broken.

  • Search to add. Two clicks from zero to monitoring.
  • Per-monitor service filters (e.g. "EC2 · us-east-1", "Stripe · Checkout · API")
  • Common severity scale. We translate each vendor's terms into the same set.
  • Sort by status, name, last change; filter by "has issues"
  • Per-monitor pause (mute without losing your setup)
Deep dive: status aggregation →
Incidents

Every incident, every vendor, one chronological feed

The incident list spans every monitor in your account. Active incidents at the top, recent ones below, with full history on its own tab. Every row links into a drill-down showing the full update thread from the vendor.

  • 4 views: Active · Recent · History · Per-incident timeline
  • Severity-normalised: Minor · Degraded · Major · Maintenance, across all vendors
  • Component-linked: each incident attributes to specific affected components
  • Duration tracked: time-to-resolution visible at a glance
Deep dive: incident timeline →
Drill-down

The full update thread, with timestamps

Click any incident and you get the vendor's full narrative. Investigating, identified, monitoring, resolved, with the timestamps pingoru.io recorded when each update was posted. No clicking through to six different status pages during an outage.

  • Vendor's original prose, preserved exactly
  • Status transitions rendered inline with the timeline
  • Affected components linked to their component page
  • Total duration + resolved timestamp up top
Maintenance

Plan deploys around vendor downtime

Every upcoming and in-progress maintenance window across the providers you watch, in one place. Switch between in-progress, upcoming, completed, and a monthly calendar. Same data, four views so you can scan it the way your brain wants to.

  • Four views: In progress · Upcoming · Completed · Calendar
  • Down to the region or service (not just "Azure is doing maintenance")
  • Maintenance has its own event type in alerts. Don't wake on-call.
  • "Scheduled" vs "In progress" badge so you can tell planned from live
Deep dive: maintenance calendar →
Calendar view

Monthly grid, vendor-coloured

Same maintenance dataset, different layout. Useful when you're scheduling a release and want to glance at the next 30 days to find a window when none of your vendors are touching prod.

Notification groups

One unit for the whole alerting stack: recipients, integrations, filters, scope

Notification groups bundle who (multiple email recipients), where else (any number of webhook integrations including Slack, Discord, Teams, PagerDuty, custom URLs), what (severity + event filters), and which monitors (all on the account, or a hand-picked subset). Send major-only to your on-call's PagerDuty, send the everything-else feed to a team Slack, send maintenance to a shared inbox. All from the same model.

  • Default group set up the moment you sign up. Your email pre-verified, ready to receive.
  • Multiple recipients per group; each verifies independently and has their own unsubscribe link
  • Mix email and webhook integrations in any combination: email-only, webhook-only, or both
  • Per-group severity filters (Major / Minor / Maintenance) and event filters (Opened / Updated / Resolved)
  • Webhooks cryptographically signed (X-Pingoru-Signature-256); deliveries deduped on (channel, event)
Deep dive: notification groups →
Webhook payload

What arrives at your endpoint

JSON body with the incident + update + provider blocks, plus the signature header. Same shape on every plan, same shape for every event type. No hidden gotchas.

POST https://ops.acme.io/pingoru-hook
X-Pingoru-Signature-256: sha256=8b2c…de91
Content-Type: application/json

{
  "event": "incident.opened",
  "timestamp": "2026-04-24T14:06:22Z",
  "provider": {
    "slug": "github",
    "name": "GitHub",
    "url": "https://pingoru.io/providers/github"
  },
  "monitor": {
    "id": "m_01HXYZ",
    "name": "GitHub Actions",
    "component_filter": ["Actions", "API Requests"]
  },
  "incident": {
    "id": "i_01HABC",
    "title": "Increased error rates on Actions",
    "impact": "minor",
    "started_at": "2026-04-24T14:05:00Z",
    "affected_components": ["Actions", "API Requests"],
    "url": "https://www.githubstatus.com/incidents/xxx"
  }
}
Exports

CSV + JSON incident reports

Pull your incident history out for internal review, vendor-SLA validation, quarterly reliability reports, or compliance. Filter by date range and monitor set, preview the result, download as CSV or JSON.

  • Presets: Last 7d / Last 30d / Last 90d / YTD / Custom
  • One row per incident: title, impact, start, resolved, duration, components, full update thread
  • CSV for spreadsheets; JSON for programmatic consumers
  • Free: 30-day rolling window · Pro: full 1-year window
app.pingoru.io/reports
Date range
Last 7d Last 30d Last 90d YTD Custom
Monitors
✓ Amazon Web Services
✓ Cloudflare
✓ Stripe
✓ GitHub
42 matching incidents Preview · showing first 25
JSON Download 42 as CSV
Public pages

A landing page for every provider

Every provider in the catalogue has its own public page on pingoru.io with live status, current incidents, recent history, and scheduled maintenance. Three URL shapes for the same page, indexed by Google:

  • /providers/<slug>: the canonical URL
  • /is-<slug>-down: matches what people search for
  • /status/<slug>: matches browser autocomplete
  • Full OpenGraph + JSON-LD so social unfurls cleanly
  • No signup required to view any of them
See the catalog →
pingoru.io/is-stripe-down
S
Stripe
Checked just now · Source: status.stripe.com
Up
Components (173 up)
Recent incidents
Elevated latency on Radar API Apr 20 · 1h 14m
Degraded webhook delivery Apr 14 · 42m
What's in each plan

Free for solo devs. Pro for teams that own production.

A side-by-side breakdown. Every feature above is on both plans unless explicitly limited here. No gotchas where a "premium feature" is just the free one with a 7-day trial.

FeatureFreePremium
Monitors
Each is a provider + optional component filter
550
Team members
Users on the same account
110
Notifications per month
Email, Slack, Discord and webhook combined
15Unlimited
Incident history retention
For postmortems, retros, SLA reports
30 days1 year
Email alerts
Sent from a verified domain. No spam folder.
✓✓
Native Slack app
OAuth install, Block Kit messages, /pingoru slash command
✓✓
Native Discord integration
Rich embed alerts in any channel, no OAuth required
✓✓
Generic webhook
POST signed JSON to Teams, Mattermost, your own tooling, anywhere
✓✓
Notification groups
Recipients + integrations + filters + scope, all in one unit
✓✓
Multiple recipients per group
Each verified independently, each with their own unsubscribe link
✓✓
Filter alerts by component
e.g. "EC2 in us-east-1 only"
✓✓
Per-group event + severity filters
Opened / Updated / Resolved · Major / Minor / Maintenance
✓✓
Maintenance calendar
See scheduled work across every monitored vendor
✓✓
CSV + JSON incident exports
For your data warehouse, BI tool, or vendor reliability reports
Last 30 daysFull 1 year
Per-incident notification preferences
Different recipients for different vendors / severities
✓✓
MCP endpoint
Plug Pingoru into Claude, Cursor, Cline, Zed, Goose…
—✓
Priority email support
Direct line during your incidents, same-day reply
—✓
Start on Free → Full pricing page

Frequently asked

Which features are free?

5 monitors, 1 seat, 15 notifications per month, email alerts, the native Slack app (with the /pingoru slash command), native Discord integration, 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 ($15/mo) is for teams: 50 monitors, 10 team seats, 1-year incident history (for postmortems and SLA reports), per-incident notification preferences, the MCP endpoint for AI assistants, 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 5 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; Premium covers the full year.

Is there an API?

A public REST API is planned for Premium after the self-serve checkout lands. For now, the signed-webhook + CSV/JSON export pair covers most "get the data out" use cases. If you have a specific automation need, email [email protected] and we'll see what makes sense.

One dashboard for every provider you depend on.

Free for 5 monitors. $15/mo for 50 + team features. No credit card.

Start monitoring free →