Vendor Status Watch

← all vendors

Font Awesome status history

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

0incidents, last 30 days
0incidents, last 90 days
3incidents on record
Get Font Awesome alerts in your Slack — free templateRSS for Font Awesome

How long do Font Awesome incidents last?

104 minmedian incident duration3 measured
2.5 h90th percentile1 in 10 ran longer
82 minmedian, major/critical only2 incidents

From 3 incidents with a vendor-posted start and resolve time. Longest on record: Pro NPM Unavaliable — 2.5 h (2026-03-31 12:03 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)

StartedIncidentStatusImpactDuration
2026-03-31 12:03 UTCPro NPM Unavaliableresolvedcritical2 h 31 min
2025-12-05 09:05 UTCMajor Outageresolvedcritical13 min
2025-11-18 14:40 UTCPartial outage for some services provided through Cloudflareresolvedminor1 h 44 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 Font Awesome with the template

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

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