Airtable Outage History

This incident has been resolved. We apologize for any inconvenience this may have caused you. Please reach out to the Airtable Support team if you have any questions about this incident.

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

We are aware of an issue which is causing some requests to Airtable to have elevated latencies. Our engineers were automatically alerted to this issue and are actively working to address the root cause.

This incident has been resolved, and the Airtable service is again operating normally. We apologize for any disruption this issue caused.

A fix has been implemented and we are seeing signs of recovery. We will continue to monitor this issue to ensure it does not recur.

We are aware of an issue which is causing some requests to Airtable to have elevated latencies. Our engineers were automatically alerted to this issue and are actively working to address the root cause.

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

We are responding to an incident where fewer than 1% of bases are periodically experiencing increased errors and latency due to an underlying database issue. We have identified the issue and our engineering team is working to resolve this.

We have resolved this incident. We’re sorry for the inconvenience.

We are rolling out a fix and will update the status page when we've confirmed resolution of the issue.

The issue has been identified, and we're working on a fix. We expect a resolution by early next week.

We are aware of an issue impacting “Push Updates” for Managed apps and components (https://support.airtable.com/docs/using-app-library-and-components-in-airtable#pushing-updates-to-bases), and have temporarily disabled this capability. We will re-enable this capability once a fix is identified and deployed.

Atlassian’s engineering team has implemented a temporary fix that has successfully addressed the API rate limiting behavior impacting Airtable–Jira syncs. With this intervention in place, sync operations are now functioning as expected. Our teams will continue collaborating closely to monitor performance and support Atlassian in delivering a long-term solution. We appreciate your patience as we worked to restore full functionality and ensure a stable integration experience. — The Airtable Team

We’ve implemented changes to reduce the impact of Jira Cloud API rate limiting, including throttling sync API calls and optimizing sync behavior to reduce load. These mitigation efforts have led to a noticeable reduction in rate limiting errors across impacted Airtable–Jira syncs. We’re continuing to monitor system performance closely to ensure stability, while Atlassian continues their investigation into the unexpected rate limit behavior to provide a long-term resolution. If you're still experiencing sync-related issues, please reach out to your Airtable support representative so we can assist further. — The Airtable Team

We’re continuing to work closely with Atlassian to address the Jira Cloud API rate limiting issue impacting some Airtable–Jira syncs. Our team remains actively engaged and is implementing mitigation strategies while collaborating with Atlassian to clarify rate limit behavior and ensure a stable experience going forward. If you're encountering sync issues, please reach out to your Airtable support representative — we’re here to help. We’ll continue to provide updates as more information becomes available. — The Airtable Team

Atlassian’s engineering team is now actively investigating the unexpected enforcement of Jira Cloud API rate limits. In parallel, Airtable engineers are implementing short-term mitigations to reduce API usage from our Jira connector. These are being applied on a best-effort, case-by-case basis. If you're experiencing failed syncs due to rate limiting, please reach out to your Airtable support representative so we can apply mitigation steps specific to your case. We’ll continue to provide updates as the situation evolves. — The Airtable Team

We’ve made initial contact with Atlassian regarding the unexpected enforcement of Jira Cloud API rate limits and are currently escalating the issue to their team for resolution. In parallel, our engineering team is actively working on workarounds to reduce the impact on Airtable-Jira syncs, especially for larger projects. We’ll continue to provide updates as we learn more. Thank you for your continued patience. — The Airtable Team

We’re currently investigating an issue affecting some Airtable-Jira syncs. Our team has identified that the root cause is related to newly enabled Jira Cloud API rate limiting by Atlassian, which was activated ahead of their previously communicated timeline. As a result, larger Jira Cloud syncs may experience delays or partial failures. We are actively working on mitigation strategies to minimize disruption for affected users and will provide further updates as we implement improvements. We appreciate your patience and will share more information as it becomes available. — The Airtable Team

This incident has been resolved.

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

We are aware of an issue where Jira server(Datacenter) syncs are failing, for all customers with Jira syncs set up. Our engineering teams are currently investigating

This has now been resolved.

We have rolled back the changes and are monitoring. Errors from Script Automation Actions should no longer be happening.

We are aware that Script Automation Actions are currently failing. We’ve traced the issue to a recent release and have started rolling it back. Other automation actions remain unaffected.

We're pleased to report that the issue affecting the Box and Hootsuite syncs to Airtable has been resolved. Our recent hotfix has been successfully deployed overnight, and both syncs should now be functioning as expected. Thank you for your patience and understanding as we addressed this matter.

We have identified the root cause of the issue affecting the Box and Hootsuite syncs to Airtable. Our engineering team has developed a hotfix and is currently in the process of deploying it. We are closely monitoring the situation and will confirm once the fix has been fully implemented. We appreciate your patience and understanding as we work to restore seamless service. Thank you for bearing with us.

We’re aware that users are currently experiencing issues with the Box and Hootsuite syncs to Airtable. Our engineering team is actively investigating the problem and working to identify the underlying cause. We understand the impact this may have on your workflows and are prioritizing a resolution. We appreciate your patience and will provide updates as more information becomes available.

The issue with our Automation Run History feature has been resolved. We apologize for any inconvenience this may have caused. If you encounter any further issues, please reach out to our support team. Thank you for your patience and understanding.

We are currently experiencing an issue with our Automation Run History feature, which has been temporarily disabled. Our team is actively working to resolve this and restore full functionality as soon as possible. Please note that creating, editing, and running automations are not impacted and continue to function normally. However, if you have the Automation History page open, you may encounter an error. To continue editing your automation, please close the Automation History page and refresh your browser. We apologize for any inconvenience this may cause and appreciate your patience. Please stay tuned for further updates. Thank you for your understanding.

Jira sync functionality has been restored. Thank you for your patience.

We explored a workaround to the bug and will be working to deploy and restore the functionality before end of day. Please stay tuned for more updates. Our team will continue working with Jira's support team to find a long term resolution in the mean time. Thank you for your patience.

We are currently investigating an issue affecting some Jira Syncs in Airtable. Due to a bug in Jira’s APIs, certain syncs are only fetching 100 rows of data instead of the full dataset. This issue began at 2:00 AM PST. We have reached out to Jira’s support team for assistance and are also proactively exploring potential workarounds. We will provide further updates as soon as we have more information. Thank you for your patience while we work to resolve this issue.

This incident has been resolved.

Our Airtable Facebook automation is currently not functional. We are actively working with Meta to restore its functionality. Thank you for your patience and understanding.

Thank you for your patience. Slack has resolved the main messaging outage for all users and is continuing to restore other features. We've observed that our automation Slack actions are now functioning properly. If your automations were affected, we recommend checking the run history and manually retrying them to resend your Slack messages.

We're aware that the Slack outage is ongoing, and some users are still affected. We are closely monitoring Slack's progress in restoring full service. This incident will remain open until we can confirm that Slack is fully operational for all our users. Thank you for your patience and understanding.

Our team is closely monitoring the ongoing Slack outage and has observed a gradual restoration of service. Unfortunately, due to the extended downtime, automations sending Slack messages have exhausted their retry attempts and failed during this period. Automation owners have been notified via email about these failures. We recommend checking the run history and manually retrying the automations to resend your Slack messages. Thank you for your patience and understanding.

Airtable slack automation are currently impacted by the slack outage and are failing. The team is closely monitoring slack status. Please stay tuned.

We have resolved this incident.

We have implemented a fix to scripting extensions, and we are monitoring to verify that everything is working again. We deeply apologize for the disruption and will continue to keep you updated on our progress.

We are aware of an issue impacting scripting extensions. Our engineers are actively investigating and identifying a fix as soon as possible. We apologize for the inconvenience this has caused.

This incident has been resolved.

The issue has been resolved

We are aware of an issue that is impacting the detailed configuration of certain types of automation actions. Existing automations continue to work as expected, and automations can be enabled or disabled as usual. Our engineers have identified the root cause and expect to have a fix implemented in the next hour.