Istoricul incidentelor Airtable

1. 8 iulie 2026 la 19:17 UTCinvestigating

   Suntem conştienţi de o problemă care cauzează inaccesibilitatea unor baze de bord. Inginerii noştri sunt angajaţi şi lucrează activ pentru a aborda această problemă.

2. 8 iulie 2026 la 19:47 UTCinvestigating

   Am pus în aplicare unele măsuri de atenuare și vedem unele îmbunătățiri, dar disponibilitatea continuă să fie limitată. Vom continua să postăm actualizări aici aşa cum le avem.

3. 8 iulie 2026 la 19:55 UTCidentified

   Am implementat o soluţie şi acum vedem o recuperare substanţială. Vom continua să postăm actualizări aici aşa cum le avem.

4. 8 iulie 2026 la 20:05 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

5. 8 iulie 2026 la 20:29 UTCmonitoring

   Site-ul Airtable şi-a revenit complet, însă continuăm să părăsim acest incident în timp ce investigăm cauza principală. Vom continua să postăm actualizări aici aşa cum le avem.

6. 8 iulie 2026 la 20:59 UTCresolved

   Acest incident a fost rezolvat şi ne cerem scuze pentru neplăcerile cauzate de această problemă. Vă rugăm să ajungeţi la [email protected] dacă aveţi orice întrebări suplimentare.

Traducere automată din actualizarea oficială a incidentului.

1. 29 iunie 2026 la 18:33 UTCinvestigating

   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. 29 iunie 2026 la 18:43 UTCmonitoring

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

3. 29 iunie 2026 la 19:13 UTCresolved

   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.

1. 8 iunie 2026 la 19:44 UTCinvestigating

   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. 8 iunie 2026 la 19:52 UTCmonitoring

   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. 8 iunie 2026 la 20:00 UTCresolved

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

1. 30 aprilie 2026 la 09:01 UTCinvestigating

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

2. 30 aprilie 2026 la 09:35 UTCidentified

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

3. 30 aprilie 2026 la 10:35 UTCidentified

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

4. 30 aprilie 2026 la 10:50 UTCmonitoring

   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. 30 aprilie 2026 la 11:19 UTCmonitoring

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

6. 30 aprilie 2026 la 11:19 UTCresolved

   This incident has been resolved.

1. 16 aprilie 2026 la 18:54 UTCinvestigating

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

2. 16 aprilie 2026 la 19:28 UTCmonitoring

   We have identified the problem and started the recovery.

3. 16 aprilie 2026 la 19:38 UTCresolved

   This issue has been fully resolved now.

1. 13 martie 2026 la 21:11 UTCinvestigating

   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. 13 martie 2026 la 21:24 UTCidentified

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

3. 13 martie 2026 la 22:24 UTCidentified

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

4. 13 martie 2026 la 23:00 UTCidentified

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

5. 13 martie 2026 la 23:44 UTCresolved

   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.

1. 11 martie 2026 la 19:01 UTCinvestigating

   We are currently investigating this issue.

2. 11 martie 2026 la 19:07 UTCidentified

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

3. 11 martie 2026 la 19:31 UTCidentified

   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. 11 martie 2026 la 22:03 UTCmonitoring

   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. 12 martie 2026 la 01:19 UTCresolved

   This incident has been resolved.

1. 20 februarie 2026 la 18:44 UTCinvestigating

   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. 20 februarie 2026 la 19:12 UTCidentified

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

3. 20 februarie 2026 la 20:56 UTCidentified

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

4. 20 februarie 2026 la 21:59 UTCidentified

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

5. 20 februarie 2026 la 23:16 UTCidentified

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

6. 21 februarie 2026 la 01:20 UTCmonitoring

   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. 21 februarie 2026 la 01:27 UTCresolved

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

1. 13 februarie 2026 la 05:40 UTCinvestigating

   We are currently investigating partial unavailability of Airtable

2. 13 februarie 2026 la 06:33 UTCinvestigating

   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. 13 februarie 2026 la 07:49 UTCresolved

   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.

1. 12 februarie 2026 la 17:29 UTCidentified

   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. 12 februarie 2026 la 21:28 UTCmonitoring

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

3. 13 februarie 2026 la 05:06 UTCresolved

   This incident has been resolved.

1. 21 ianuarie 2026 la 22:36 UTCinvestigating

   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. 21 ianuarie 2026 la 23:01 UTCidentified

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

3. 21 ianuarie 2026 la 23:49 UTCresolved

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

1. 20 noiembrie 2025 la 18:26 UTCidentified

   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. 20 noiembrie 2025 la 18:27 UTCidentified

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

3. 20 noiembrie 2025 la 18:49 UTCmonitoring

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

4. 20 noiembrie 2025 la 19:34 UTCresolved

   This incident has been resolved.

1. 30 octombrie 2025 la 20:48 UTCinvestigating

   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. 30 octombrie 2025 la 23:53 UTCidentified

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

3. 31 octombrie 2025 la 01:43 UTCidentified

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

4. 31 octombrie 2025 la 04:43 UTCresolved

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

1. 20 octombrie 2025 la 07:25 UTCinvestigating

   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. 20 octombrie 2025 la 08:59 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 octombrie 2025 la 09:01 UTCidentified

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

4. 20 octombrie 2025 la 11:34 UTCmonitoring

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

5. 20 octombrie 2025 la 14:35 UTCmonitoring

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

6. 20 octombrie 2025 la 19:02 UTCinvestigating

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

7. 20 octombrie 2025 la 20:06 UTCmonitoring

   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. 21 octombrie 2025 la 00:03 UTCmonitoring

   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. 21 octombrie 2025 la 16:51 UTCresolved

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

1. 25 septembrie 2025 la 19:09 UTCinvestigating

   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. 25 septembrie 2025 la 21:34 UTCmonitoring

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

3. 25 septembrie 2025 la 21:37 UTCresolved

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

1. 31 iulie 2025 la 17:01 UTCidentified

   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. 31 iulie 2025 la 23:26 UTCidentified

   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. 1 august 2025 la 19:50 UTCidentified

   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. 5 august 2025 la 15:35 UTCidentified

   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. 6 august 2025 la 19:29 UTCmonitoring

   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. 8 august 2025 la 20:05 UTCresolved

   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

1. 30 iulie 2025 la 01:26 UTCidentified

   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. 30 iulie 2025 la 02:43 UTCresolved

   This incident has been resolved.

1. 28 iulie 2025 la 22:54 UTCinvestigating

   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. 28 iulie 2025 la 23:04 UTCidentified

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

3. 29 iulie 2025 la 02:13 UTCresolved

   This incident has been resolved.

1. 23 iulie 2025 la 01:05 UTCidentified

   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. 23 iulie 2025 la 01:12 UTCmonitoring

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

3. 23 iulie 2025 la 01:39 UTCresolved

   This has now been resolved.

1. 26 iunie 2025 la 22:25 UTCinvestigating

   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. 26 iunie 2025 la 22:37 UTCmonitoring

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

3. 26 iunie 2025 la 22:47 UTCresolved

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