- Service Status
- /
- Airtable

Is Airtable Down?
- 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
| Component | Status |
|---|---|
| Airtable Service | Operational |
FlareWarden checks
airtable.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- 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
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 144 ms | 2 ms | 3 ms | 256 ms |
| Dallas | 67 ms | 1 ms | 4 ms | 255 ms |
| Frankfurt | 16 ms | 3 ms | 4 ms | 250 ms |
| Johannesburg | 314 ms | 1 ms | 4 ms | 703 ms |
| London | 63 ms | 2 ms | 5 ms | 242 ms |
| Los Angeles | 36 ms | 3 ms | 6 ms | 236 ms |
| Newark | 114 ms | 3 ms | 5 ms | 275 ms |
| São Paulo | 149 ms | 1 ms | 4 ms | 364 ms |
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 streakMeasured 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.
Related services
Airtable outage FAQ
Is Airtable down or is my base just slow?
Will edits made during an Airtable outage be saved?
Do Airtable forms keep collecting responses during an outage?
Does an Airtable outage break my automations and integrations?
Can I export my data while Airtable is down?
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
403or429means 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


