HI Team, We started to see the exchange rate API failing with below error from today; Could you please help me to fix; it was working fine yesterday; And we didn't do any infra changes recently

2026-09-29 04:31:20 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):136 - Docker volume job log path: /tmp/workspace/80261/0/logs.log
2026-09-29 04:31:20 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):141 - Executing worker wrapper. Airbyte version: 0.40.28
2026-09-29 04:31:20 [32mINFO[m i.a.a.c.AirbyteApiClient(retryWithJitter):172 - Attempt 0 to save workflow id for cancellation
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - ----- START CHECK -----
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - Checking if airbyte/source-exchange-rates:1.2.7 exists...
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - airbyte/source-exchange-rates:1.2.7 was found locally.
2026-09-29 04:31:21 [32mINFO[m i.a.w.p.DockerProcessFactory(create):120 - Creating docker container = source-exchange-rates-check-80261-0-lpmmh with resources io.airbyte.config.ResourceRequirements@4047ce63[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=]
2026-09-29 04:31:21 [32mINFO[m i.a.w.p.DockerProcessFactory(create):164 - Preparing command: docker run --rm --init -i -w /data/80261/0 --log-driver none --name source-exchange-rates-check-80261-0-lpmmh --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e AIRBYTE_ROLE= -e WORKER_ENVIRONMENT=DOCKER -e APPLY_FIELD_SELECTION=false -e WORKER_CONNECTOR_IMAGE=airbyte/source-exchange-rates:1.2.7 -e WORKER_JOB_ATTEMPT=0 -e AUTO_DETECT_SCHEMA=false -e AIRBYTE_VERSION=0.40.28 -e WORKER_JOB_ID=80261 airbyte/source-exchange-rates:1.2.7 check --config source_config.json
2026-09-29 04:31:21 [32mINFO[m i.a.w.i.VersionedAirbyteStreamFactory(create):100 - Reading messages from protocol version 0.2.0
2026-09-29 04:32:24 [32mINFO[m i.a.w.i.DefaultAirbyteStreamFactory(internalLog):120 - Ping response code: 504
2026-09-29 04:32:24 [1;31mERROR[m i.a.w.i.DefaultAirbyteStreamFactory(internalLog):116 - Check failed
2026-09-29 04:32:24 [32mINFO[m i.a.w.g.DefaultCheckConnectionWorker(run):110 - Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@5452dc14[status=failed,message=JSONDecodeError('Expecting value: line 1 column 1 (char 0)')]
2026-09-29 04:32:24 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):163 - Stopping cancellation check scheduling...
2026-09-29 04:32:24 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:32:24 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - ----- END CHECK -----
2026-09-29 04:32:24 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:32:25 [32mINFO[m i.a.c.f.EnvVariableFeatureFlags(autoDisablesFailingConnections):27 - Auto Disable Failing Connections: false

Thinking completed The root cause of this failure is indicated by these two lines in your log:

Ping response code: 504
Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@...[status=failed,message=JSONDecodeError('Expecting value: line 1 column 1 (char 0)')]

Why this happens 1. HTTP 504 Gateway Timeout: During the connector's connection check, the request sent to the upstream Exchange Rates API (hosted at APILayer) timed out and returned an HTTP

504

error [Exchange Rates Metadata]. 2. JSONDecodeError: Instead of returning a valid JSON payload, the upstream server or gateway returned an HTML error page or empty response. When the connector attempted to parse this response as JSON, it failed with

JSONDecodeError: Expecting value: line 1 column 1 (char 0)

[Forum Post: Unable to connect; Forum Post: Source Kustomer]. Because you did not make any infrastructure changes and it worked previously, this is typically caused by temporary downtime, severe latency, or rate limiting on the external Exchange Rates API provider's end. Recommended troubleshooting steps 1. Verify Upstream API Status: Test the endpoint directly outside of Airbyte using

curl

or Postman with your API key to see if APILayer / Exchange Rates API is currently responding or timing out:curl -i "https://api.apilayer.com/exchangerates_data/latest?apikey=YOUR_API_KEY" 2. Update the Connector Version: You are running an older version (

airbyte/source-exchange-rates:1.2.7

), whereas newer versions (such as `1.4.64`+) are available [Exchange Rates Metadata]. Newer versions often include better error handling, retries, and backoff logic for HTTP 5xx responses [Github Issue: Pardot 504]. ◦ Go to Settings > Sources in your Airbyte UI and upgrade the

Exchange Rates

connector to the latest available version. 1. Retry Later: If the third-party service is experiencing an outage or degraded performance, syncs and checks will automatically resume working once their gateway recovers. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

(base) -m@MacBook-Air-2 ~ % curl -i "api.apilayer.com/exchangerates_data/latest?apikey=${AIRBYTE_EXCHANGE_K…" HTTP/2 504 date: Tue, 29 Sep 2026 052851 GMT content-type: text/plain; charset=UTF-8 content-length: 16 cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 000001 GMT referrer-policy: same-origin x-frame-options: SAMEORIGIN server: cloudflare cf-ray: a42894c008f23021-MAA alt-svc: h3=":443"; ma=86400 error code: 504 I am getting this from my local curl