Airtable SLA
99.9% uptime guarantee (Enterprise, Enterprise Scale, Certain Business plan customers who have agreed to the Master Subscription Agreement plan only)
Official SLA Commitment
Applies to
Enterprise, Enterprise Scale, Certain Business plan customers who have agreed to the Master Subscription Agreement plans only
Scope
Monthly availability of Airtable Services (web app and public API), measured across each calendar month
Measurement
Uptime = total minutes in calendar month minus Downtime. Measured via server monitoring software tracking server-side and client-side success/error rates and overall request volume (including public API requests).
Exclusions
Customer/Permitted User acts or omissions; customer/third-party equipment or integrations; performance slowness (not inaccessibility); internet/telecom failures; force majeure; scheduled maintenance with ≥24h notice; hacking/virus attacks; reasonable emergency maintenance.
Not covered
Free, Team, and self-serve Business plans without MSA. Trial Features and alpha/beta/preview products are explicitly excluded from the SLA per MSA.
Promised vs Measured
SLA Promise
99.9%
≤ 43m downtime/month
Measured (30d)
—
Collecting data…
Verdict
—
24h Uptime
—
7d Uptime
—
30d Uptime
—
Pricing & SLA by Tier
| Plan | SLA Guarantee | Price | Meeting 30d? |
|---|---|---|---|
| Free | No uptime SLA | $0 | — |
| Team | No uptime SLA | $20/user/mo annual ($24 monthly) | — |
| Business | 99.9% (MSA customers only) | $45/user/mo annual ($54 monthly) | |
| Enterprise | 99.9% | Custom (contact sales) | |
| Enterprise Scale | 99.9% | Custom (contact sales) |
Source: airtable.com/pricing
SLA Credit Policy
If monthly uptime falls below 99.9%, eligible Enterprise plan customers may request a Service Credit equal to 10× the fees paid for the downtime portion of the month. Credits apply to future billing only; sole and exclusive remedy for uptime failures.
| Monthly Uptime | Credit |
|---|---|
| < 99.9% monthly uptime | Fees allocated per-minute over the calendar month. Example: 43 min downtime (~99.9% breach) on a $10,000/mo contract ≈ 10 × ($10,000 × 43/43,200) ≈ $995 credit. Report to support@airtable.com within 30 days after month end with account ID and downtime dates/times. |
Must be claimed within 30 days. Applied within 30 days of approval.
Industry SLA Tier Compliance
| Tier | Downtime Budget/Month | 24h | 7d | 30d |
|---|---|---|---|---|
| 99.9%(three nines)Airtable's SLA | 43m 12s | |||
| 99.95% | 21m 36s | |||
| 99.99%(four nines) | 4m 19s | |||
| 99.999%(five nines) | 26s |
Equivalent Downtime
Last 24 hours
—
Last 7 days
—
Last 30 days
—
Incident Summary (90 days)
Total Incidents
0
Active Now
0
Resolved
0
Avg. Resolution
—
Airtable SLA: What You Need to Know
Airtable guarantees 99.9% uptime measured as monthly availability of airtable services (web app and public api), measured across each calendar month. This commitment applies exclusively to Enterprise, Enterprise Scale, Certain Business plan customers who have agreed to the Master Subscription Agreement plan customers — other tiers have no contractual uptime guarantee.
Based on DevHelm's continuous monitoring, Airtable currently shows a 30-day measured uptime of —. Uptime data is still being collected for a complete assessment.
What's Covered (and What Isn't)
Airtable's SLA specifically covers monthly availability of airtable services (web app and public api), measured across each calendar month. It explicitly excludes: Free, Team, and self-serve Business plans without MSA. Trial Features and alpha/beta/preview products are explicitly excluded from the SLA per MSA.. This means outages in excluded components don't count toward SLA credits.
Impact on Your Application
Once sufficient monitoring data is collected, this section will show projected annual downtime. If your application depends on additional services, their independent failure probabilities compound — making dependency monitoring essential for maintaining your own SLA commitments.
Monitoring Methodology
DevHelm tracks Airtable's official status page continuously and aggregates component-level status data into uptime percentages. Data is refreshed every 5 minutes. Uptime is calculated as the percentage of time all components report operational status.
