Vendor Status Watch

← all vendors

Fasterize status history

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

0incidents, last 30 days
0incidents, last 90 days
11incidents on record
Get Fasterize alerts in your Slack — free templateRSS for Fasterize

How long do Fasterize incidents last?

7 minmedian incident duration11 measured
9.4 h90th percentile1 in 10 ran longer
5.7 hmedian, major/critical only3 incidents

From 11 incidents with a vendor-posted start and resolve time. Longest on record: Website status may incorrectly show as “Ping blocked” — 19.1 h (2026-05-20 10:33 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 (11)

StartedIncidentStatusImpactDuration
2026-05-22 09:33 UTCPerformance degradationresolvedmajor5 h 44 min
2026-05-20 10:33 UTCWebsite status may incorrectly show as “Ping blocked”resolvednone19 h 04 min
2026-05-20 08:00 UTCIssue on the flush on the dashboard and APIresolvedminor7 min
2026-04-10 20:30 UTCPerformance degradationresolvednone0 min
2026-02-05 12:00 UTCINP Data Inaccuracy on Safari (iPhone)resolvedminor0 min
2025-11-24 14:50 UTCFasterize Console is slowresolvedminor52 min
2025-10-09 09:01 UTCPlatform unavailabilitypostmortemcritical9 h 22 min
2025-09-25 08:00 UTCSome origin requests got a wrong Client IP header between 09:52 – 10:34 (Paris time)resolvednone0 min
2025-09-09 13:11 UTCPlatform has been unavailableresolvedcritical39 min
2025-09-09 10:13 UTCSlowdowns on the platformpostmortemminor0 min
2025-09-09 00:30 UTCClient IP retrieval has been broken between 14:50 – 18:30 (Paris time)postmortemminor0 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 Fasterize with the template

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

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