# Pingoru

> Pingoru watches the official status pages of every cloud and SaaS provider your stack depends on (currently 6,000+) and sends you an email, Slack, Discord, or webhook alert the moment one reports an incident.

Pingoru is a third-party status-monitoring SaaS for indie hackers and small engineering teams. We poll every supported provider's status page on a 5-minute cycle, parse the official incident data, and surface it in one dashboard alongside every other vendor you depend on. We do not manufacture status — we surface what the vendor publishes, attributing the source and the time we saw it. Free for 5 monitors; Premium ($15/month) for 50 monitors, 12 months of history, and every integration.

## Core pages

- [Homepage](https://pingoru.io/): product overview, current global incidents, popular providers
- [Provider directory](https://pingoru.io/providers): searchable index of all 6,000+ monitored providers
- [Pricing](https://pingoru.io/pricing): Free vs Premium plan breakdown
- [Sign up](https://pingoru.io/signup): create a free account (5 monitors, no credit card)
- [Sign in](https://pingoru.io/login): existing accounts
- [About](https://pingoru.io/about): who builds and runs Pingoru
- [Support](https://pingoru.io/support): help articles and documentation
- [Contact](https://pingoru.io/contact): get in touch

## Per-provider pages

The canonical URL for any single provider is https://pingoru.io/providers/<slug>. Aliases https://pingoru.io/is-<slug>-down and https://pingoru.io/status/<slug> resolve to the same content but self-canonicalize to the providers/ URL. Each page includes live status, recent outages, full incident history, 90-day uptime percentage, component breakdown, structured FAQ data (FAQPage JSON-LD), and a CTA to add the provider as a monitor.

Two deeper surfaces are linked from every provider page:

- `https://pingoru.io/providers/<slug>/outage-history` — paginated 90-day incident roster with full update timelines (see *Outage history pages* section below)
- `https://pingoru.io/providers/<slug>/incidents/<incident_id>` — individual incident article page with Article + NewsArticle JSON-LD (see *Per-incident article pages* section below)

Examples (each has a paired `/outage-history` deep-dive):
- [Stripe](https://pingoru.io/providers/stripe) · [outage history](https://pingoru.io/providers/stripe/outage-history) — payments infrastructure
- [Amazon Web Services](https://pingoru.io/providers/amazon-web-services) · [outage history](https://pingoru.io/providers/amazon-web-services/outage-history) — cloud compute, storage, networking
- [Cloudflare](https://pingoru.io/providers/cloudflare) · [outage history](https://pingoru.io/providers/cloudflare/outage-history) — CDN, DNS, security
- [OpenAI](https://pingoru.io/providers/openai) · [outage history](https://pingoru.io/providers/openai/outage-history) — GPT and DALL-E APIs
- [GitHub](https://pingoru.io/providers/github) · [outage history](https://pingoru.io/providers/github/outage-history) — code hosting, Actions, packages
- [Google Cloud Platform](https://pingoru.io/providers/google-cloud) · [outage history](https://pingoru.io/providers/google-cloud/outage-history) — GCP services and regions
- [Microsoft Azure](https://pingoru.io/providers/microsoft-azure) · [outage history](https://pingoru.io/providers/microsoft-azure/outage-history) — Azure cloud services
- [Slack](https://pingoru.io/providers/slack) · [outage history](https://pingoru.io/providers/slack/outage-history) — team messaging
- [Datadog](https://pingoru.io/providers/datadog) · [outage history](https://pingoru.io/providers/datadog/outage-history) — observability platform
- [Vercel](https://pingoru.io/providers/vercel) · [outage history](https://pingoru.io/providers/vercel/outage-history) — frontend hosting

## Outage history pages

Each provider has a dedicated deep-dive at `https://pingoru.io/providers/<slug>/outage-history`. This is the long-form, paginated companion to the compact "Outage history" section on the provider page. Lists every resolved incident from the last 90 days with full update timeline, affected components, detected/resolved timestamps, and duration. Carries CollectionPage + ItemList JSON-LD with Article references for incidents inside the per-incident live window.

- [Atlassian outage history](https://pingoru.io/providers/atlassian/outage-history): umbrella view aggregating Jira, Confluence, Bitbucket, OpsGenie

## Per-incident article pages

Each incident from the last 90 days has its own permanent URL at `https://pingoru.io/providers/<slug>/incidents/<incident_id>`. Pages render the full incident headline, severity, ongoing/resolved state, affected components, complete update timeline, and "other recent <provider> outages" sidebar. Carry Article (and NewsArticle for outages) JSON-LD — eligible for Top Stories / News-card surfaces. Once an incident's started_at ages past 90 days the URL 301-redirects to its outage-history anchor.

This means AI agents answering "was Stripe down on <date>?" or "what happened during the <provider> incident on <month> <year>?" can deep-link directly to the structured incident page. The article body, started_at, resolved_at, dateModified, affected components, and sourced upstream URL are all in the rendered HTML and JSON-LD.

## Marketing landing pages (search-intent specific)

- [Cloud monitoring](https://pingoru.io/cloud-monitoring): general cloud monitoring overview
- [Cloud status monitoring](https://pingoru.io/cloud-status-monitoring): aggregated status-page monitoring
- [Cloud uptime monitoring](https://pingoru.io/cloud-uptime-monitoring): uptime tracking
- [SaaS monitoring](https://pingoru.io/saas-monitoring): SaaS-specific use cases
- [Status page monitoring](https://pingoru.io/status-page-monitoring): how we read status pages
- [SLA monitoring](https://pingoru.io/sla-monitoring): vendor SLA tracking and service-credit-claim evidence
- [Root cause analysis](https://pingoru.io/root-cause-analysis): tracing customer issues to upstream incidents
- [Use cases](https://pingoru.io/use-cases): summary of who uses Pingoru and how

## Features

- [Feature index](https://pingoru.io/features)
- [Status aggregation](https://pingoru.io/features/status-aggregation): one dashboard, every vendor
- [Status page aggregator](https://pingoru.io/features/status-page-aggregator): how the aggregator works
- [Incidents](https://pingoru.io/features/incidents): incident-level detail and timelines
- [Maintenance](https://pingoru.io/features/maintenance): scheduled maintenance windows
- [Notifications](https://pingoru.io/features/notifications): email, Slack, Discord, Teams, webhooks

## Support / docs

- [Getting started](https://pingoru.io/support/getting-started): set up your first monitor
- [Notifications](https://pingoru.io/support/notifications): configure alerts and notification groups
- [Incidents](https://pingoru.io/support/incidents): how incidents are captured and surfaced
- [Maintenance](https://pingoru.io/support/maintenance): how scheduled maintenance is handled

## Public API (read-only)

Pingoru exposes a small public API that anyone can query without authentication. Useful for AI agents that want to answer questions like "is X down right now?" or "what's the recent uptime of Y?".

- `GET https://pingoru.io/api/providers?q=<query>&limit=<n>`: search or list providers
- `GET https://pingoru.io/api/search/popular?limit=<n>`: most-subscribed providers
- `GET https://pingoru.io/api/search/count`: total provider count
- `GET https://pingoru.io/api/providers/<slug>/uptime?days=<n>`: per-day status + computed uptime percentage
- `GET https://pingoru.io/api/providers-recent-incidents?limit=<n>&days=<n>`: cross-provider incident feed
- `GET https://pingoru.io/api/providers/<slug>/outage-history?page=<n>`: paginated last-90-days incident list with full update timelines, affected components, durations
- `GET https://pingoru.io/api/providers/<slug>/incidents/<incident_id>`: single incident detail (returns 410 with redirect_to for incidents older than the per-incident live window)
- `GET https://pingoru.io/health`: public health check (Bearer-token gated in prod)

The main sitemap is at [https://pingoru.io/sitemap.xml](https://pingoru.io/sitemap.xml) — a flat urlset of ~12,800 marketing + provider URLs. Per-incident article URLs live in paginated companion files at `https://pingoru.io/sitemap-incidents-N.xml` (40,000 URLs each, page count grows with the catalog); `robots.txt` enumerates each one for crawler auto-discovery.

## What Pingoru is and isn't

**Is:** an aggregator + alerter for *upstream* (vendor) status. We watch 6,000+ status pages so engineers don't have to manually subscribe to each vendor's individual feed. Polls every 5 min. Email + Slack + Discord + Teams + webhook alerts.

**Isn't:** an internal uptime monitor (we don't ping your endpoints — pair us with Pingdom / UptimeRobot / Better Stack for that), a status page builder (we read status pages, we don't host them), or a synthetic checker.


## Brand

The Pingoru mascot is a happy green cartoon kangaroo. The wordmark is "pingoru" with "ping" in dark forest green and "oru" in bright leaf green. Brand color is #3DB54A.

## See also

- [llms-full.txt](https://pingoru.io/llms-full.txt): the long-form companion to this document with full FAQ, plan comparison, glossary, use cases, and detailed API reference. ~30KB.