Skip to content

Outage tracker / Airtable

Is Airtable down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Airtable from all 10 regions we check.

As of Oct 5, 2026, 8:14 PM UTC, Airtable answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Airtable (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 8:14 PM UTC
US-East235 msOperational
US-West352 msOperational
Europe438 msOperational
Asia-Pacific787 msOperational
US-Central602 msOperational
Canada305 msOperational
UK631 msOperational
Southeast Asia1230 msOperational
Australia1713 msOperational
South America865 msOperational
their status pagetheir claim, not our reading

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

from Airtable's own status page, checked Oct 5, 2026, 7:58 PM UTC
Our probes and Airtable's own status page agree: both show Airtable as reachable 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
331msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 400ms2026-09-07 UTC: p95 370ms2026-09-08 UTC: p95 345ms2026-09-09 UTC: p95 377ms2026-09-10 UTC: p95 315ms2026-09-11 UTC: p95 302ms2026-09-12 UTC: p95 318ms2026-09-13 UTC: p95 308ms2026-09-14 UTC: p95 378ms2026-09-15 UTC: p95 341ms2026-09-16 UTC: p95 315ms2026-09-17 UTC: p95 370ms2026-09-18 UTC: p95 308ms2026-09-19 UTC: p95 378ms2026-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 331ms
Sep 6Sep 20Oct 5
US-West
551msp95 · 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-06 UTC: p95 564ms2026-09-07 UTC: p95 659ms2026-09-08 UTC: p95 537ms2026-09-09 UTC: p95 339ms2026-09-10 UTC: p95 384ms2026-09-11 UTC: p95 524ms2026-09-12 UTC: p95 448ms2026-09-13 UTC: p95 378ms2026-09-14 UTC: p95 394ms2026-09-15 UTC: p95 457ms2026-09-16 UTC: p95 495ms2026-09-17 UTC: p95 560ms2026-09-18 UTC: p95 489ms2026-09-19 UTC: p95 575ms2026-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 551ms
Sep 6Sep 20Oct 5
Europe
530msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 695ms2026-09-07 UTC: p95 535ms2026-09-08 UTC: p95 694ms2026-09-09 UTC: p95 599ms2026-09-10 UTC: p95 673ms2026-09-11 UTC: p95 578ms2026-09-12 UTC: p95 674ms2026-09-13 UTC: p95 548ms2026-09-14 UTC: p95 541ms2026-09-15 UTC: p95 538ms2026-09-16 UTC: p95 629ms2026-09-17 UTC: p95 672ms2026-09-18 UTC: p95 548ms2026-09-19 UTC: p95 618ms2026-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 530ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.3sp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-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.3s
Sep 6Sep 20Oct 5
US-Central
422msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 657ms2026-09-08 UTC: p95 483ms2026-09-09 UTC: p95 337ms2026-09-10 UTC: p95 326ms2026-09-11 UTC: p95 338ms2026-09-12 UTC: p95 373ms2026-09-13 UTC: p95 377ms2026-09-14 UTC: p95 376ms2026-09-15 UTC: p95 521ms2026-09-16 UTC: p95 362ms2026-09-17 UTC: p95 313ms2026-09-18 UTC: p95 315ms2026-09-19 UTC: p95 331ms2026-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 422ms
Sep 6Sep 20Oct 5
Canada
455msp95 · 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-06 UTC: p95 467ms2026-09-07 UTC: p95 386ms2026-09-08 UTC: p95 408ms2026-09-09 UTC: p95 356ms2026-09-10 UTC: p95 410ms2026-09-11 UTC: p95 411ms2026-09-12 UTC: p95 442ms2026-09-13 UTC: p95 512ms2026-09-14 UTC: p95 491ms2026-09-15 UTC: p95 593ms2026-09-16 UTC: p95 531ms2026-09-17 UTC: p95 339ms2026-09-18 UTC: p95 484ms2026-09-19 UTC: p95 450ms2026-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 455ms
Sep 6Sep 20Oct 5
UK
679msp95 · 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-06 UTC: p95 672ms2026-09-07 UTC: p95 682ms2026-09-08 UTC: p95 590ms2026-09-09 UTC: p95 567ms2026-09-10 UTC: p95 691ms2026-09-11 UTC: p95 560ms2026-09-12 UTC: p95 764ms2026-09-13 UTC: p95 744ms2026-09-14 UTC: p95 680ms2026-09-15 UTC: p95 830ms2026-09-16 UTC: p95 843ms2026-09-17 UTC: p95 910ms2026-09-18 UTC: p95 830ms2026-09-19 UTC: p95 819ms2026-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 679ms
Sep 6Sep 20Oct 5
Southeast Asia
1.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-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.5s2026-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.5s
Sep 6Sep 20Oct 5
Australia
1.7sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 2.2s2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 2.1s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.6s2026-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.7s
Sep 6Sep 20Oct 5
South America
1.1sp95 · 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-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.8s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-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.1s
Sep 6Sep 20Oct 5

Is it Airtable, or is it you?

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.

Get an email when we see Airtable go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Airtable, and again when they can reach it again. That is our own measurement from ten regions, not Airtable's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 235msstatus code: 401checked: Oct 5, 2026, 7:57 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
      Operationallatency: 352msstatus code: 401checked: Oct 5, 2026, 8:10 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
      Operationallatency: 602msstatus code: 401checked: Oct 5, 2026, 7:21 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
      Operationallatency: 305msstatus code: 401checked: Oct 5, 2026, 7:29 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
    Operationallatency: 865msstatus code: 401checked: Oct 5, 2026, 8:14 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 438msstatus code: 401checked: Oct 5, 2026, 7:53 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
      Operationallatency: 631msstatus code: 401checked: Oct 5, 2026, 7:24 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 787msstatus code: 401checked: Oct 5, 2026, 7:50 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
      Operationallatency: 1230msstatus code: 401checked: Oct 5, 2026, 7:24 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
      Operationallatency: 1713msstatus code: 401checked: Oct 5, 2026, 7:30 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 outages

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

measured 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 measurements and Airtable's own claim at the time, side by side.

Full availability history for Airtable: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Airtable uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Airtable's SLA implies, from our measurement

At or above your target

We measured none of downtime for Airtable over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Airtable's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.airtable.com/v0/meta/whoami
secondary
https://status.airtable.com/
RealUptime is not affiliated with Airtable; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.