Airtable service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for airtable.com. Compare the regional responses with the problem you see in Airtable.
Find Airtable help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Airtable's marketing site, a particular base and an automation run are different targets. Access permissions can affect one base without a platform outage.
The checker above requests airtable.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Airtable action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse work app checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
A base owner or organisation administrator may need to provide access-related context.
Open the website in your browser and compare it with the result above.
Open Airtable help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Base or interface identifier, automation run time, failed action, role and exact error; omit private row contents.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Airtable.
These are troubleshooting comparisons, not claims that Airtable is currently experiencing a particular incident.
Compare another base you own and ask an authorised collaborator whether the same view fails.
For an automation issue, inspect the failed run and the trigger/action that stopped before rerunning the workflow.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Airtable seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open airtable.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Airtable issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Airtable support.
Run the airtable.com check and compare its original timestamps and responses with your actual error. Airtable's marketing site, a particular base and an automation run are different targets. Access permissions can affect one base without a platform outage.
Use the community buttons on this page to share whether the service works for you. For help from Airtable, use the official help/reporting resource linked above. A base owner or organisation administrator may need to provide access-related context.
Compare another base you own and ask an authorised collaborator whether the same view fails. For an automation issue, inspect the failed run and the trigger/action that stopped before rerunning the workflow.
Base or interface identifier, automation run time, failed action, role and exact error; omit private row contents.