Skip to content

Outage tracker / Airtable

Is Airtable down?

I'm having a problem

Vendor reports no incidentWhat Airtable reports

Airtable reports no incident on its status page.

As of the last successful poll, 2026-10-19 21:26 UTC.

Airtable's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 6 minutes ago

Airtable is answering our probes, but running at least 4.5x its 7-day median from US-East. The rest of the regions we check answered at their usual speed.

As of Oct 19, 2026, 9:22 PM UTC, RealUptime's checks of Airtable passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 19, 2026, 9:22 PM UTC
US-East1131 msDegraded
US-West556 msChecks passing
Europe968 msChecks passing
Asia-Pacific1641 msChecks passing
US-Central244 msChecks passing
Canada143 msChecks passing
UK419 msChecks passing
Southeast Asia1959 msChecks passing
Australia1438 msChecks passing
South America996 msChecks passing
their status pagetheir claim, not our reading

Airtable reports: All systems operational (“All Systems Operational”)

from Airtable's own status page, checked Oct 19, 2026, 9:19 PM UTC
Airtable's own status page shows no incident, and our checks of Airtable pass right now.

Airtable's own component breakdown, as they publish it

  • Airtable ServiceOperational

These are Airtable's components, named and scored by Airtable. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Airtable's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Airtable response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 287ms2026-09-21 UTC: p95 352ms2026-09-22 UTC: p95 342ms2026-09-23 UTC: p95 433ms2026-09-24 UTC: p95 515ms2026-09-25 UTC: p95 422ms2026-09-26 UTC: p95 455ms2026-09-27 UTC: p95 405ms2026-09-28 UTC: p95 398ms2026-09-29 UTC: p95 376ms2026-09-30 UTC: p95 462ms2026-10-01 UTC: p95 328ms2026-10-02 UTC: p95 338ms2026-10-03 UTC: p95 439ms2026-10-04 UTC: p95 481ms2026-10-05 UTC: p95 321ms2026-10-06 UTC: p95 408ms2026-10-07 UTC: p95 395ms2026-10-08 UTC: p95 588ms2026-10-09 UTC: p95 466ms2026-10-10 UTC: p95 313ms2026-10-11 UTC: p95 509ms2026-10-12 UTC: p95 330ms2026-10-13 UTC: p95 536ms2026-10-14 UTC: p95 294ms2026-10-15 UTC: p95 271ms2026-10-16 UTC: p95 356ms2026-10-17 UTC: p95 435ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
US-West
649msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 539ms2026-09-21 UTC: p95 650ms2026-09-22 UTC: p95 612ms2026-09-23 UTC: p95 531ms2026-09-24 UTC: p95 856ms2026-09-25 UTC: p95 715ms2026-09-26 UTC: p95 775ms2026-09-27 UTC: p95 604ms2026-09-28 UTC: p95 618ms2026-09-29 UTC: p95 649ms2026-09-30 UTC: p95 626ms2026-10-01 UTC: p95 551ms2026-10-02 UTC: p95 550ms2026-10-03 UTC: p95 562ms2026-10-04 UTC: p95 549ms2026-10-05 UTC: p95 571ms2026-10-06 UTC: p95 670ms2026-10-07 UTC: p95 710ms2026-10-08 UTC: p95 682ms2026-10-09 UTC: p95 535ms2026-10-10 UTC: p95 516ms2026-10-11 UTC: p95 605ms2026-10-12 UTC: p95 558ms2026-10-13 UTC: p95 634ms2026-10-14 UTC: p95 559ms2026-10-15 UTC: p95 555ms2026-10-16 UTC: p95 635ms2026-10-17 UTC: p95 554ms2026-10-18 UTC: p95 583ms2026-10-19 UTC: p95 649ms
Sep 20Oct 4Oct 19
Europe
1.1sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 591ms2026-09-21 UTC: p95 605ms2026-09-22 UTC: p95 562ms2026-09-23 UTC: p95 609ms2026-09-24 UTC: p95 662ms2026-09-25 UTC: p95 546ms2026-09-26 UTC: p95 556ms2026-09-27 UTC: p95 689ms2026-09-28 UTC: p95 609ms2026-09-29 UTC: p95 540ms2026-09-30 UTC: p95 587ms2026-10-01 UTC: p95 969ms2026-10-02 UTC: p95 651ms2026-10-03 UTC: p95 682ms2026-10-04 UTC: p95 545ms2026-10-05 UTC: p95 522ms2026-10-06 UTC: p95 615ms2026-10-07 UTC: p95 675ms2026-10-08 UTC: p95 559ms2026-10-09 UTC: p95 609ms2026-10-10 UTC: p95 649ms2026-10-11 UTC: p95 506ms2026-10-12 UTC: p95 612ms2026-10-13 UTC: p95 550ms2026-10-14 UTC: p95 515ms2026-10-15 UTC: p95 637ms2026-10-16 UTC: p95 533ms2026-10-17 UTC: p95 746ms2026-10-18 UTC: p95 824ms2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
Asia-Pacific
1.7sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.7s
Sep 20Oct 4Oct 19
US-Central
428msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 313ms2026-09-21 UTC: p95 445ms2026-09-22 UTC: p95 541ms2026-09-23 UTC: p95 538ms2026-09-24 UTC: p95 511ms2026-09-25 UTC: p95 344ms2026-09-26 UTC: p95 486ms2026-09-27 UTC: p95 600ms2026-09-28 UTC: p95 687ms2026-09-29 UTC: p95 570ms2026-09-30 UTC: p95 578ms2026-10-01 UTC: p95 483ms2026-10-02 UTC: p95 726ms2026-10-03 UTC: p95 661ms2026-10-04 UTC: p95 329ms2026-10-05 UTC: p95 408ms2026-10-06 UTC: p95 351ms2026-10-07 UTC: p95 375ms2026-10-08 UTC: p95 542ms2026-10-09 UTC: p95 620ms2026-10-10 UTC: p95 557ms2026-10-11 UTC: p95 455ms2026-10-12 UTC: p95 497ms2026-10-13 UTC: p95 403ms2026-10-14 UTC: p95 410ms2026-10-15 UTC: p95 472ms2026-10-16 UTC: p95 349ms2026-10-17 UTC: p95 393ms2026-10-18 UTC: p95 358ms2026-10-19 UTC: p95 428ms
Sep 20Oct 4Oct 19
Canada
232msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 408ms2026-09-21 UTC: p95 415ms2026-09-22 UTC: p95 482ms2026-09-23 UTC: p95 431ms2026-09-24 UTC: p95 533ms2026-09-25 UTC: p95 611ms2026-09-26 UTC: p95 562ms2026-09-27 UTC: p95 338ms2026-09-28 UTC: p95 616ms2026-09-29 UTC: p95 595ms2026-09-30 UTC: p95 657ms2026-10-01 UTC: p95 705ms2026-10-02 UTC: p95 670ms2026-10-03 UTC: p95 611ms2026-10-04 UTC: p95 573ms2026-10-05 UTC: p95 453ms2026-10-06 UTC: p95 474ms2026-10-07 UTC: p95 395ms2026-10-08 UTC: p95 620ms2026-10-09 UTC: p95 352ms2026-10-10 UTC: p95 405ms2026-10-11 UTC: p95 489ms2026-10-12 UTC: p95 335ms2026-10-13 UTC: p95 474ms2026-10-14 UTC: p95 321ms2026-10-15 UTC: p95 442ms2026-10-16 UTC: p95 513ms2026-10-17 UTC: p95 379ms2026-10-18 UTC: p95 210ms2026-10-19 UTC: p95 232ms
Sep 20Oct 4Oct 19
UK
666msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 619ms2026-09-21 UTC: p95 642ms2026-09-22 UTC: p95 716ms2026-09-23 UTC: p95 928ms2026-09-24 UTC: p95 694ms2026-09-25 UTC: p95 836ms2026-09-26 UTC: p95 882ms2026-09-27 UTC: p95 683ms2026-09-28 UTC: p95 766ms2026-09-29 UTC: p95 627ms2026-09-30 UTC: p95 731ms2026-10-01 UTC: p95 596ms2026-10-02 UTC: p95 762ms2026-10-03 UTC: p95 679ms2026-10-04 UTC: p95 800ms2026-10-05 UTC: p95 695ms2026-10-06 UTC: p95 651ms2026-10-07 UTC: p95 589ms2026-10-08 UTC: p95 642ms2026-10-09 UTC: p95 652ms2026-10-10 UTC: p95 722ms2026-10-11 UTC: p95 726ms2026-10-12 UTC: p95 830ms2026-10-13 UTC: p95 663ms2026-10-14 UTC: p95 511ms2026-10-15 UTC: p95 578ms2026-10-16 UTC: p95 662ms2026-10-17 UTC: p95 633ms2026-10-18 UTC: p95 607ms2026-10-19 UTC: p95 666ms
Sep 20Oct 4Oct 19
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.1s2026-09-23 UTC: p95 2.7s2026-09-24 UTC: p95 2.2s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 2.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.5s
Sep 20Oct 4Oct 19
Australia
3.4sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 2.0s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 2.0s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.9s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 3.4s
Sep 20Oct 4Oct 19
South America
902msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 856ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 759ms2026-10-07 UTC: p95 878ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 910ms2026-10-18 UTC: p95 952ms2026-10-19 UTC: p95 902ms
Sep 20Oct 4Oct 19

Check your own site while you wait on Airtable

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Airtable. It cannot diagnose Airtable's own systems.

Email me when Airtable reports an incident on its status page, and again when it reports it resolved.

Get an email when Airtable reports an incident

Email me when Airtable reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Airtable's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    DegradedUS-East, US-West, US-Central, Canada
    • US-East
      Degradedlatency: 1131msstatus code: 401checked: Oct 19, 2026, 9:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Airtable normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 556msstatus code: 401checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Airtable normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 244msstatus code: 401checked: Oct 19, 2026, 8:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Airtable normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 143msstatus code: 401checked: Oct 19, 2026, 8:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Airtable normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 996msstatus code: 401checked: Oct 19, 2026, 8:41 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Airtable normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 968msstatus code: 401checked: Oct 19, 2026, 9:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Airtable normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 419msstatus code: 401checked: Oct 19, 2026, 8:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Airtable normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1641msstatus code: 401checked: Oct 19, 2026, 9:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Airtable normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1959msstatus code: 401checked: Oct 19, 2026, 8:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Airtable normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1438msstatus code: 401checked: Oct 19, 2026, 8:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Airtable normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Airtable, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Airtable yet, which is not evidence that nothing is wrong.

Recent probe events

Airtable service unavailability, 1h 42mdeclared on their status page2026-07-08
Increased latency for requests to Airtable, 39mdeclared on their status page2026-06-29
Increased latency for requests to Airtable, 16mdeclared on their status page2026-06-08
Partial unavailability for 0.45% bases, 2h 18mdeclared on their status page2026-04-30
Service interruption on Airtable iOS app, 45mdeclared on their status page2026-04-16
MCP Server Unavailable, 2h 33mdeclared on their status page2026-03-13
Some users unable to access Airtable, 6h 18mdeclared on their status page2026-03-11
Airtable service interruption, 6h 43mdeclared on their status page2026-02-20

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Airtable since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Airtable covering any window you pick, with our check readings and Airtable's own claim at the time, side by side.

Full check history for Airtable: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Airtable uptime by RealUptime's checksLive, from this page's own readings.
[![Airtable uptime by RealUptime's checks](https://realuptime.io/outages/airtable/badge.svg?days=30)](https://realuptime.io/outages/airtable)
<a href="https://realuptime.io/outages/airtable"><img src="https://realuptime.io/outages/airtable/badge.svg?days=30" alt="Airtable uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Airtable down?", https://realuptime.io/outages/airtable. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://api.airtable.com/v0/meta/whoami
secondary
https://status.airtable.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.airtable.com

RealUptime is not affiliated with Airtable; the name identifies what we checked, and nothing here speaks for Airtable's own team. We send a single web request to Airtable from 10 regions on our own schedule and time the response. We do not see inside Airtable's systems, do not use an account or real transaction, and are not the same signal Airtable's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Airtable is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.