FOSSA status history
Current state: operational — “All Systems Operational” per https://status.fossa.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do FOSSA incidents last?
From 14 incidents with a vendor-posted start and resolve time. Longest on record: Investigating additional build slowdowns — 30.9 h (2026-02-26 14:04 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (14)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-05 20:50 UTC | FOSSA app outage | resolved | none | 30 min |
| 2026-06-01 21:46 UTC | Slow performance on component analysis | resolved | minor | 55 min |
| 2026-05-07 20:01 UTC | Degraded Performance | resolved | none | 1 h 20 min |
| 2026-05-06 15:51 UTC | Degraded Performance | resolved | minor | 4 h 56 min |
| 2026-04-21 18:36 UTC | Degraded performance: Container scanning | resolved | minor | 58 min |
| 2026-04-16 22:14 UTC | Slow performance on analysis service | resolved | major | 1 h 13 min |
| 2026-03-17 01:55 UTC | Degraded Performance | resolved | none | 2 h 12 min |
| 2026-03-12 20:48 UTC | Service disruption | resolved | minor | 44 min |
| 2026-02-26 14:04 UTC | Investigating additional build slowdowns | resolved | minor | 30 h 54 min |
| 2026-02-25 14:28 UTC | Increased build queue wait times for CLI-submitted builds | resolved | major | 12 h 09 min |
| 2025-12-16 23:50 UTC | Slow Issue Scans and Degraded Web App Performance | resolved | major | 2 h 12 min |
| 2025-11-24 21:54 UTC | Ongoing Issue Scanning Service Disruption | resolved | none | 4 h 52 min |
| 2025-09-11 16:04 UTC | Elevated build times | resolved | minor | 4 h 41 min |
| 2025-08-27 15:23 UTC | Partial Analysis Outage | resolved | critical | 6 h 15 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch FOSSA with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"fossa"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}