Airtable

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 19:17 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 2026-07-08 19:47 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 2026-07-08 19:55 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 2026-07-08 20:05 UTC

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

5. monitoring 2026-07-08 20:29 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 2026-07-08 20:59 UTC

   This incident has been resolved, and we apologize for the inconvenience this issue has caused. Please reach out to support@airtable.com if you have any further questions.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 18:33 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 2026-06-29 18:43 UTC

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

3. resolved 2026-06-29 19:13 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.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-08 19:44 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 2026-06-08 19:52 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 2026-06-08 20:00 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-30 09:01 UTC

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

2. identified 2026-04-30 09:35 UTC

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

3. identified 2026-04-30 10:35 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 2026-04-30 10:50 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 2026-04-30 11:19 UTC

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

6. resolved 2026-04-30 11:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-16 18:54 UTC

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

2. monitoring 2026-04-16 19:28 UTC

   We have identified the problem and started the recovery.

3. resolved 2026-04-16 19:38 UTC

   This issue has been fully resolved now.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-13 21:11 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 2026-03-13 21:24 UTC

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

3. identified 2026-03-13 22:24 UTC

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

4. identified 2026-03-13 23:00 UTC

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

5. resolved 2026-03-13 23:44 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.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-11 19:01 UTC

   We are currently investigating this issue.

2. identified 2026-03-11 19:07 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 2026-03-11 19:31 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 2026-03-11 22:03 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 2026-03-12 01:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-20 18:44 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 2026-02-20 19:12 UTC

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

3. identified 2026-02-20 20:56 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 2026-02-20 21:59 UTC

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

5. identified 2026-02-20 23:16 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 2026-02-21 01:20 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 2026-02-21 01:27 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-13 05:40 UTC

   We are currently investigating partial unavailability of Airtable

2. investigating 2026-02-13 06:33 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...

3. resolved 2026-02-13 07:49 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.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-12 17:29 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 2026-02-12 21:28 UTC

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

3. resolved 2026-02-13 05:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-21 22:36 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 2026-01-21 23:01 UTC

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

3. resolved 2026-01-21 23:49 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-20 18:26 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 2025-11-20 18:27 UTC

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

3. monitoring 2025-11-20 18:49 UTC

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

4. resolved 2025-11-20 19:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-30 20:48 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...

2. identified 2025-10-30 23:53 UTC

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

3. identified 2025-10-31 01:43 UTC

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

4. resolved 2025-10-31 04:43 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 07:25 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 2025-10-20 08:59 UTC

   We are continuing to investigate this issue.

3. identified 2025-10-20 09:01 UTC

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

4. monitoring 2025-10-20 11:34 UTC

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

5. monitoring 2025-10-20 14:35 UTC

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

6. investigating 2025-10-20 19:02 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 2025-10-20 20:06 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 2025-10-21 00:03 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 2025-10-21 16:51 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-25 19:09 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 2025-09-25 21:34 UTC

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

3. resolved 2025-09-25 21:37 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-31 17:01 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...

2. identified 2025-07-31 23:26 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...

3. identified 2025-08-01 19:50 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,...

4. identified 2025-08-05 15:35 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...

5. monitoring 2025-08-06 19:29 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...

6. resolved 2025-08-08 20:05 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...

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-07-30 01:26 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 2025-07-30 02:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-28 22:54 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 2025-07-28 23:04 UTC

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

3. resolved 2025-07-29 02:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-23 01:05 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 2025-07-23 01:12 UTC

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

3. resolved 2025-07-23 01:39 UTC

   This has now been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-26 22:25 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 2025-06-26 22:37 UTC

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

3. resolved 2025-06-26 22:47 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-04 20:43 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 2025-06-04 21:20 UTC

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

3. monitoring 2025-06-04 21:23 UTC

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

4. resolved 2025-06-04 23:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-16 19:48 UTC

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

2. identified 2025-05-16 19:57 UTC

   We have identified the issue and are implementing mitigations

3. resolved 2025-05-16 20:20 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-30 13:12 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...

2. identified 2025-04-30 15:57 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...

3. resolved 2025-04-30 17:28 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...

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-23 03:34 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...

2. identified 2025-04-23 03:55 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...

3. resolved 2025-04-23 14:32 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...

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-08 20:01 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 2025-04-08 21:14 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 2025-04-08 22:16 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...

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-03-28 17:36 UTC

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

2. resolved 2025-03-28 21:27 UTC

   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.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-03-11 23:59 UTC

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

2. identified 2025-03-12 16:46 UTC

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

3. resolved 2025-03-13 03:18 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-03-11 02:59 UTC

   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.

2. resolved 2025-03-11 05:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-28 17:56 UTC

   We are aware of an issue which is causing errors to be shown when dragging and dropping attachments into grid view cells. We are actively working on fixing this issue, but in the meantime you can work around this issue by using the "browse files" dialog.

2. identified 2025-02-28 17:58 UTC

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

3. resolved 2025-02-28 20:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-26 16:54 UTC

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

2. monitoring 2025-02-26 18:51 UTC

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

3. monitoring 2025-02-27 00:19 UTC

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

4. resolved 2025-02-27 01:58 UTC

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

Excerpts are shortened. Read the full incident on Airtable's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-21 22:35 UTC

   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.

2. monitoring 2025-01-21 22:57 UTC

   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.

3. resolved 2025-01-21 23:17 UTC

   We have resolved this incident.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-08 19:13 UTC

   Airtable’s services are currently unavailable for some customers. Our engineers are actively investigating this downtime incident, and will keep you informed as updates are available. We apologize for the inconvenience this has caused.

2. monitoring 2025-01-08 19:22 UTC

   We have implemented a fix to resolve the issues some customers are having when accessing Airtable, and we are monitoring the results. Until we confirm the incident is fully resolved, these customers may continue experiencing downgraded service. We deeply apologize for the...

3. resolved 2025-01-08 19:34 UTC

   We have resolved this incident, and Airtable’s services are functioning normally. We’re sorry for any inconvenience this has caused.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-11-21 18:30 UTC

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

2. identified 2024-11-21 21:14 UTC

   The issue has been resolved

3. resolved 2024-11-21 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-11-11 18:16 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. resolved 2024-11-11 18:50 UTC

   We have resolved this incident. We apologize for the interruption to our customers’ operations.

Excerpts are shortened. Read the full incident on Airtable's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-23 18:24 UTC

   We are aware of an issue that is causing an increase in errors when making calls to the Airtable public API. Our engineers are engaged and we are investigating.

2. investigating 2024-10-23 18:54 UTC

   Note that this incident is also affecting custom scripting actions. We are actively working on remediating this issue and will continue to post updates here.

3. monitoring 2024-10-23 19:10 UTC

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

4. resolved 2024-10-23 20:31 UTC

   This incident has been resolved. We apologize for the disruption this may have caused you. Please reach out to Airtable support or your account team if you have any questions about this incident.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-26 16:26 UTC

   We are aware of an issue which is impacting the stability of a small number of bases, particularly large bases. Our engineers are actively investigating this issue and will provide updates here as we have them.

2. identified 2024-09-26 17:29 UTC

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

3. monitoring 2024-09-26 17:40 UTC

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

4. resolved 2024-09-26 18:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-09-10 01:58 UTC

   We are investigating reports that some customers in asia-pacific have difficulty accessing airtable.com.

2. monitoring 2024-09-10 02:35 UTC

   The issue appears to be caused by network connectivity between internet providers in APAC. Customer affected can use a VPN to connect to airtable.com.

3. monitoring 2024-09-10 02:42 UTC

   The issue appears to be caused by network connectivity between internet providers in APAC region. Customers affected can use a VPN to connect to airtable.com.

4. resolved 2024-09-10 04:41 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-09-03 20:26 UTC

   Some customers might have encountered issues loading the data or automations tab. This issue has been resolved now. We’re sorry for the inconvenience to our customers’ operations.

Excerpts are shortened. Read the full incident on Airtable's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-02 15:20 UTC

   We are aware of an issue that is causing slow loading and other issues with a very small percentage of bases. Our engineers have identified the root cause of the issue and are working on a remediation.

2. resolved 2024-09-02 15:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-30 15:24 UTC

   Airtable's service is currently experiencing increased error rates. Engineering has implemented a mitigation that we expect to resolve the issue soon.

2. resolved 2024-08-30 15:34 UTC

   We have mitigated this issue, and Airtable's service is now operating normally. We apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Airtable's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-16 18:23 UTC

   Airtable's service is currently experiencing increased error rates. Engineering has implemented a mitigation that we expect to resolve the issue soon.

2. resolved 2024-08-16 18:29 UTC

   Our mitigation is complete, and Airtable's service is now operating normally. We deeply apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-16 02:17 UTC

   Airtable's service is currently experiencing increased error rates and latency. Engineering is responding and implementing mitigations. We expect resolution soon.

2. resolved 2024-08-16 03:15 UTC

   Our mitigation is complete, and Airtable's service is now operating normally. We deeply apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-08 18:19 UTC

   Airtable's service is currently experiencing increased error rates. Engineering is responding and implementing mitigations.

2. resolved 2024-08-08 18:30 UTC

   We have mitigated this issue, and Airtable's service is now operating normally. We deeply apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-15 23:34 UTC

   We are aware of some users having trouble accessing Airtable and we are investigating the issue.

2. monitoring 2024-07-16 00:08 UTC

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

3. resolved 2024-07-16 00:49 UTC

   We have resolved this incident, and Airtable’s services are functioning normally. We’re sorry for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-05 13:59 UTC

   Airtable’s services are currently unavailable for some customers. Our engineers are actively investigating this downtime incident, and will keep you informed as updates are available. We apologize for the inconvenience this has caused.

2. monitoring 2024-06-05 14:32 UTC

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

3. resolved 2024-06-05 20:14 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-05-27 15:37 UTC

   Our email sending infrastructure is experiencing issues, which is leading to failures on some product surfaces. We are continuing to monitor the situation. We’re sorry for the inconvenience to our customers’ operations.

2. resolved 2024-05-27 18:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-21 16:42 UTC

   We are currently investigating this issue. We apologize for the inconvenience.

2. investigating 2024-03-21 17:27 UTC

   We have implemented mitigations leading to partial recovery and are continuing to work to fully stabilize the system. At this time, Automations are not running. We apologize for the inconvenience.

3. investigating 2024-03-21 18:39 UTC

   We are re-enabling Automations at this time. We have implemented a fix that has caused most bases to recover. Some bases are still unavailable and we are actively working on getting these bases stable as well.

4. monitoring 2024-03-21 19:36 UTC

   A fix has been implemented and we are monitoring the results. Automations are now fully re-enabled. We apologize for the inconvenience this incident has caused.

5. resolved 2024-03-22 00:27 UTC

   We have resolved this incident, and Airtable’s services are functioning normally. We’re sorry for the inconvenience to our customers’ operations.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-07 15:17 UTC

   Some Airtable users are seeing increased error rates. Our engineers are actively investigating this downtime incident, and will keep you informed as updates are available. We apologize for the inconvenience this has caused.

2. resolved 2024-03-07 15:50 UTC

   We have resolved this incident, and Airtable’s services are functioning normally. We’re sorry for the inconvenience to our customers’ operations.

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-03-05 20:55 UTC

   We have received reports that some customers are unable to access Airtable. We believe it may be related to broader connectivity issues with specific ISPs. We will keep you informed as updates are available, and apologize for the inconvenience this has caused.

2. resolved 2024-03-06 01:24 UTC

   The major ISP's incident that was preventing some customers from reaching Airtable has been resolved. Thank you for your patience!

Excerpts are shortened. Read the full incident on Airtable's status page.

Affected: Airtable Service

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-23 19:39 UTC

   Some Airtable users are seeing increased error rates. Our engineers are actively investigating this downtime incident, and will keep you informed as updates are available. We apologize for the inconvenience this has caused.

2. monitoring 2024-02-23 20:00 UTC

   We have implemented a fix to resolve the issues, the service is operating normally. We will continue to monitor the service. We deeply apologize for the disruption and will continue to keep you updated on our progress.

3. resolved 2024-02-24 00:03 UTC

   We have resolved this incident, and Airtable’s services are functioning normally. We’re sorry for the inconvenience to our customers’ operations.

Excerpts are shortened. Read the full incident on Airtable's status page.