F-Secure status history

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

1incidents, last 30 days

2incidents, last 90 days

3incidents on record

Incidents per week, last 12 weeks:

Get F-Secure alerts in your Slack — free template RSS for F-Secure

How long do F-Secure incidents last?

24.3 hmedian incident duration3 measured

45.1 days90th percentile1 in 10 ran longer

—median, major/critical onlynone posted

From 3 incidents with a vendor-posted start and resolve time. Longest on record: F-Secure ID Monitoring Internal Error — 45.1 days (2025-09-26 05:14 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 (3)

Started	Incident	Status	Impact	Duration
2026-09-02 11:15 UTC	My F-Secure: Service Disruption	resolved	none	24 h 16 min
2026-07-28 10:34 UTC	[Resolved] Service Notification – Activation Failures (APAC/Japan Region)	resolved	none	24 h 01 min
2025-09-26 05:14 UTC	F-Secure ID Monitoring Internal Error	resolved	none	45 d 2 h

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 F-Secure with the template

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

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