60SecMonitor Incidents API

The Incidents API from 60SecMonitor — 1 operation(s) for incidents.

GitHub OpenAPI

Operations 1

GET /v1/incidents Recent incidents for a vendor (60SecMonitor) #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/isitdownapi-com:isitdownapi-com-incidents-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

isitdownapi-com-incidents-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: 60SecMonitor Status Incidents API
  version: 1.1.0
  description: Is this vendor down? Pay-per-call current status and recent incidents for 1,400+ SaaS/cloud vendors, read live from 60SecMonitor (isitdownapi.com). Batch status for up to 25 vendors, and an MCP server at /mcp.
  contact:
    name: 60SecMonitor Status API
    email: dario@inboxguards.com
    url: https://api.isitdownapi.com/llms.txt
  x-guidance: 'Is this vendor down? Pay-per-call current status and recent incidents for 1,400+ SaaS/cloud vendors, read live from 60SecMonitor (isitdownapi.com). Batch status for up to 25 vendors, and an MCP server at /mcp. Call a paid route without payment to get an x402 v2 challenge (402 + PAYMENT-REQUIRED header), pay in USDC, retry with PAYMENT-SIGNATURE. Invalid input -> 400, never charged. More: https://api.isitdownapi.com/llms.txt'
servers:
- url: https://api.isitdownapi.com
tags:
- name: Incidents
paths:
  /v1/incidents:
    get:
      operationId: v1_incidents
      summary: Recent incidents for a vendor (60SecMonitor)
      description: Up to 10 most recent incidents (title, status, severity, start/resolve times) for one vendor from 60SecMonitor. Unknown vendors return 404 and are not charged.
      x-payment-info:
        price:
          mode: fixed
          currency: USD
          amount: '0.01'
        protocols:
        - x402:
            version: 2
            scheme: exact
            network: eip155:8453
            asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
            payTo: '0x2dAF658B01e257206375798a15832E9f547D65dD'
      responses:
        '200':
          description: Success (payment settled)
          content:
            application/json: {}
        '400':
          description: Invalid input. Never charged.
        '402':
          description: Payment required. x402 v2 challenge in the PAYMENT-REQUIRED header.
        '502':
          description: Upstream data source failed. Payment NOT settled.
      parameters:
      - name: vendor
        in: query
        required: true
        schema:
          type: string
          minLength: 2
          maxLength: 100
          description: Vendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com
        example: stripe
      tags:
      - Incidents
x-discovery:
  wellKnown: https://api.isitdownapi.com/.well-known/x402
  llms: https://api.isitdownapi.com/llms.txt