Flatfile status history
Current state: operational — “All Systems Operational” per https://status.flatfile.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Flatfile incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-15 14:51 UTC | Slow and failing space creation | resolved | minor | 8 h 04 min |
| 2026-09-14 15:35 UTC | Service Degradation on Existing Workbooks | resolved | minor | 7 h 03 min |
| 2026-09-02 14:34 UTC | Mapping and other services down | resolved | major | 1 h 14 min |
| 2026-06-10 17:28 UTC | Elevated API latency on US prod | resolved | minor | 0 min |
| 2026-06-10 17:00 UTC | File Extraction Error (UK) | resolved | none | 0 min |
| 2026-05-29 17:10 UTC | File Upload - Unsupported File Type | resolved | minor | 0 min |
| 2026-05-29 17:06 UTC | File Upload - Unsupported File Type | resolved | minor | 0 min |
| 2026-04-10 17:24 UTC | Experiencing Increased Latency | resolved | minor | 3 h 00 min |
| 2026-02-02 15:07 UTC | Investigating reports of Mapping Issues | resolved | minor | 1 h 24 min |
| 2025-12-18 16:31 UTC | Degraded Performance on Workbooks and Space Creation | resolved | minor | 1 h 13 min |
| 2025-12-18 13:32 UTC | Spaces failing to load | resolved | minor | 1 h 22 min |
| 2025-11-18 14:06 UTC | DNS: Third-Party Service Provider Issue | resolved | none | 1 h 19 min |
| 2025-11-11 19:52 UTC | Performance Degradation: Slowness in Load Times/Timeouts Occurring | resolved | minor | 1 h 32 min |
| 2025-11-06 15:44 UTC | Increased Number of 400 Errors | resolved | minor | 3 h 09 min |
| 2025-11-04 16:15 UTC | Performance Degradation: Experiencing Long Load Times | postmortem | minor | 2 h 35 min |
| 2025-10-23 10:13 UTC | Service disruption in EU | resolved | minor | 37 min |
| 2025-09-12 15:32 UTC | Intermittent Errors When Accessing Spaces | resolved | minor | 46 min |
| 2025-08-28 18:10 UTC | Certification Error | resolved | minor | 12 min |
| 2025-08-22 03:58 UTC | Maintenance: Space Degradation | resolved | minor | 38 min |
| 2025-08-21 18:18 UTC | Degraded Service - Network issue on Login Provider | resolved | major | 46 min |
| 2025-08-19 23:32 UTC | Platform Slowness | resolved | minor | 2 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
}