outages.live
Live

Airbyte

Airbyte is operational

Checked 1 min ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

85
Data Sync Operational
90 days agoNo incidentsToday
WebApp Operational
90 days agoNo incidentsToday
Notifications Operational
90 days agoNo incidentsToday
Normalization Operational
90 days agoNo incidentsToday
Airbyte Homepage (Airbyte.com) Operational
90 days agoNo incidentsToday
Third Party Component Operational
90 days agoNo incidentsToday
Airbyte API Operational
90 days agoNo incidentsToday
Connector Builder Operational
90 days agoNo incidentsToday
Airbyte Agents Operational
90 days agoNo incidentsToday

Sources

All Other Connectors Operational
90 days agoNo incidentsToday
Airtable Source Operational
90 days agoNo incidentsToday
All Other Database Sources Operational
90 days agoNo incidentsToday
Db2 (Enterprise) Source Operational
90 days agoNo incidentsToday
Amazon Ads Source Operational
90 days agoNo incidentsToday
Azure Blob Storage Source Operational
90 days agoNo incidentsToday
Amazon Seller Partner Source Operational
90 days agoNo incidentsToday
File Source Operational
90 days agoNo incidentsToday
MSSQL Source Operational
90 days agoNo incidentsToday
MongoDB Source Operational
90 days agoNo incidentsToday
Google Cloud Storage (GCS) Source Operational
90 days agoNo incidentsToday
Amplitude Source Operational
90 days agoNo incidentsToday
Google Drive Source Operational
90 days agoNo incidentsToday
MySQL Source Operational
90 days agoNo incidentsToday
Bing Ads Source Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow Airbyte

Your coding agent knows when Airbyte is down, and tells you when a failure is theirs, not yours. You can also get Airbyte incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "airbyte" and tell me if Airbyte has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=airbyte
Slack
/feed subscribe https://outages.cc/feed.xml?providers=airbyte

Go from tracking outages to fixing production issues with Polylane.

Try Polylane