JsonAPI
GraphQL
graphql.js
Apollo
Graphene
Productivity Power Tools
Mercurius
Prisma GraphQL API
OutageDeck
StatusGator
IsDown.app
IncidentHub
StatusTicker
DownDetector
Indatus
VendorStatus.dev
I built OutageDeck because I got tired of opening a dozen browser tabs every time something broke, trying to work out whether the problem was mine or somebody else's.
It watches the status pages that 172 cloud and SaaS companies publish about themselves. AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, Vercel, and a long tail of others. Every ten minutes it reads what each one is saying and puts it all in one place, so answering "is it us or them" takes seconds instead of twenty minutes. When something does break, it tells you where you already are: Slack, Teams, Discord, email, or your own webhook.
One rule I set early and haven't bent: official sources only. Nothing scraped, nothing crowdsourced, no probing from my own servers. If a vendor hasn't said it, OutageDeck doesn't say it either. That means fewer vendors than the aggregators that scrape everything. It also means that when you get an alert, something is genuinely wrong.
The other thing that kept bothering me is how fast the evidence disappears. A vendor resolves an incident, the banner comes down, and six weeks later you're writing a postmortem with nothing to point at. So OutageDeck keeps it. Uptime history and incident timelines stay where you left them, and every entry links back to the vendor's own page.
If you depend on something I don't track, paid plans let you point it at any Statuspage or Instatus page yourself, and it shows up privately in your account like everything else.
For developers there's a JSON API with no account and no key, an OpenAPI 3.1 spec, RSS feeds, README status badges, and an MCP server so a coding agent can check whether a vendor is down before it starts tearing apart your code.
Email alerts for five vendors are free, no card needed. Paid plans start at $19 a month and add the other channels, unlimited vendors, and your own feeds.
Built and run by Kerolos Atallah, a developer in Cairo. Not affiliated with any of the companies it tracks.
JsonAPI OutageDeckOutageDeck's answer:
OutageDeck's answer:
OutageDeck only reports what vendors officially publish. Every status comes from the provider's own machine-readable feed, never crowd reports and never scraping. Then it holds vendors to what they said:
OutageDeck's answer:
I got tired of opening a dozen vendor status pages during every incident, just to work out whether the problem was mine or somebody else's. So I built the thing I wanted.
It launched in July 2026 as one live board over the official status feeds of the vendors teams actually depend on. The catalog is at 172 now: AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, and a long tail of others.
The rule from day one: official machine-readable sources only. No crowd reports, no scraping. If a status can't be traced back to the vendor's own feed, it doesn't get published.
OutageDeck's answer:
Anyone whose incident channel regularly starts with "is AWS down, or is it just us?":
OutageDeck's answer:
Three reasons.
Based on our record, JsonAPI seems to be more popular. It has been mentiond 52 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
REST does not define a standard batching mechanism at the protocol level. When batching is needed, it is handled through API design (such as bulk endpoints), infrastructure, or framework-specific solutions. Some specifications attempt to address this, such as ODataโs batch format or JSON:APIโs compound documents, but adoption is inconsistent. - Source: dev.to / 4 months ago
Why reinvent the wheel poorly when you have a hundred of solutions like https://jsonapi.org/? - Source: Hacker News / 12 months ago
For context, the subject-predicate-object pattern is known as a semantic triple or Resource Description Framework (RDF) triple: https://en.wikipedia.org/wiki/Semantic_triple They're useful for storing social network graph data, for example, and can be expressed using standards like Open Graph and JSONAPI: https://ogp.me https://jsonapi.org I've stored RDF triples in database tables and experimented with query... - Source: Hacker News / about 1 year ago
Built on JSON API standards, the OSF API is intuitive for anyone familiar with REST conventions. Once you learn its core patterns, you can quickly expand into project creation, user collaboration, and moreโwithout constantly referencing documentation. The official OSF API docs provide everything needed to get started. - Source: dev.to / over 1 year ago
Following established patterns reduces the learning curve for your API. Adopt conventions from JSON:API or Microsoft API Guidelines to provide consistent experiences. - Source: dev.to / over 1 year ago
GraphQL - GraphQL is a data query language and runtime to request and deliver data to mobile and web apps.
StatusGator - Early outage alerts for every app you rely on
graphql.js - A reference implementation of GraphQL for JavaScript - graphql/graphql-js
IsDown.app - When a vendor goes down, does your team find out in seconds or after users start complaining? IsDown monitors 6,000+ official status pages and alerts your team within seconds across Slack, PagerDuty, Datadog, and more. 14-day free trial
Apollo - Apollo is a full project management and contact tracking application.
IncidentHub - Real-Time Vendor Monitoring That Actually Works