Vendor Status Watch

← all vendors

FOSSA status history

Current state: operational — “All Systems Operational” per https://status.fossa.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
1incidents, last 90 days
14incidents on record
Incidents per week, last 12 weeks:

How long do FOSSA incidents last?

2.2 hmedian incident duration14 measured
12.2 h90th percentile1 in 10 ran longer
4.2 hmedian, major/critical only4 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-05 20:50 UTCFOSSA app outageresolvednone30 min
2026-06-01 21:46 UTCSlow performance on component analysisresolvedminor55 min
2026-05-07 20:01 UTCDegraded Performanceresolvednone1 h 20 min
2026-05-06 15:51 UTCDegraded Performanceresolvedminor4 h 56 min
2026-04-21 18:36 UTCDegraded performance: Container scanningresolvedminor58 min
2026-04-16 22:14 UTCSlow performance on analysis serviceresolvedmajor1 h 13 min
2026-03-17 01:55 UTCDegraded Performanceresolvednone2 h 12 min
2026-03-12 20:48 UTCService disruptionresolvedminor44 min
2026-02-26 14:04 UTCInvestigating additional build slowdownsresolvedminor30 h 54 min
2026-02-25 14:28 UTCIncreased build queue wait times for CLI-submitted buildsresolvedmajor12 h 09 min
2025-12-16 23:50 UTCSlow Issue Scans and Degraded Web App Performanceresolvedmajor2 h 12 min
2025-11-24 21:54 UTCOngoing Issue Scanning Service Disruptionresolvednone4 h 52 min
2025-09-11 16:04 UTCElevated build timesresolvedminor4 h 41 min
2025-08-27 15:23 UTCPartial Analysis Outageresolvedcritical6 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
}