Skip to main content
Airbyte logo

Is Airbyte Down?

No — Airbyte is up

Reachable from all 8 checked regions

Average response time: 515ms

Last checked · checks run every 6 hours

Official status page: https://status.airbyte.com

Airbyte uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

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

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
197ms
DNS 150ms TCP 1ms TLS 15ms TTFB 186ms
gru
357ms
DNS 152ms TCP 1ms TLS 9ms TTFB 344ms
iad
68ms
DNS 30ms TCP 1ms TLS 9ms TTFB 59ms
jnb
1302ms
DNS 59ms TCP 0ms TLS 359ms TTFB 608ms
lax
157ms
DNS 77ms TCP 1ms TLS 23ms TTFB 123ms
lhr
206ms
DNS 77ms TCP 1ms TLS 39ms TTFB 151ms
nrt
1652ms
DNS 74ms TCP 2ms TLS 141ms TTFB 1383ms
ord
187ms
DNS 44ms TCP 1ms TLS 45ms TTFB 119ms

What Airbyte does

Airbyte is an open-source data integration platform. It runs connectors that pull data out of APIs, databases and files and load it into a warehouse on a schedule, and it is usually the first step of an analytics stack. Teams run either Airbyte Cloud or their own deployment, and downstream transformation and reporting wait on whatever it has loaded.

What an outage looks like

Syncs stop starting on schedule, or start and never finish, so warehouse tables quietly hold yesterday's data with no error anywhere downstream. Dashboards built on those tables keep rendering and simply stop moving. The web application will not load, so failing connections cannot be inspected. New connector configuration and API-triggered syncs fail.

What to do about it

Read status.airbyte.com. It separates Data Sync from WebApp and Airbyte API, and it groups connectors as API Connectors, Database/Warehouse/Lake Connectors and File Connectors, so identify which class your source belongs to before assuming everything is affected. Tell anyone reading the downstream dashboards that the numbers are stale rather than falling, which is the part that misleads people.

Is it down for everyone, or just you?

If this page says Airbyte 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Fivetran
Fivetran
dbt Cloud
dbt Cloud
Snowflake
Snowflake
Databricks
Databricks

Airbyte outage FAQ

My dashboards still load but the numbers stopped moving. Is Airbyte down?
That is the characteristic symptom. When Airbyte fails, new rows stop arriving in the warehouse, so every dashboard built on it keeps rendering the last successful load with no error anywhere. Nothing in the reporting layer is broken, which is why it goes unnoticed. Check the Data Sync component on status.airbyte.com and the connection's last successful sync time.
Only some of my connections are failing. Is that still an Airbyte incident?
It can be. status.airbyte.com reports connectors in three groups, API Connectors, Database/Warehouse/Lake Connectors and File Connectors, so an incident can affect one class of source while the others sync normally. Check which group your failing sources fall into before concluding the problem is specific to your own configuration or credentials.
Does an Airbyte outage affect data already in my warehouse?
No. Airbyte writes into your warehouse, so everything already loaded stays there and remains queryable. The warehouse is a separate service with its own status page. What stops is new data arriving, which makes the effect a growing gap at the recent end of your tables rather than any loss of history you already hold.
Will missed syncs catch up on their own?
Airbyte runs on a schedule and incremental connections resume from where they left off, so a later run generally collects what the missed window would have. Do not assume this for every connector. Check the connection's sync mode and its first successful run after the incident, and compare row counts either side of the gap before trusting it closed.
Is it Airbyte or my source system?
Check the source directly first. A single connector failing while others succeed usually points at that source's own API, credentials or rate limits rather than at Airbyte. status.airbyte.com is the check for the platform itself, and its separate WebApp component tells you whether an unreachable console is a different problem from your syncs still running.

How we measure this

  • We request Airbyte's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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. We only change the 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 Airbyte publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Airbyte goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required