Skip to main content
Airbyte

Investigating Increased Latency on Workload APIs

Degraded Lasted 0m · started · Airbyte's page

Level
confirmed
Worst impact
Degraded
Components
Airbyte API
Down Index
17of 100

What to do

  • Check whether you use Airbyte Airbyte API. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-07-06 17:30 UTC and 2026-07-06 17:30 UTC may need a replay.
  • Subscribe to Airbyte's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=airbyte works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Airbyte 1

  1. resolved

    Type: Incident Duration: 5 hours and 58 minutes Affected Components: Airbyte API Jul 6, 23:28:21 GMT+0 - Resolved - This incident has been resolved. Jul 6, 20:52:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 6, 17:30:00 GMT+0 - Monitoring - We implemented a fix for an issue that caused increased latency affecting the Workload APIs. We will provide updates as more information becomes available.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-3665187b32

Is Airbyte still down?

No, this incident was resolved 2026-07-06 17:30 UTC. For Airbyte's live state, see https://down.guide/airbyte.

How long did it last?

0m, from 2026-07-06 17:30 UTC to 2026-07-06 17:30 UTC, by the times Airbyte posted.

What was affected?

Airbyte named Airbyte API.

What caused it?

Airbyte hasn't published a root cause. If it does, it shows here.

Where does this come from?

Airbyte's official status page, https://status.airbyte.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.