Urgent: Why is my Index Exchange Header Bidding setup throwing 'bid timed out' errors constantly?

If only Index Exchange is timing out while other bidders in your Prebid stack are returning bids normally, that usually points to an adapter configuration issue, endpoint connectivity problem, account-side restriction, or traffic filtering issue, rather than a generic Prebid timeout problem.

Most Common Causes of Index Exchange Timeouts

1. Incorrect Site ID / Placement Configuration

One of the most frequent causes is that the siteID configured in Prebid does not match what is provisioned in your Index Exchange account.

Example:

{
    bidder: "ix",
    params: {
        siteId: "123456"
    }
}

Things to verify:

• Correct siteId

• Correct environment (production vs test)

• Ad units approved in Index Exchange

• Domain authorized in your IX account

A valid-looking Site ID can still timeout if IX rejects the request internally.

2. Geographic or Network Blocking

Open DevTools → Network tab.

Look for requests to:

htp://htlb.casalemedia.com

or

https://htlb.casalemedia.com

Questions:

• Are requests being sent?

• Do they receive HTTP 200 responses?

• Are they pending for several seconds?

• Do they fail with 403, 502, 503, or DNS errors?

Many publishers discover:

• Corporate firewalls

• Hosting provider filtering

• CDN rules

• Country-specific routing issues

are preventing successful communication with IX endpoints.

3. Auction Timeout Too Low

Your logs show:

Bid timed out in 1200ms

1200ms is often aggressive.

Many publishers use:

pbjs.setConfig({
    bidderTimeout: 2000
});

or

bidderTimeout: 2500

especially when traffic comes from:

• Asia

• South America

• Mobile networks

However, since you've already increased the timeout and IX still fails consistently, timeout length alone is probably not the root cause.

4. Missing User IDs / Identity Modules

Some SSPs perform poorly when identity signals are absent.

Check whether your stack uses:

• SharedID

• ID5

• PubCommon ID

• LiveRamp

• UID2

Although lack of IDs shouldn't normally cause a timeout, misconfigured identity modules can occasionally create request delays.

5. Prebid Version Compatibility

Verify:

pbjs.version

Older Prebid builds sometimes have bidder-specific bugs.

If you're running a custom build:

• Confirm the Index Exchange adapter is included.

• Confirm the adapter version matches your Prebid version.

A mismatch can produce strange timeout behavior.

6. Consent Management (GDPR/TCF/USP/GPP)

A very common hidden issue.

Check whether your CMP is delaying auctions.

Symptoms:

auction starts
↓
waiting for consent
↓
IX request delayed
↓
timeout

Look for console messages related to:

consentManagement
gdpr
gpp
usp

If consent retrieval is slow, IX may never get enough time to respond.

7. Ad Unit Size Mismatch

Example:

mediaTypes: {
  banner: {
    sizes: [[300,250]]
  }
}

but IX expects:

[[300,250],[336,280]]

or has different mappings configured.

A mismatch can result in no valid bid opportunities and apparent timeout behavior.

8. Index Exchange Account Not Fully Activated

I've seen cases where:

• Site ID exists

• Requests are sent

• No bids ever return

because:

• Domain approval is pending

• Supply path isn't activated

• Seat configuration incomplete

• Traffic quality review still pending

In these cases only Index Exchange fails while every other bidder works.

Contact your IX representative and ask them to verify:

• Site ID status

• Bid request volume

• Bid response volume

• Error logs on their side

Advanced Debugging

Enable Prebid debugging:

pbjs.setConfig({
  debug: true
});

Then inspect:

pbjs.getBidResponses()

and

pbjs.getEvents()

Look specifically for:

eventType === "bidTimeout"

and

eventType === "bidRequested"

This tells you whether:

• IX never received the request

• IX received it but never responded

• IX responded after the timeout

The Most Important Test

Open Chrome DevTools and run:

pbjs.onEvent('bidTimeout', function(data){
    console.log(data);
});

Then inspect the Network tab for IX requests.

You want to determine which of these is happening:

Given your description—every IX bid timing out across multiple ad units while network latency is otherwise healthy—the most likely culprits are:

1. Incorrect or inactive IX Site ID.

2. Domain/account-side provisioning issue in Index Exchange.

3. IX endpoint requests being blocked or failing.

4. Consent/CMP delays preventing the adapter from executing properly.

The next thing I'd check is the actual Network request to htlb.casalemedia.com and its response timing/status, because that usually reveals whether the problem is happening before the request, during transport, or inside Index Exchange's platform.