VIES timeouts

A VIES timeout means no answer arrived before your deadline. The request may still have been processed upstream, which is what makes timeouts trickier than explicit errors.

Good news: no member state is reporting TIMEOUT right now. See the live board →

What it means

A timeout is not something VIES returns. It is the absence of any answer inside the time you were willing to wait, and it happens when a member state's database is slow rather than down, when VIES is queuing behind a backlog, or when the network path is having a bad day.

Timeouts are harder to handle well than explicit errors, for one reason: you do not know whether the request was processed. A lookup is a read, so retrying is perfectly safe — but you cannot infer a single thing about the VAT number from the silence.

Two traps to watch for. First, VIES returns HTTP 200 even for its own error envelopes — {"actionSucceed": false, "errorWrappers":[{"error":"..."}]} — so code that only checks the status code will read a member-state failure as a success and then trip over a missing valid field. Second, default HTTP client timeouts are usually far too generous. A 60-second hang is worse for your users than a fast, honest "unknown".

Which member states return TIMEOUT most

3 occurrences of TIMEOUT observed across all member states in the last 7 days, from our own 5-minute checks. Monitoring began 2026-08-09.

What to do about it

• Set an explicit timeout of about 10 seconds. A healthy VIES lookup normally comes back in well under a second, and a slow member state in a few. Past ten seconds, waiting rarely pays off.
• Always parse the body — never just the status code. Check for actionSucceed === false and read errorWrappers[0].error before you go anywhere near valid.
• Retry idempotently with backoff. Validation is a read, so retrying cannot break anything.
• Fail to "unknown", never to "invalid". Silence is not a negative result.
• Do the work asynchronously wherever you can, so a slow member state never blocks a user-facing request.

Frequently asked questions

Hit a different error?

• MS_UNAVAILABLE — MS_UNAVAILABLE means the national VAT database behind VIES is not answering.
• MS_MAX_CONCURRENT_REQ — MS_MAX_CONCURRENT_REQ means a member state is already handling as many simultaneous VIES lookups as it will take.
• GLOBAL_MAX_CONCURRENT_REQ — GLOBAL_MAX_CONCURRENT_REQ means the VIES front end — not one member state — is handling as many simultaneous requests as it will take.

← Live VIES status for all 28 member states