Vendor Status Watch

← all vendors

Frontify status history

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

0incidents, last 30 days
1incidents, last 90 days
6incidents on record
Incidents per week, last 12 weeks:
Get Frontify alerts in your Slack — free templateRSS for Frontify

How long do Frontify incidents last?

75 minmedian incident duration6 measured
4.1 h90th percentile1 in 10 ran longer
16.6 hmedian, major/critical only1 incident

From 6 incidents with a vendor-posted start and resolve time. Longest on record: Asset processing and delivery broken for some assets — 16.6 h (2025-10-20 15:37 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 (6)

StartedIncidentStatusImpactDuration
2026-07-24 12:05 UTCDegraded Performanceresolvedminor1 h 58 min
2026-03-12 14:34 UTCDegraded Performanceresolvednone33 min
2026-01-13 16:38 UTCDegraded Performanceresolvedminor13 min
2025-10-20 15:37 UTCAsset processing and delivery broken for some assetsresolvedmajor16 h 35 min
2025-10-20 14:18 UTCPartial outage due to AWS issue - SelfServiceresolvednone4 h 04 min
2025-10-20 11:56 UTCPartial outage due to AWS issueresolvednone0 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 Frontify with the template

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

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