Skip to main content
Airtable logo

Is Airtable Down?

No — Airtable is up

Reachable from all 6 checked regions

Average response time: 384ms

Last checked · checks run every 6 hours

Official status page: https://status.airtable.com

Airtable uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
374ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 22 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
292ms
DNS 0ms TCP 6ms TLS 11ms TTFB 225ms
ewr
122ms
DNS 0ms TCP 1ms TLS 3ms TTFB 108ms
fra
303ms
DNS 0ms TCP 1ms TLS 3ms TTFB 168ms
gru
400ms
DNS 0ms TCP 11ms TLS 15ms TTFB 261ms
iad
129ms
DNS 0ms TCP 1ms TLS 5ms TTFB 109ms
jnb
411ms
DNS 0ms TCP 0ms TLS 3ms TTFB 362ms
lax
369ms
DNS 0ms TCP 2ms TLS 5ms TTFB 183ms
lhr
823ms
DNS 0ms TCP 7ms TLS 11ms TTFB 669ms

What Airtable does

Airtable is a spreadsheet and database hybrid that teams use to run content calendars, inventories, applicant pipelines and internal tools. Many organisations wire it into automations and customer-facing forms through its API, so an Airtable outage often stops workflows in other products rather than only blocking people from a table.

What an outage looks like

Bases fail to load, or load with rows missing and cells stuck showing placeholder values. Edits appear locally and then revert once the client reconnects. Forms served to customers stop accepting submissions. Automations and API integrations return errors or time out, so downstream tools relying on Airtable as their datastore fail alongside it.

What to do about it

Check status.airtable.com, which reports the service as a single component rather than splitting it by feature, so it tells you whether Airtable is affected but not which part. Avoid re-entering rows that appeared to fail, since edits queued in the browser often sync on reconnect and produce duplicates. Anything driven by an Airtable automation is worth checking afterwards.

Is it down for everyone, or just you?

If this page says Airtable is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Notion
Notion
Monday.com
Monday.com
Jira
Jira
Figma
Figma

Airtable outage FAQ

Is Airtable down or is my base just slow?
Very large bases load slowly under normal conditions, which is easy to mistake for an incident. Check status.airtable.com first, then try a small base in the same workspace. If the small base opens quickly, the problem is base size or view complexity rather than the service. Airtable reports a single overall component, so it will not narrow it further.
Will edits made during an Airtable outage be saved?
Edits the browser accepted but could not send are held client-side and often sync when the connection returns, which is why rows sometimes reappear after an incident. Edits made in a tab you then closed are usually lost. Keep the tab open until the status page clears rather than refreshing, since refreshing discards anything not yet delivered.
Do Airtable forms keep collecting responses during an outage?
No. Forms are served by Airtable, so if the service is unreachable the form does not render and the person filling it in sees a failure rather than a queue. Nothing is stored to be recovered later. If the form matters commercially, publishing an alternative during a long incident is more useful than waiting.
Does an Airtable outage break my automations and integrations?
Yes, and often more visibly than the tables themselves. Automations that read or write Airtable fail, and any external tool using the API errors out. Some integrations retry on their own; others record a failure and move on. Check downstream systems once Airtable recovers rather than assuming the backlog processed itself.
Can I export my data while Airtable is down?
Not reliably, since export runs through the same service. This is the argument for scheduled exports rather than on-demand ones: a backup taken weekly is available during an incident, while one you try to take mid-outage is not. If you need the data urgently, a recent local CSV or a synced copy in another tool is the practical route.

How we measure this

  • We request Airtable's public endpoint every 6 hours from Fly.io regions across six continents — 6 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Airtable publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Airtable goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required