Slow and failing space creation
Timeline · 2 updates
- investigating Sep 15, 2026, 02:51 PM UTC
We are currently investigating this issue.
- resolved Sep 15, 2026, 10:55 PM UTC
This incident has been resolved.
Flatfile had 15 outages in the last 2 years totaling 32h 36m of downtime — averaging 0.6 incidents per month.
There were 15 Flatfile outages since October 23, 2025 totaling 32h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
Existing workbooks are slow or degraded when restored from storage. We are investigating the root cause.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Mapping and other services are down. We are investigating the issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Timestamp: 16:46 UTC to 17:25 UTC
Retroactive: Occurred Tue Jun 9, 2026 16:48:14 UTC to Wed Jun 10, 2026 12:02 UTC , Resolved
2026-05-29 13:45 UTC to 14:12 UTC Customers experienced intermittent failures when uploading and processing workbook files. The issue was traced to elevated resource utilization on internal processing workers, which caused a backlog in our job queue and prevented files from completing extraction. Our team identified the problem, restarted the affected services, and confirmed full restoration of functionality. We are implementing infrastructure improvements to prevent recurrence under similar load conditions.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of degraded performance with mapping in spaces.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating reports of space initialization and creation issues
We have identified the root cause and a fix is currently being rolled out
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
The incident has been resolved.
An issue with one of our third-party service providers
A fix has been implemented and we are monitoring the recovery.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue where some users are seeing an increased number of 400 errors from the API with the message "remaining connection slots are reserved for roles with the SUPERUSER attribute".
We are no longer seeing these errors however we are continuing to investigate the cause.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of a service degredation on our EU platform region
We have identified the issue and are rolling out a fix
A fix has