API Status Check

Live status probes plus published uptime and incident history for 280+ APIs and cloud services.

От сообществаРаботаетБез входаГлобальныйБесплатноМожет изменять данные

Что умеет

    Какие данные видит

    Нужен ли аккаунт

    Не нужен: сервер работает без входа

    Live status probes plus published uptime and incident history for 280+ APIs and cloud services.

    Список инструментов сервера (8)

    Технические названия из tools/list. Нужны только разработчикам.

    list_apisList the APIs and developer platforms this service monitors, optionally filtered by category. Statuses come from the most recently published monitor snapshot, not a live probe, and can be up to a day old — check monitorCheckedAt, and call get_api_status when the caller needs the status right now.
    search_apisFind monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.
    get_api_statusProbe a monitored API endpoint at call time and return up/degraded/down with the response time. This is the tool to reach for when a user asks "is X down?" — it makes a real request rather than reading the hourly cache.
    list_down_apisEverything the most recent monitor run found down or degraded, across all categories. Returns an empty list when the monitor snapshot is missing or stale — an empty list is therefore not proof that everything is healthy; check monitorLastRun.
    get_uptime_historyUptime percentages, response-time stats and recorded data points for one API over a time range. History is retained for 30 days; an API added recently will have few or no data points, which reads as null percentages rather than 100%.
    get_incident_historyReal incidents a vendor published on its own status page, newest first, with start/end times, duration, severity, affected components and a link to the vendor’s incident page. Use this for "has X been flaky lately?" — it is the vendor’s own record, not our probes. Services without a public Statuspage endpoint return covered:false rather than an empty list.
    rank_reliabilityGiven several service slugs, return a scorecard ranked worst-first: incident count, total downtime minutes, mean time to resolve, and the longest incident over a window. Use this to answer "which vendor in my stack is least reliable?" — it compares services across vendors, which a vendor’s own monitoring tool cannot. Services with no archive are listed separately as uncovered instead of being ranked as flawless.
    list_categoriesCategory slugs and how many monitored APIs sit in each. Use the slugs with list_apis.