APProjects/saas-vendor-outage-duration-incident-resolution-time-mttr

How long do SaaS vendor outages last? Incident resolution time per vendor, rebuilt daily

As of 2026-09-24 12:28 UTC. For every incident a vendor posted on its own public status page with BOTH an opened time and a resolved time, this dataset computes

duration_minutes = resolved_at - started_at

and rolls it up per vendor. It is derived, every day, from the incident table in saas-vendor-status-pages-outages-incidents-daily; the two are rebuilt by the same job and cannot disagree.

The headline, over 15,172 measured incidents across 598 vendors

Excluded, and counted rather than guessed

Most incidents in the last 90 days (to 2026-09-24)

Incident count measures how much a vendor communicates, not how reliable it is: a vendor that posts every blip ranks "worse" here than one that posts nothing. Read it with the median next to it.

“≥” on 18 row(s): the source status-page API returns at most 50 incidents per vendor, and these vendors' archives begin inside the 90-day window, so the count is a floor rather than a total. The median beside it is over the incidents we can see.

Slowest and fastest to resolve (vendors with at least 20 measured incidents)

What is in the files

data/incident_durations.csv — 15,172 rows, one per measured incident:

data/vendor_summary.csv — 598 rows, one per vendor with at least one measured incident: incidents_measured, first_incident, last_incident, median_minutes, p90_minutes, mean_minutes, total_minutes, major_critical_count, major_critical_median_minutes, incidents_90d, minutes_90d.

import pandas as pd
d = pd.read_csv("https://huggingface.co/datasets/APProjects/saas-vendor-outage-duration-incident-resolution-time-mttr/resolve/main/data/incident_durations.csv")
d.groupby("vendor")["duration_minutes"].median().sort_values().tail(20)   # slowest to resolve

Method, and what it does NOT say

• —Times are the vendor's own, as posted on its status page. This is posted incident duration, not measured downtime: a vendor can open the incident late, resolve it early, or never post one at all. It is not an uptime or SLA figure and must not be read as one.
• —History depth differs by platform: Atlassian Statuspage exposes a public incident archive that we back-fill (capped at 50 incidents per vendor by that API); other platforms accumulate only from the day we first watched them (2026-09-04). Cross-vendor counts are therefore not comparable; medians are more robust than counts.
• —Scheduled maintenance is excluded because a planned window is not an outage.
• —Where a resolve time is missing, or where we had to infer resolution from the incident disappearing, the incident is excluded — never estimated.
• —Impact labels are the vendor's; "major" at one vendor is not "major" at another.

Freshness

Rebuilt daily by an automated pipeline from 804 vendor status pages; source snapshot generated 2026-09-24T12:28:39Z. A static copy of this table is wrong within a week, which is why it is published here rather than once.

Keep up with this dataset

Not setting it up today? Join the update list → — an occasional note when this dataset's coverage or schema changes materially. The list is shared across APProjects datasets, holds an email address only, is run by Gumroad, and any message unsubscribes you. The all-vendors RSS feed at https://approjects-vendor-status-watch.static.hf.space/feed.xml needs no address at all.

Paid tier — Hosted watch, $49 / 12 months.

We run the watcher for you: your vendors' public status pages are checked every 5 minutes, and every incident opened, updated or resolved appears in your own private feed within minutes — plus one check-in every 24 hours, so a quiet feed is a working feed rather than an ambiguous one.

Who this is for. For teams that cannot or will not run a GitHub Action: IT and vendor-management staff without a repo, agencies watching clients' vendors, and companies whose policy forbids third-party actions. If you have a repo and five minutes, the free template above is the same engine.

• —Up to 50 vendors from the living map of 1,100+ SaaS status pages; type names at checkout.
• —Checked every 5 minutes for a year by a scheduled job in Apify's cloud — not on a laptop, and not dependent on any server of ours staying up.
• —Delivered as your own private RSS feed, which you point Slack, Teams, Discord or any reader at. We never ask for a webhook, so we hold no credential of yours.
• —A first entry within minutes of purchase naming which vendors matched the map and which did not — nothing is silently unwatched.
• —A vendor we cannot read is reported as CANNOT SEE, never as OK; when it is readable again you are told.
• —No repo, no GitHub, no YAML, no account with us. Nothing to install.

Get the hosted watch — $49 / 12 months · Try it free for 30 days — up to 5 vendors, no card

One payment, no auto-renewal. Full refund within 30 days for any reason — reply to your Gumroad receipt. After that, a pro-rata refund if alerts stop for 7 consecutive days through our fault. Would rather run it yourself? The open-source GitHub Action does the same 5-minute watch for unlimited vendors inside your own account, free: https://github.com/APVentureEngine/vendor-status-watch

Related

• —saas-vendor-status-pages-outages-incidents-daily — the full incident and vendor tables this is derived from.
• —approjects-vendor-status-watch.static.hf.space — the live board, per-vendor history pages, RSS and JSON.
• —Source and MIT template — watch your own vendors from GitHub Actions.

License

CC BY 4.0. Underlying incidents are the vendors' own public status-page posts. Attribution: "Vendor Status Watch, https://approjects-vendor-status-watch.static.hf.space".

Not affiliated with any vendor named here.

<!-- warn-feed:px:start --> <img src="https://cdn.jsdelivr.net/gh/APVentureEngine/vendor-status-watch@main/docs/assets/px/hf/saas-vendor-outage-duration-incident-resolution-time-mttr.png" width="1" height="1" alt=""> _{Card views are counted anonymously: one 1×1 image on a public CDN, no cookies, no script, no personal data. The count is public: <a href="https://data.jsdelivr.com/v1/stats/packages/gh/APVentureEngine/vendor-status-watch@main/files?period=month">jsDelivr stats</a>.} <!-- warn-feed:px:end -->