52 recorded Codaio incidents since April 2018, with official updates, affected components, duration and resolution information.
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.
The incident has been resolved.
We're currently working on a fix for an issue that manifests in slow performance of Superhuman Docs. Users may experience delays when loading, editing, or saving documents. Our team is actively looking into the issue and working to restore normal performance as quickly as possible. We'll post an update as soon as we have more information. Thank you for your patience.
A fix has been implemented, and we're monitoring the results.
This incident has been resolved.
We have identified an issue affecting access to coda.io and login to the Coda service through superhuman.com. This may be related to a temporary Amazon CloudFront outage. We apologize for any inconvenience, and updates will be provided as they become available.
The issue has been identified.
We introduced temporary changes to mitigate this issue during CloudFront's outage. Access to coda.io and Coda via superhuman.com should now be restored. We are monitoring the results.
Amazon has resolved the CloudFront service outage, and our services are back to normal.
We are currently investigating this issue.
This incident has been resolved.
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.
We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
We're aware of an issue affecting doc size and resulting in formula calculations being disabled unexpectedly in some docs. We are currently investigating
This incident has been resolved.
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.
The issue is now resolved and all sign-in options are available again.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
We are currently investigating this issue.
We have identified the issue and are working with Google on a resolution.
This incident has been resolved.
We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.
This incident has been resolved.
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.
This incident has been resolved.
We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.
This incident has been resolved.
We have identified an issue affecting access to Coda and are working on fixing it as quickly as possible.
This incident has been resolved.
