Flagsmith status history

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

1incidents, last 30 days

1incidents, last 90 days

4incidents on record

Incidents per week, last 12 weeks:

Get Flagsmith alerts in your Slack — free template RSS for Flagsmith

How long do Flagsmith incidents last?

95 minmedian incident duration4 measured

4.7 h90th percentile1 in 10 ran longer

4.7 hmedian, major/critical only1 incident

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Task processor down — 4.7 h (2025-10-23 10:08 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 (4)

Started	Incident	Status	Impact	Duration
2026-09-10 14:43 UTC	Delays processing flag changes	resolved	minor	1 h 27 min
2026-03-03 17:00 UTC	Numeric values incorrectly being converted to numbers in environment documents	postmortem	none	0 min
2026-01-22 16:56 UTC	Data parsing issues in Edge API	resolved	minor	1 h 44 min
2025-10-23 10:08 UTC	Task processor down	resolved	major	4 h 41 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 Flagsmith with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "flagsmith"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}