Fetch incident history and scheduled maintenance windows for a vendor. Returns full incident timeline — each investigator update, affected components, and resolution. Filter by status to focus on active incidents (use before deploy), resolved history (for postmortem), or maintenance windows: upcoming and in-progress ones, plus completed ones on Atlassian Statuspage, incident.io, Firehydrant, and Datadog vendors (Status.io vendors list upcoming and in-progress only). Narrow further with match (terms in the title or affected component names, plus location names and IDs on Google Cloud and AWS) and since/until (a start-date range) — all applied before paging, so totals count only what they keep. Page through long histories with limit + offset — a truncated result discloses the total and returns the value to page with in nextOffset. Each response is held to 64,000 bytes per surface: a page can stop short of limit at that budget (the paging fields and notice say so), and an incident too large on its own keeps only its newest updates, with updates_omitted counting the rest — full_updates: true returns them all. Some vendor feeds cap their own history: when upstreamCeiling is present the vendor API returned everything it will serve, and older incidents are not reachable at a higher offset; the notice says whether since reaches them. On Atlassian Statuspage vendors, since (a date) also reads the status page's quarterly history archive back to that date, or 24 months back at most, where the page publishes one — not on a vendor that covers only part of a shared page, such as "sendgrid"; those records are marked source: "history" and carry the title, impact, start and end times, and final update message only. On incident.io vendors (such as "openai"), whose feed lists the last 90 days by default, since reads the page's incident list one calendar quarter at a time back to that date, 24 months back at most, and returns full records (source: "api"). An empty result, or a history read that stopped short of since, explains itself in notice.
View input schema
{
"type": "object",
"properties": {
"vendor": {
"type": "string",
"minLength": 1,
"description": "Vendor slug (e.g., \"github\", \"aws\") or raw Atlassian Statuspage base URL, read at its origin and path (credentials, query, and fragment dropped). Most other backends are reached by slug only: a URL on such a vendor's status page (https://status.gitlab.com) is rejected with the slug to pass. A URL on an incident.io page (https://status.openai.com) reads its Statuspage-compatible API instead, which lists 25 incidents at most and no maintenance windows; pass the slug (\"openai\") for the page's full feed. Use devops_list_vendors to find slugs."
},
"filter": {
"default": "all",
"description": "all: incidents plus scheduled maintenances. active: only incidents with status investigating/identified/monitoring. resolved: only fully resolved incidents. scheduled: only maintenance windows — upcoming and in-progress ones, plus completed ones on Atlassian Statuspage, incident.io (\"fly-io\", \"supabase\"), Firehydrant (\"redis-cloud\"), and Datadog (\"datadog\", \"datadog-eu1\") vendors; Status.io vendors (\"gitlab\", \"neon\") list upcoming and in-progress windows only. Not every vendor backend serves every filter — \"aws\" lists a resolved event only until it drops off its feed, \"azure\" lists open items only (never resolved), and \"aws\", \"azure\", \"azure-devops\", \"gcp\", and \"slack\" publish no maintenance windows. An empty result names which case applied.",
"type": "string",
"enum": [
"all",
"active",
"resolved",
"scheduled"
]
},
"limit": {
"default": 20,
"description": "Maximum incidents to return per call, at least 1. A value over 50 is served as 50, and the notice says so. Page through longer history with offset rather than raising this.",
"type": "integer",
"minimum": 1,
"maximum": 9007199254740991
},
"offset": {
"default": 0,
"description": "Number of matching incidents to skip before applying limit, for paging through history. 0 (default) returns the most recent page; a truncated result returns the value to use next in the nextOffset field. Raising offset past the number of matches returns an empty list and says so.",
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"since": {
"description": "Earliest start date to include, as YYYY-MM-DD (UTC). Accepted with filter \"all\" or \"resolved\". A record's start is its scheduled_for, else the earlier of its started_at and created_at; records that started before since are left out, and limit/offset page the rest. On Atlassian Statuspage vendors it also reads the status page's quarterly history archive back to this date, reaching incidents older than the 50 the status API serves — except on a vendor that covers only part of a shared status page (such as \"sendgrid\" on Twilio's page), whose archive records carry no components to narrow by. The archive is read back 24 months at most: for an earlier date, older records come only from what the status API still returns (such as completed maintenance windows), and the notice gives the date the archive was read back to. On incident.io vendors (\"openai\", \"supabase\") it reads the status page's incident list one calendar quarter per request back to this date, 24 months back at most, past the last 90 days that list covers without since; those are full records, marked source: \"api\". On a vendor with no archive this tool reads, since filters only what its status feed returns. Where that feed is a recent window, a since earlier than the oldest record it returned gets that record's start date in the notice. A feed that carries its page's whole history (such as \"redis-cloud\" or \"datadog\") holds nothing older, so it gets that date only on an empty result whose until is earlier than it. Omit to read only the status API.",
"anyOf": [
{
"type": "string",
"const": ""
},
{
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
"description": "Earliest start date to include, as YYYY-MM-DD (UTC), e.g. \"2025-10-01\"."
}
]
},
"until": {
"description": "Latest start date to include, as YYYY-MM-DD (UTC) — the whole day, so until equal to since returns that one day. Accepted with filter \"all\" or \"resolved\", and on or after since. A record's start is its scheduled_for, else the earlier of its started_at and created_at; records that started after until are left out before limit/offset page the rest. It reads no history archive on its own: set since as well to reach incidents older than the status API returns, through an archive read back 24 months at most. On a vendor with no archive this tool reads, until alone filters what its status feed returns. Where that feed is a recent window, the notice then gives the start date of the oldest record it returned. A feed that carries its page's whole history (such as \"redis-cloud\" or \"datadog\") gets that date only on an empty result whose until is earlier than it.",
"anyOf": [
{
"type": "string",
"const": ""
},
{
"type": "string",
"format": "date",
"pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
"description": "Latest start date to include, as YYYY-MM-DD (UTC), e.g. \"2025-10-31\"."
}
]
},
"match": {
"description": "Terms to look for, separated by spaces, in each incident's title, its affected component names, and, on Google Cloud and AWS, its affected location names and IDs (\"us-central1\", \"me-south-1\", \"bahrain\"), ignoring case. An incident is kept when every term appears in its title, one of its component names, or one of its location names or IDs, each term on its own. A one-word term matches all or part of a word. A term whose words are joined by punctuation (\"eu-central-1\", \"git-operations\", \"git/operations\") matches only where those words appear together, in that order, within one of those texts, anywhere in it: \"eu-central-1\" finds eu-central-1 but not me-central-1, and \"eu-west\" finds every eu-west region. History-archive records, and vendors that publish no components, match on title alone. Applied before limit/offset, so totals and paging count only the matches. Leave blank to keep every incident.",
"type": "string",
"maxLength": 200
},
"full_updates": {
"default": false,
"description": "Return every update of an incident that is too large for the response size budget on its own, instead of only its newest updates. Default false. Pair it with limit: 1 and the offset the notice names; the response can then run past the budget.",
"type": "boolean"
}
},
"required": [
"vendor"
],
"$schema": "https://json-schema.org/draft/2020-12/schema",
"additionalProperties": false
}