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

1. 13 августа 2026 г. в 16:36 UTCinvestigating

   We're investigating reports that creating packs and docs via pack.new and coda.new isn't working. You can still create new packs and docs by logging in to Superhuman Docs at https://docs.superhuman.com/. We'll provide updates as they become available.

2. 14 августа 2026 г. в 18:16 UTCresolved

   The incident has been resolved.

1. 29 июля 2026 г. в 17:38 UTCidentified

   В настоящее время мы работаем над исправлением проблемы, которая проявляется в медленной работе сверхчеловеческих документов. Пользователи могут испытывать задержки при загрузке, редактировании или сохранении документов. Наша команда активно изучает проблему и работает над тем, чтобы как можно быстрее восстановить нормальную производительность. Мы опубликуем обновление, как только у нас будет больше информации. Спасибо за ваше терпение.

2. 29 июля 2026 г. в 18:05 UTCmonitoring

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

3. 29 июля 2026 г. в 18:16 UTCresolved

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

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

1. 16 июля 2026 г. в 08:56 UTCinvestigating

   Мы выявили проблему, затрагивающую доступ к coda.io и вход в сервис Coda через superhuman.com. Это может быть связано с временным отключением Amazon CloudFront. Мы приносим извинения за любые неудобства, и обновления будут предоставляться по мере их поступления.

2. 16 июля 2026 г. в 09:00 UTCidentified

   Вопрос был выявлен.

3. 16 июля 2026 г. в 09:11 UTCmonitoring

   Мы внесли временные изменения, чтобы смягчить эту проблему во время отключения CloudFront. Теперь доступ к coda.io и Coda через superhuman.com должен быть восстановлен. Мы следим за результатами.

4. 16 июля 2026 г. в 13:15 UTCresolved

   Amazon разрешила отключение сервиса CloudFront, и наши сервисы вернулись к нормальному состоянию.

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

1. 22 мая 2026 г. в 02:11 UTCinvestigating

   We are currently investigating this issue.

2. 24 мая 2026 г. в 04:52 UTCresolved

   This incident has been resolved.

1. 7 мая 2026 г. в 14:15 UTCresolved

   We identified an issue with Claude's desktop and web connections to Coda MCP. The issue has been resolved, and you should now be able to set up connections. If you set up any connections before May 4, you may need to reconnect the Coda MCP in Claude. Find more instructions here: https://help.coda.io/hc/en-us/articles/44722661982989.

1. 20 января 2026 г. в 21:34 UTCinvestigating

   We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.

2. 20 января 2026 г. в 22:05 UTCresolved

   This incident has been resolved.

1. 20 октября 2025 г. в 18:09 UTCidentified

   Coda has been experiencing an outage that is preventing the scanning of attachments and images for viruses. This outage is causing a delay in processing images and attachments into the document. Any uploaded images and attachments have been stored on our servers successfully, but we are experiencing a delay in processing them to deem them safe to provide to other collaborators of your document. Once the AWS + Scanii issues are resolved, it is expected that all images and attachments previously uploaded will become available to collaborators across docs. We are monitoring the situation and hope to have a resolution shortly.

2. 20 октября 2025 г. в 20:08 UTCresolved

   This incident has been resolved.

1. 1 октября 2025 г. в 18:12 UTCidentified

   There is an ongoing issue that prevents Coda doc links from being unfurled correctly when posted within Slack. This ongoing issue also impacts sharing modifications that would otherwise work within the Slack integration. We are aware of the issue and we are working to resolve the issue.

2. 1 октября 2025 г. в 21:12 UTCresolved

   This incident has been resolved.

1. 12 августа 2025 г. в 18:59 UTCinvestigating

   We're aware of an issue affecting doc size and resulting in formula calculations being disabled unexpectedly in some docs. We are currently investigating

2. 13 августа 2025 г. в 00:33 UTCresolved

   This incident has been resolved.

1. 1 июля 2025 г. в 05:53 UTCidentified

   The sign-in web pages currently only show SSO as an option due to a code change that was deployed today. We are currently working to deploy a fix for this change. The issue is expected to be resolved within one hour.

2. 1 июля 2025 г. в 06:48 UTCresolved

   The issue is now resolved and all sign-in options are available again.

1. 7 марта 2025 г. в 03:35 UTCinvestigating

   We have identified an issue with sending emails to users and are currently working on a fix. In the meantime, users might not be able to receive some emails from us, including but not limited to: sign ups, password-less logins, invitations, mentions, and document shares.

2. 7 марта 2025 г. в 05:59 UTCresolved

   This incident has been resolved.

1. 6 марта 2025 г. в 16:50 UTCidentified

   We have identified an issue with sending emails to users and are currently working on a fix. In the meantime, users might not be able to receive some emails from us, including but not limited to: sign ups, password-less logins, invitations, mentions, and document shares.

2. 6 марта 2025 г. в 18:53 UTCresolved

   This incident has been resolved.

1. 29 января 2025 г. в 04:24 UTCinvestigating

   There is currently an issue degrading performance across doc writes through the API server and with doc processing. We are investigating this issue and expect it to be resolved within 30 minutes.

2. 29 января 2025 г. в 05:50 UTCresolved

   This incident has been resolved.

1. 10 января 2025 г. в 04:31 UTCidentified

   We are currently experiencing an outage that is preventing the scanning of attachments and images for viruses. This outage is causing a delay in processing images and attachments into the document. Any uploaded images and attachments have been stored on our servers successfully, but we are experiencing a delay in processing them to deem them safe to provide to other collaborators of your document. We are monitoring the situation and hope to have a resolution shortly.

2. 10 января 2025 г. в 15:25 UTCresolved

   This incident has been resolved.

1. 10 декабря 2024 г. в 07:28 UTCidentified

   We are currently experiencing an outage with a dependent service to scan attachments and images for viruses (scanii). This outage is causing a delay to process images and attachments into the doc. Any uploaded image and attachment has been stored on our servers successfully but we are experiencing a delay with processing the attachments and images to deem them as safe to provide to other collaborators of your document. We are monitoring the situation and hope to have a resolution shortly.

2. 12 декабря 2024 г. в 23:59 UTCresolved

   This incident has been resolved.

1. 25 июля 2024 г. в 22:16 UTCinvestigating

   We are currently investigating this issue.

2. 25 июля 2024 г. в 22:23 UTCinvestigating

   We have identified the issue and are working with Google on a resolution.

3. 26 июля 2024 г. в 18:20 UTCresolved

   This incident has been resolved.

1. 26 марта 2024 г. в 19:40 UTCinvestigating

   We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.

2. 26 марта 2024 г. в 19:51 UTCresolved

   This incident has been resolved.

1. 1 марта 2024 г. в 18:27 UTCinvestigating

   We have identified an issue affecting connectivity to docs within Coda causing docs to show as "Offline" and are working on fixing it as quickly as possible. Docs will continue to work in the offline mode though and edits will be saved when docs connect again online.

2. 1 марта 2024 г. в 18:48 UTCresolved

   This incident has been resolved.

1. 3 ноября 2023 г. в 02:59 UTCinvestigating

   We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.

2. 3 ноября 2023 г. в 04:13 UTCresolved

   This incident has been resolved.

1. 3 ноября 2023 г. в 02:50 UTCinvestigating

   We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.

2. 3 ноября 2023 г. в 02:51 UTCresolved

   This incident has been resolved.