История сбоев Flatfile

1. 15 сентября 2026 г. в 14:51 UTCinvestigating

   В настоящее время мы расследуем этот вопрос.

2. 15 сентября 2026 г. в 22:55 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 14 сентября 2026 г. в 15:35 UTCinvestigating

   Существующие рабочие книги медленно или ухудшаются при восстановлении из хранилища. Мы расследуем первопричину.

2. 14 сентября 2026 г. в 20:41 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 14 сентября 2026 г. в 22:38 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 2 сентября 2026 г. в 14:54 UTCinvestigating

   Картографирование и другие услуги отключены. Мы расследуем этот вопрос.

2. 2 сентября 2026 г. в 15:29 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 2 сентября 2026 г. в 15:39 UTCmonitoring

   Мы продолжаем отслеживать любые дополнительные проблемы.

4. 2 сентября 2026 г. в 15:48 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 10 июня 2026 г. в 17:28 UTCresolved

   Timestamp: 16:46 UTC to 17:25 UTC

1. 10 июня 2026 г. в 17:00 UTCresolved

   Retroactive: Occurred Tue Jun 9, 2026 16:48:14 UTC to Wed Jun 10, 2026 12:02 UTC , Resolved

1. 29 мая 2026 г. в 17:10 UTCresolved

   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.

1. 29 мая 2026 г. в 17:06 UTCresolved

   2026-05-28 23:14 UTC to 2026-05-29 00:19 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.

1. 10 апреля 2026 г. в 17:24 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 10 апреля 2026 г. в 20:17 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10 апреля 2026 г. в 20:24 UTCresolved

   This incident has been resolved.

1. 2 февраля 2026 г. в 15:07 UTCinvestigating

   We are currently investigating reports of degraded performance with mapping in spaces.

2. 2 февраля 2026 г. в 16:32 UTCresolved

   This incident has been resolved.

1. 18 декабря 2025 г. в 16:31 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 18 декабря 2025 г. в 16:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 18 декабря 2025 г. в 17:44 UTCresolved

   This incident has been resolved.

1. 18 декабря 2025 г. в 13:32 UTCinvestigating

   We are investigating reports of space initialization and creation issues

2. 18 декабря 2025 г. в 13:38 UTCidentified

   We have identified the root cause and a fix is currently being rolled out

3. 18 декабря 2025 г. в 14:01 UTCidentified

   A fix has been implemented and we are monitoring the results.

4. 18 декабря 2025 г. в 14:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 18 декабря 2025 г. в 14:54 UTCresolved

   The incident has been resolved.

1. 18 ноября 2025 г. в 14:06 UTCinvestigating

   An issue with one of our third-party service providers

2. 18 ноября 2025 г. в 15:12 UTCmonitoring

   A fix has been implemented and we are monitoring the recovery.

3. 18 ноября 2025 г. в 15:25 UTCresolved

   This incident has been resolved.

1. 11 ноября 2025 г. в 19:52 UTCinvestigating

   We are currently investigating this issue.

2. 11 ноября 2025 г. в 19:56 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 ноября 2025 г. в 20:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11 ноября 2025 г. в 21:25 UTCresolved

   This incident has been resolved.

1. 6 ноября 2025 г. в 15:44 UTCinvestigating

   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".

2. 6 ноября 2025 г. в 16:24 UTCinvestigating

   We are no longer seeing these errors however we are continuing to investigate the cause.

3. 6 ноября 2025 г. в 16:44 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 6 ноября 2025 г. в 16:49 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 6 ноября 2025 г. в 18:53 UTCresolved

   This incident has been resolved.

1. 4 ноября 2025 г. в 16:15 UTCinvestigating

   We are currently investigating this issue.

2. 4 ноября 2025 г. в 16:51 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 4 ноября 2025 г. в 16:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 4 ноября 2025 г. в 17:33 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 ноября 2025 г. в 18:51 UTCresolved

   This incident has been resolved.

6. 7 ноября 2025 г. в 16:17 UTCpostmortem

   # Incident Overview **Date and Time of Incident:** November 4 08:15 PST - 10:51 PST **Nature of Incident:** Exhausted Database Connections due to Thawing Expired Workbooks **Services Affected:** Flatfile Platform US Region ## Details of the Incident On November 4 a daily event expired a large number of workbooks. Many of the expired workbooks had been backed up and moved to cold storage. The expiry event caused these workbooks to first thaw before being marked as expired and purged. This led to elevated database connections growing for a period of time that ultimately exhausted database resources at approximately 8:15 PST. This caused intermittent service degradations across the platform that manifested as API requests randomly failing when the API was unable to open a database connection. Flatfile engineering took steps to short circuit the thawing process for expired workbooks and hardened the thaw process so that a large number of workbooks moving from cold storage to “hot” storage would not spike database resources. ## Impact Assessment During the incident window, some API requests would randomly fail leading to unpredictable behavior across the Platform. ## Root Cause The data retention policy feature allows a customer to automatically purge workbooks that have not been active in a set amount of days. This feature would run on a cron-like basis to identify and purge workbooks. It was discovered that this conflicted with the cold storage system for workbooks where any workbook that was backed up and moved to “cold” storage \(S3 backup\) would first be “thawed” and moved into “hot” storage. In the early morning of the 4th, a large number of workbooks in cold storage were identified for expiry and several thousand workbooks entered the queue to await thaw. Over the course of several hours, the database connection pool became saturated causing API requests to intermittently fail while also causing workbooks in the thaw process to fail and be re-enqueued which exacerbated the connection pool problem. ## Resolution Flatfile engineering took steps to implement a short circuit for expired workbooks to resolve the immediate symptoms. The engineering team followed up with a series of steps to harden the queue, the database connection pool, and the thaw mechanism as well. ## Security and Data Integrity Please be assured that this incident did not compromise the security or integrity of your data. Our commitment to data protection remains a top priority.

1. 23 октября 2025 г. в 10:13 UTCinvestigating

   We are currently investigating reports of a service degredation on our EU platform region

2. 23 октября 2025 г. в 10:22 UTCidentified

   We have identified the issue and are rolling out a fix

3. 23 октября 2025 г. в 10:51 UTCresolved

   A fix has

1. 12 сентября 2025 г. в 15:55 UTCinvestigating

   We are currently investigating an issue where some users are seeing an "Unknown Error" when launching a space. We are investigating this issue however refreshing the page seems to resolve this error.

2. 12 сентября 2025 г. в 16:10 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 сентября 2025 г. в 16:12 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 12 сентября 2025 г. в 16:19 UTCresolved

   This incident has been resolved.

1. 28 августа 2025 г. в 18:10 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 28 августа 2025 г. в 18:18 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 28 августа 2025 г. в 18:22 UTCresolved

   This incident has been resolved.

1. 22 августа 2025 г. в 03:58 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 22 августа 2025 г. в 04:32 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 22 августа 2025 г. в 04:36 UTCresolved

   This incident has been resolved.

1. 21 августа 2025 г. в 18:18 UTCidentified

   Our login vendor is experiencing issues. Some dashboards will be effected for US users. Thank you for your patience while this is resolved.

2. 21 августа 2025 г. в 18:34 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 21 августа 2025 г. в 19:05 UTCresolved

   This incident has been resolved.