Vendor Status Watch

← all vendors

Flatfile status history

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

3incidents, last 30 days
3incidents, last 90 days
21incidents on record
Incidents per week, last 12 weeks:

How long do Flatfile incidents last?

76 minmedian incident duration20 measured
3.1 h90th percentile1 in 10 ran longer
60 minmedian, major/critical only2 incidents

From 20 incidents with a vendor-posted start and resolve time. Longest on record: Slow and failing space creation — 8.1 h (2026-09-15 14:51 UTC). Excluded, never estimated: 1 scheduled maintenance. 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 (21)

StartedIncidentStatusImpactDuration
2026-09-15 14:51 UTCSlow and failing space creationresolvedminor8 h 04 min
2026-09-14 15:35 UTCService Degradation on Existing Workbooksresolvedminor7 h 03 min
2026-09-02 14:34 UTCMapping and other services downresolvedmajor1 h 14 min
2026-06-10 17:28 UTCElevated API latency on US prodresolvedminor0 min
2026-06-10 17:00 UTCFile Extraction Error (UK)resolvednone0 min
2026-05-29 17:10 UTCFile Upload - Unsupported File Typeresolvedminor0 min
2026-05-29 17:06 UTCFile Upload - Unsupported File Typeresolvedminor0 min
2026-04-10 17:24 UTCExperiencing Increased Latencyresolvedminor3 h 00 min
2026-02-02 15:07 UTCInvestigating reports of Mapping Issuesresolvedminor1 h 24 min
2025-12-18 16:31 UTCDegraded Performance on Workbooks and Space Creationresolvedminor1 h 13 min
2025-12-18 13:32 UTCSpaces failing to loadresolvedminor1 h 22 min
2025-11-18 14:06 UTCDNS: Third-Party Service Provider Issueresolvednone1 h 19 min
2025-11-11 19:52 UTCPerformance Degradation: Slowness in Load Times/Timeouts Occurringresolvedminor1 h 32 min
2025-11-06 15:44 UTCIncreased Number of 400 Errorsresolvedminor3 h 09 min
2025-11-04 16:15 UTCPerformance Degradation: Experiencing Long Load Timespostmortemminor2 h 35 min
2025-10-23 10:13 UTCService disruption in EUresolvedminor37 min
2025-09-12 15:32 UTCIntermittent Errors When Accessing Spacesresolvedminor46 min
2025-08-28 18:10 UTCCertification Errorresolvedminor12 min
2025-08-22 03:58 UTCMaintenance: Space Degradationresolvedminor38 min
2025-08-21 18:18 UTCDegraded Service - Network issue on Login Providerresolvedmajor46 min
2025-08-19 23:32 UTCPlatform Slownessresolvedminor2 h 09 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 Flatfile with the template

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

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