Airtable Outage History

Started Jul 08, 2026, 07:17 PM UTC· resolved Jul 08, 2026, 08:59 PM UTC

1. investigating Jul 08, 2026, 07:17 PM UTC

   We are aware of an issue which is causing some Airtable bases to be inaccessible. Our engineers are engaged and are actively working to address this issue.

2. investigating Jul 08, 2026, 07:47 PM UTC

   We have implemented some mitigations and are seeing some improvement, but availability continues to be limited. We will continue to post updates here as we have them.

3. identified Jul 08, 2026, 07:55 PM UTC

   We have implemented a fix and are now seeing substantial recovery. We will continue to post updates here as we have them.

4. monitoring Jul 08, 2026, 08:05 PM UTC

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

5. monitoring Jul 08, 2026, 08:29 PM UTC

   The Airtable site has fully recovered, however we are continuing to leave this incident while we investigate root cause. We will continue to post updates here as we have them.

6. resolved Jul 08, 2026, 08:59 PM UTC

   This incident has been resolved, and we apologize for the inconvenience this issue has caused. Please reach out to [email protected] if you have any further questions.

Read the full incident report →

Started Jun 29, 2026, 06:33 PM UTC· resolved Jun 29, 2026, 07:13 PM UTC

1. investigating Jun 29, 2026, 06:33 PM UTC

   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.

2. monitoring Jun 29, 2026, 06:43 PM UTC

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

3. resolved Jun 29, 2026, 07:13 PM UTC

   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.

Read the full incident report →

Started Jun 08, 2026, 07:44 PM UTC· resolved Jun 08, 2026, 08:00 PM UTC

1. investigating Jun 08, 2026, 07:44 PM UTC

   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.

2. monitoring Jun 08, 2026, 07:52 PM UTC

   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.

3. resolved Jun 08, 2026, 08:00 PM UTC

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

Read the full incident report →

Started Apr 30, 2026, 09:01 AM UTC· resolved Apr 30, 2026, 11:19 AM UTC

1. investigating Apr 30, 2026, 09:01 AM UTC

   We detected a backend issue that could impact availability of up to 0.45% of bases

2. identified Apr 30, 2026, 09:35 AM UTC

   We've identified source of problem and are attempting some mitigation actions

3. identified Apr 30, 2026, 10:35 AM UTC

   Mitigation actions have not yet yielded a recovery. We're engaged with a dependency vendor to perform mitigation actions on their side.

4. monitoring Apr 30, 2026, 10:50 AM UTC

   We've mitigated the issue and are seeing recovery. Bases should now be back online. We will continue to monitor. Automations are still disabled until we confirm full recovery

5. monitoring Apr 30, 2026, 11:19 AM UTC

   We have re-enabled automations as well and everything is functional now

6. resolved Apr 30, 2026, 11:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2026, 06:54 PM UTC· resolved Apr 16, 2026, 07:38 PM UTC

1. investigating Apr 16, 2026, 06:54 PM UTC

   We are seeing issues with Airtable iOS app, our engineering team is investigating the problem.

2. monitoring Apr 16, 2026, 07:28 PM UTC

   We have identified the problem and started the recovery.

3. resolved Apr 16, 2026, 07:38 PM UTC

   This issue has been fully resolved now.

Read the full incident report →

Started Mar 13, 2026, 09:11 PM UTC· resolved Mar 13, 2026, 11:44 PM UTC

1. investigating Mar 13, 2026, 09:11 PM UTC

   We are aware that the Airtable MCP server is currently unavailable. Our engineers are investigating and we will post updates here as we have them.

2. identified Mar 13, 2026, 09:24 PM UTC

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

3. identified Mar 13, 2026, 10:24 PM UTC

   We have prepared a fix and are currently validating it before deploying it to production.

4. identified Mar 13, 2026, 11:00 PM UTC

   We have validated the fix and are deploying it to production now.

5. resolved Mar 13, 2026, 11:44 PM UTC

   A fix has been implemented and the Airtable MCP server is now fully available. Please reach out to Airtable Support if you have any further questions.

Read the full incident report →

Started Mar 11, 2026, 07:01 PM UTC· resolved Mar 12, 2026, 01:19 AM UTC

1. investigating Mar 11, 2026, 07:01 PM UTC

   We are currently investigating this issue.

2. identified Mar 11, 2026, 07:07 PM UTC

   We have identified the issue and are seeing initial signs of recovery. We will continue to post updates here as we have them.

3. identified Mar 11, 2026, 07:31 PM UTC

   The Airtable service has fully recovered, but we will be leaving this incident open while we continue to work on this issue, and will continue to post updates here as we have them.

4. monitoring Mar 11, 2026, 10:03 PM UTC

   A fix has been implemented and the Airtable service continues to be stable. We will continue to closely monitor the service and will post more updates here.

5. resolved Mar 12, 2026, 01:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 06:44 PM UTC· resolved Feb 21, 2026, 01:27 AM UTC

1. investigating Feb 20, 2026, 06:44 PM UTC

   We are aware of an issue impact the availability of the Airtable service. Our engineers are engaged and we will post status updates here.

2. identified Feb 20, 2026, 07:12 PM UTC

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

3. identified Feb 20, 2026, 08:56 PM UTC

   We have begun recovery. Our remediation is still in progress. Some Airtable bases are reachable, and the rest will come online soon.

4. identified Feb 20, 2026, 09:59 PM UTC

   Recovery is continuing. We are on a path to full recovery and are exploring ways to expedite this.

5. identified Feb 20, 2026, 11:16 PM UTC

   Many Airtable bases are now reachable. Some bases and some Airtable features are still broken. We continue to work towards full recovery.

6. monitoring Feb 21, 2026, 01:20 AM UTC

   We have completed the recovery of the primary issue. The vast majority of Airtable functionality is restored. There may be some residual slowness and errors.

7. resolved Feb 21, 2026, 01:27 AM UTC

   Our recovery is complete, and Airtable's service is back to normal.

Read the full incident report →

Started Feb 13, 2026, 05:40 AM UTC· resolved Feb 13, 2026, 07:49 AM UTC

1. investigating Feb 13, 2026, 05:40 AM UTC

   We are currently investigating partial unavailability of Airtable

2. investigating Feb 13, 2026, 06:33 AM UTC

   We have found the root cause and applied a mitigation that restores most base functionality such as read/writes as of 9:45PM PST. However, certain functionality like adding collaborators/shares or creating/deleting applications are still unavailable. We're actively working on restoring that functionality.

3. resolved Feb 13, 2026, 07:49 AM UTC

   We have mitigated the issue as of 10:22 PM PST and all site functionality except billing management should now be working. We are separately working on restoring billing functionality.

Read the full incident report →

Started Feb 12, 2026, 05:29 PM UTC· resolved Feb 13, 2026, 05:06 AM UTC

1. identified Feb 12, 2026, 05:29 PM UTC

   We are aware of an issue impacting non-logged-in users from being able to upload attachments to standalone forms. Our engineers have identified the root cause, and we expect to resolve the issue within the next few hours.

2. monitoring Feb 12, 2026, 09:28 PM UTC

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

3. resolved Feb 13, 2026, 05:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 21, 2026, 10:36 PM UTC· resolved Jan 21, 2026, 11:49 PM UTC

1. investigating Jan 21, 2026, 10:36 PM UTC

   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 are working with our vendor to resolve the issue.

2. identified Jan 21, 2026, 11:01 PM UTC

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

3. resolved Jan 21, 2026, 11:49 PM UTC

   This incident has been resolved, with all systems back to operating normally.

Read the full incident report →

Started Nov 20, 2025, 06:26 PM UTC· resolved Nov 20, 2025, 07:34 PM UTC

1. identified Nov 20, 2025, 06:26 PM UTC

   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.

2. identified Nov 20, 2025, 06:27 PM UTC

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

3. monitoring Nov 20, 2025, 06:49 PM UTC

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

4. resolved Nov 20, 2025, 07:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 30, 2025, 08:48 PM UTC· resolved Oct 31, 2025, 04:43 AM UTC

1. investigating Oct 30, 2025, 08:48 PM UTC

   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.

2. identified Oct 30, 2025, 11:53 PM UTC

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

3. identified Oct 31, 2025, 01:43 AM UTC

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

4. resolved Oct 31, 2025, 04:43 AM UTC

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

Read the full incident report →

Started Oct 20, 2025, 07:25 AM UTC· resolved Oct 21, 2025, 04:51 PM UTC

1. investigating Oct 20, 2025, 07:25 AM UTC

   Airtable is partially unavailable due to an underlying service outage. Our engineering team is investigating and working to bring the service back to a healthy state.

2. investigating Oct 20, 2025, 08:59 AM UTC

   We are continuing to investigate this issue.

3. identified Oct 20, 2025, 09:01 AM UTC

   We have identified the issue with our infrastructure provider and are working with the provider to restore full functionality.

4. monitoring Oct 20, 2025, 11:34 AM UTC

   The underlying issue has been resolved and we are actively monitoring the service recovery.

5. monitoring Oct 20, 2025, 02:35 PM UTC

   Airtable is operational but certain features may experience degraded performance. We are working with our infrastructure provider to address capacity constraints.

6. investigating Oct 20, 2025, 07:02 PM UTC

   Airtable is experiencing a further degradation in performance and increased error rates. We suspect that our infrastructure provider is experiencing a networking issue.

7. monitoring Oct 20, 2025, 08:06 PM UTC

   Airtable's availability and latency have returned to normal. We are no longer observing networking issues with our infrastructure provider. We will continue to monitor for further disruptions as our provider rolls out further mitigations.

8. monitoring Oct 21, 2025, 12:03 AM UTC

   Airtable is operational and functioning within normal boundaries. Our engineering team will continue to monitor our systems, and we will share an update tomorrow morning PDT.

9. resolved Oct 21, 2025, 04:51 PM UTC

   Airtable's systems are back to normal, and this incident is resolved.

Read the full incident report →

Started Sep 25, 2025, 07:09 PM UTC· resolved Sep 25, 2025, 09:37 PM UTC

1. investigating Sep 25, 2025, 07:09 PM UTC

   We are aware of an issue that is causing a subset of bases to be unavailable. Our engineers are engaged and actively investigating this issue. We will post updates here as we have them.

2. monitoring Sep 25, 2025, 09:34 PM UTC

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

3. resolved Sep 25, 2025, 09:37 PM UTC

   All the impacted customer bases should be back and running again.

Read the full incident report →

Started Jul 31, 2025, 05:01 PM UTC· resolved Aug 08, 2025, 08:05 PM UTC

1. identified Jul 31, 2025, 05:01 PM UTC

   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

2. identified Jul 31, 2025, 11:26 PM UTC

   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

3. identified Aug 01, 2025, 07:50 PM UTC

   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

4. identified Aug 05, 2025, 03:35 PM UTC

   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

5. monitoring Aug 06, 2025, 07:29 PM UTC

   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

6. resolved Aug 08, 2025, 08:05 PM UTC

   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

Read the full incident report →

Started Jul 30, 2025, 01:26 AM UTC· resolved Jul 30, 2025, 02:43 AM UTC

1. identified Jul 30, 2025, 01:26 AM UTC

   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

2. resolved Jul 30, 2025, 02:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 28, 2025, 10:54 PM UTC· resolved Jul 29, 2025, 02:13 AM UTC

1. investigating Jul 28, 2025, 10:54 PM UTC

   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

2. identified Jul 28, 2025, 11:04 PM UTC

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

3. resolved Jul 29, 2025, 02:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2025, 01:05 AM UTC· resolved Jul 23, 2025, 01:39 AM UTC

1. identified Jul 23, 2025, 01:05 AM UTC

   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.

2. monitoring Jul 23, 2025, 01:12 AM UTC

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

3. resolved Jul 23, 2025, 01:39 AM UTC

   This has now been resolved.

Read the full incident report →

Started Jun 26, 2025, 10:25 PM UTC· resolved Jun 26, 2025, 10:47 PM UTC

1. investigating Jun 26, 2025, 10:25 PM UTC

   We are aware of an issue which is causing some Airtable bases to be inaccessible. Our engineers are actively engaged and investigating this issue.

2. monitoring Jun 26, 2025, 10:37 PM UTC

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

3. resolved Jun 26, 2025, 10:47 PM UTC

   This incident has been resolved. We apologize for the inconvenience.

Read the full incident report →

Started Jun 04, 2025, 08:43 PM UTC· resolved Jun 04, 2025, 11:57 PM UTC

1. investigating Jun 04, 2025, 08:43 PM UTC

   We are aware of an issue that is causing a subset of bases to be intermittently unavailable. Our engineers are engaged and actively investigating this issue. We will post updates here as we have them.

2. identified Jun 04, 2025, 09:20 PM UTC

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

3. monitoring Jun 04, 2025, 09:23 PM UTC

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

4. resolved Jun 04, 2025, 11:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 16, 2025, 07:48 PM UTC· resolved May 16, 2025, 08:20 PM UTC

1. investigating May 16, 2025, 07:48 PM UTC

   Some customers are having issues loading bases and other Airtable pages. Airtable engineering is investigating.

2. identified May 16, 2025, 07:57 PM UTC

   We have identified the issue and are implementing mitigations

3. resolved May 16, 2025, 08:20 PM UTC

   We have resolved this incident, and Airtable is operating normally again. We deeply apologize for the inconvenience.

Read the full incident report →

Started Apr 30, 2025, 01:12 PM UTC· resolved Apr 30, 2025, 05:28 PM UTC

1. investigating Apr 30, 2025, 01:12 PM UTC

   We are investigating an issue where interface-only users encounter a “Not connected to an automation” message when clicking Interface buttons that trigger published automations. Buttons continue to work normally for users with base access. Our engineering team is working to identify the root cause and restore full functionality. We appreciate your patience and will post updates as soon as more information becomes available.

2. identified Apr 30, 2025, 03:57 PM UTC

   We’ve identified the root cause of the issue causing interface-only users to see “Not connected to an automation” when clicking Interface buttons that trigger automations. Our engineering team is deploying a patch and expects full resolution by 10:00 AM Pacific Time. Interface buttons for users with base access remain unaffected. We’ll confirm once the fix is fully implemented and monitored. Thank you for your patience while we work to restore the service.

3. resolved Apr 30, 2025, 05:28 PM UTC

   We have resolved the issue causing interface-only users to see “Not connected to an automation” when clicking Interface buttons that trigger automations. Interface-only users should be able to trigger automations from interfaces as expected. We apologize for the impact and thank you for your patience.

Read the full incident report →

Started Apr 23, 2025, 03:34 AM UTC· resolved Apr 23, 2025, 02:32 PM UTC

1. investigating Apr 23, 2025, 03:34 AM UTC

   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.

2. identified Apr 23, 2025, 03:55 AM UTC

   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.

3. resolved Apr 23, 2025, 02:32 PM UTC

   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.

Read the full incident report →

Started Apr 08, 2025, 08:01 PM UTC· resolved Apr 08, 2025, 10:16 PM UTC

1. investigating Apr 08, 2025, 08:01 PM UTC

   We are aware of an issue which is causing some "run script" actions in automations to be stuck in the "pending" state indefinitely. Our engineers are investigating now, and we will post more updates here as we have them.

2. monitoring Apr 08, 2025, 09:14 PM UTC

   We have implemented a fix for the "Run Script" action and are observing signs of recovery. Our team is actively monitoring the situation to ensure full restoration of functionality. Thank you for your patience and understanding.

3. resolved Apr 08, 2025, 10:16 PM UTC

   The issue affecting the "Run Script" action has been resolved. Our system is processing the backlog, and all pending automations will be completed. If you experienced any script failures during the outage, you can manually retrigger those automations. Thank you for your patience and understanding as we work to ensure everything returns to normal. We appreciate your continued support.

Read the full incident report →