52 Airtable incidents · 2024年2月 — official updates, affected components, duration and resolution details.
エアテーブルの拠点がアクセスできない問題を認識しています。 当社のエンジニアは、この問題に対処するために積極的に取り組んでいます.
緩和策を実装し、改善点をいくつか見ていますが、可用性は制限されています。 今後も更新情報を掲載してまいります.
私たちは、修正を実施し、今、実質的な回復を見ています。 今後も更新情報を掲載してまいります.
修正を実装し、結果を監視しています.
エアテーブルのサイトは完全に回復しましたが、私たちは根本的な原因を調べながら、この事件を残し続けています。 今後も更新情報を掲載してまいります.
本件が解決し、本件に不便をおかけしましたので、ご了承願います。 ご不明な点がございましたら、[email protected]までお問い合わせ下さい.
公式のインシデント更新を自動翻訳しています。
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.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
This incident has been resolved, and the Airtable service is again operating normally. We apologize for any disruption this issue caused.
We detected a backend issue that could impact availability of up to 0.45% of bases
We've identified source of problem and are attempting some mitigation actions
Mitigation actions have not yet yielded a recovery. We're engaged with a dependency vendor to perform mitigation actions on their side.
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
We have re-enabled automations as well and everything is functional now
This incident has been resolved.
We are seeing issues with Airtable iOS app, our engineering team is investigating the problem.
We have identified the problem and started the recovery.
This issue has been fully resolved now.
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.
The issue has been identified and a fix is being implemented.
We have prepared a fix and are currently validating it before deploying it to production.
We have validated the fix and are deploying it to production now.
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.
We are currently investigating this issue.
We have identified the issue and are seeing initial signs of recovery. We will continue to post updates here as we have them.
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.
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.
This incident has been resolved.
We are aware of an issue impact the availability of the Airtable service. Our engineers are engaged and we will post status updates here.
The issue has been identified and a fix is being implemented.
We have begun recovery. Our remediation is still in progress. Some Airtable bases are reachable, and the rest will come online soon.
Recovery is continuing. We are on a path to full recovery and are exploring ways to expedite this.
Many Airtable bases are now reachable. Some bases and some Airtable features are still broken. We continue to work towards full recovery.
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.
Our recovery is complete, and Airtable's service is back to normal.
We are currently investigating partial unavailability of Airtable
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.
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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved, with all systems back to operating normally.
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 are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified, and we're working on a fix. We expect a resolution by early next week.
We are rolling out a fix and will update the status page when we've confirmed resolution of the issue.
We have resolved this incident. We’re sorry for the inconvenience.
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.
We are continuing to investigate this issue.
We have identified the issue with our infrastructure provider and are working with the provider to restore full functionality.
The underlying issue has been resolved and we are actively monitoring the service recovery.
Airtable is operational but certain features may experience degraded performance. We are working with our infrastructure provider to address capacity constraints.
Airtable is experiencing a further degradation in performance and increased error rates. We suspect that our infrastructure provider is experiencing a networking issue.
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.
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.
Airtable's systems are back to normal, and this incident is resolved.
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.
A fix has been implemented and we are monitoring the results.
All the impacted customer bases should be back and running again.
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
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
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’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
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
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 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 incident has been resolved.
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
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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 have rolled back the changes and are monitoring. Errors from Script Automation Actions should no longer be happening.
This has now been resolved.
We are aware of an issue which is causing some Airtable bases to be inaccessible. Our engineers are actively engaged and investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. We apologize for the inconvenience.