Skip to main content
Airtable logo

Is Airtable Down?

No — Airtable is up
Airtable's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 491 ms

Right now

The verdict is the worse of these two. How we decide

Airtable's status page

status.airtable.com · read · checked every 3 minutes

Operational
Airtable's components, as its status page reports them
ComponentStatus
Airtable ServiceOperational

FlareWarden checks

airtable.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
491 ms
Checked

By region

  • Ashburn reachable, 263 ms
  • Dallas reachable, 304 ms
  • Frankfurt reachable, 344 ms
  • Johannesburg reachable, 1381 ms
  • London reachable, 395 ms
  • Los Angeles reachable, 361 ms
  • Newark reachable, 287 ms
  • São Paulo reachable, 593 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn144 ms2 ms3 ms256 ms
Dallas67 ms1 ms4 ms255 ms
Frankfurt16 ms3 ms4 ms250 ms
Johannesburg314 ms1 ms4 ms703 ms
London63 ms2 ms5 ms242 ms
Los Angeles36 ms3 ms6 ms236 ms
Newark114 ms3 ms5 ms275 ms
São Paulo149 ms1 ms4 ms364 ms
We check that airtable.com loads, not every feature behind it. Test it yourself

History

Incidents Airtable reported

Since Oct 22, 15 days · from status.airtable.com

Incidents
0
Major or critical
0
Median to resolve
—

No incidents reported in this window.

Airtable website availability

Measured by FlareWarden · airtable.com

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

Last 30 days

91-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 31 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 31 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of airtable.com from multiple regions every 6 hours. Airtable's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Airtable itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Airtable goes down

We check Airtable every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required