VIES Down or Not Working? What to Do Right Now
When VIES is down, the VAT number was not checked: store it as unchecked, retry with backoff, and validate it again later. Avatcado retries VIES on every plan. On Pro and Business it also asks the national tax register in the 10 EU countries it covers.
VIES failures in the last 90 days, from Avatcado production traffic
Figures as of November 18, 2026, refreshed every hour.
Least reliable member states
The failure rate is the share of VIES lookups for a member state that ended without a usable VIES answer, after Avatcado's retries. Member states with fewer than 50 lookups in the window are left out, and so are test keys. These rates include checks made through the demo checker on this site.
| Member state | Failure rate |
|---|---|
FRFrance | 8.2% |
DKDenmark | 5.4% |
DEGermany | 4% |
PLPoland | 2.6% |
FIFinland | 2.2% |
Which VIES errors the failures carried
Each code's share of requests that met a VIES availability error, including requests a retry later answered, for customer API keys, with test keys and the demo checker left out. Codes met by fewer than 30 requests are not shown. Each code links to what it means and how to handle it.
An error such as MS_UNAVAILABLE means VIES could not complete the check. Let the order or signup go through with the number stored as unchecked, and check it again once the member state is back.
For current figures, the VIES uptime page shows the failure rate of each member state on Avatcado's production traffic, and each VIES error page shows how often its code occurs.
How to tell a VIES outage from an invalid VAT number
VIES has no central database. It forwards each check to the VAT database of the member state that issued the number. Normally, a result of invalid means that database was asked and does not record the number. When the member state's system or VIES itself cannot answer, VIES returns an error code instead, and the number has not been checked. During a partial outage, some member states answer invalid for valid numbers instead of returning an error; the degraded status described below is how Avatcado handles that.
Avatcado treats 6 VIES errors as availability errors, meaning VIES could not complete the check. Each one links to its cause and how to handle it:
MS_UNAVAILABLE: The member state's own system is not replying or not available.MS_MAX_CONCURRENT_REQ: Too many requests are open towards one member state at the same time.TIMEOUT: VIES did not receive a reply within its allocated time.SERVICE_UNAVAILABLE: VIES hit an error at the network or web application level.GLOBAL_MAX_CONCURRENT_REQ: VIES as a whole reached its maximum number of concurrent requests.VOW-ERR-11: A REST API error reading "A mandatory field is missing". On 2026-09-04 Avatcado got it on complete requests while VIES listed one of the member states as unavailable.
None of them says anything about the VAT number. Store the outcome as unchecked, apart from invalid, and never show the customer an "invalid VAT number" message for one of them. In a VIES response, check the error fields before you read valid: the VIES REST and SOAP API guide shows where they sit, including errors carried inside HTTP 200 responses.
To see whether a member state is down right now, open the VIES technical information page, which shows the status of each member state, or call GET /check-status on the VIES REST API, which lists every country as Available, Unavailable or Monitoring Disabled. Some downtime is planned: the VIES FAQ lists regular unavailability windows for some member states.
What to do while VIES is down
- Retry with exponential backoff and a cap on the number of attempts. Do not retry
GLOBAL_MAX_CONCURRENT_REQstraight away: it means VIES as a whole has reached its maximum number of concurrent requests, and an immediate retry adds one more. - Let the customer continue. Accept the order or signup with the VAT number stored as unchecked. How you tax an unchecked number is a rule for your own business, so decide it before the next outage.
- Check the number again later. Put it in a queue and retry once the member state is back;
GET /check-statusshows whether it is. - Tell the customer that the VAT number check for their country is temporarily unavailable, and that the number they entered has not been rejected.
How to design for VIES outages
Validate in the background
A check inside the checkout request keeps the customer waiting while VIES retries or times out. Run it from a queue or a background job, record the outcome, and act on it when it arrives. Avatcado's async endpoint, on Pro and Business, returns 202 at once and delivers the result to your webhook. The async validation guide shows the flow.
Keep the last known answer, and know its limits
Store every completed check: the number, the result, the date, and the consultation number when you have one. During an outage, a stored valid result for a returning customer lets the order go through. A stored result shows what the member state recorded on the day of the check, and a registration can end after that day. It cannot help with a number you have never checked. Record the age of an answer when you use it, and check stored numbers again on a schedule.
Use a national register as a second source
Some member states publish their own VAT register outside VIES. Avatcado uses 10 of them as a second source. The coverage page lists which ones, and how the national registry fallback works explains the order of the steps. A register answer never carries a VIES consultation number. A register can also leave out entity types that VIES covers, so Avatcado serves a register answer only when it confirms the number, and never uses one to reject a number.
Decide what proof you keep
VIES returns a consultation number when you send your own VAT number as the requester and the check completes. A fault response carries none. If you keep consultation numbers as evidence, store the error code and the time of a failed check, and run the check again once the member state answers. With Avatcado, a request that carries requester_vat_number is always a fresh VIES check: during an outage it ends in a 503 rather than a stored or register answer, unless you pass cache=true or fallback=true.
What Avatcado does when VIES is down
Avatcado takes these steps in order, and the response says which one answered:
- It retries the VIES call inside the same request, on every plan, with a short pause and random jitter between attempts.
GLOBAL_MAX_CONCURRENT_REQis the one availability error it does not retry. - On Pro and Business, for the 10 EU countries it covers, it asks that country's national tax register. A register answer that confirms the number is served with
meta.source_status: "fallback"andmeta.sourcenaming the register. - On every plan, it serves the most recent stored result for that number with
meta.source_status: "unavailable". - When none of these can answer, it returns a
503with the codeupstream_member_state_unavailableorupstream_unavailable. The 503 does not count against your monthly quota.
If VIES hangs on every attempt, the request can reach the API's time limit before either code is returned. Treat a timeout or a dropped connection the same way, as unchecked.
A normal (live) response:
curl "https://api.avatcado.com/v1/validate?vat_number=IT12345678901" \
-H "Authorization: Bearer avat_live_your_api_key"{
"data": {
"valid": true,
"vat_number": "IT12345678901",
"country_code": "IT",
"company": {
"name": "ESEMPIO S.R.L.",
"address": "VIA ROMA 1, 00100 ROMA"
},
"requested_at": "2026-03-24T10:30:00Z"
},
"meta": {
"request_id": "550e8400-e29b-41d4-a716-446655440000",
"request_duration_ms": 1420,
"source": "vies",
"source_status": "live",
"cached": false,
"stale": false
}
}A stored result served while the member state is down:
{
"data": {
"valid": true,
"vat_number": "IT12345678901",
"country_code": "IT",
"company": {
"name": "ESEMPIO S.R.L.",
"address": "VIA ROMA 1, 00100 ROMA"
},
"requested_at": "2026-02-25T14:00:00Z"
},
"meta": {
"request_id": "661f9500-f30c-52e5-b827-557766551111",
"request_duration_ms": 45,
"source": "vies",
"source_status": "unavailable",
"cached": true,
"cached_at": "2026-02-25T14:00:00Z",
"stale": true
}
}What each meta field tells you:
cached: truemeans the result came from a stored row, not a live lookup.cached_atis when the original lookup happened.stale: truemeans the stored result is older than the cache window and was served only because the upstream is unavailable.source_status: "unavailable"means the member state service was down when Avatcado tried to reach it.source_status: "fallback"means the member state was down and its national tax register confirmed the number as VAT registered. A register that does not confirm the number is never served; the request moves on to the stored result.source_status: "degraded"means VIES returned a result, but Avatcado detected a possible silent false negative (some member states return "invalid" for valid numbers during partial outages) and served the earlier valid result.
When nothing is stored, the 503 error response still identifies the attempt: it echoes the normalized vat_number you submitted inside the error object and carries a meta.validation_id for the recorded attempt, so your logs show which number was not checked.
Handling the response in your code
This TypeScript example keeps a number that was not checked apart from an invalid one, and logs which step answered:
const vatNumber = "IT12345678901";
// A dropped connection rejects, and a gateway timeout can come back without
// a JSON body. Both leave the number unchecked, like a 503.
const response = await fetch(
`https://api.avatcado.com/v1/validate?vat_number=${vatNumber}`,
{ headers: { Authorization: "Bearer avat_live_your_api_key" } }
).catch(() => null);
const body = response ? await response.json().catch(() => null) : null;
if (!response || !body || response.status >= 500) {
// upstream_member_state_unavailable, upstream_unavailable, any other 5xx,
// a timeout or a dropped connection: the number was not checked. Store it
// as unchecked and validate it again later.
const reason = body?.error?.code ?? (response ? `HTTP ${response.status}` : "no response");
console.warn(`${vatNumber} not checked (${reason}), retry later`);
} else if (body.error) {
console.error(`${body.error.code}: ${body.error.message}`);
} else {
const { data, meta } = body;
if (data.valid) {
if (meta.stale) {
// Valid, but from a stored result older than the cache window.
// Flag the record for a fresh check once the member state is back.
console.log("Valid (stale stored result, upstream was down)");
} else {
console.log("Valid");
}
}
// Log the source status for monitoring
if (meta.source_status === "fallback") {
console.info(`VIES down for ${data.country_code}, answered by the national register (${meta.source})`);
} else if (meta.source_status === "unavailable") {
console.warn(`VIES unavailable for ${data.country_code}`);
} else if (meta.source_status === "degraded") {
console.warn(`VIES degraded for ${data.country_code}, result may be unreliable`);
}
}Keep reading
The VIES uptime page shows the failure rate per member state, the VIES error reference covers each error code, and the VIES API guide covers calling VIES directly.
Avatcado's Free plan includes 500 validations a month, with the retries and the stored result step. The national register step needs Pro or Business.
Frequently asked questions
How often does VIES go down?
VIES has no single availability figure, because each check depends on the database of the member state that issued the number, and each member state runs its own. Some downtime is planned: the VIES FAQ lists regular unavailability windows for some member states, such as Germany, which it lists as unavailable daily from 11:00 PM to 01:30 AM. For measured figures, Avatcado's VIES uptime page shows the failure rate of each member state on its own production traffic, and each VIES error page shows how often that code occurs.
Does a VIES availability error mean the VAT number is invalid?
No. MS_UNAVAILABLE, MS_MAX_CONCURRENT_REQ, TIMEOUT, SERVICE_UNAVAILABLE, GLOBAL_MAX_CONCURRENT_REQ and VOW-ERR-11 all mean VIES could not complete the check, so the number was not checked. Normally, VIES reports a number as invalid only after the member state's database was asked and does not record it. During a partial outage, some member states answer invalid for valid numbers instead of returning an error; when Avatcado holds an earlier valid result for that number, it serves that result with source_status 'degraded'. Store an availability error as unchecked, keep it apart from invalid, and check the number again later.
How can I check whether VIES is down right now?
The VIES technical information page shows the status of each member state, and GET /check-status on the VIES REST API lists every country as Available, Unavailable or Monitoring Disabled, next to a flag for VIES itself. Avatcado's VIES uptime page adds the failure rate of each member state measured on its own production traffic.
What does source_status: 'degraded' mean?
It means VIES answered valid: false with no error code, while the most recent stored result for the same number is valid: true. Some member states report valid numbers as invalid during partial outages, and a raw VIES response of that kind looks the same as an unregistered number. Avatcado treats the answer as a likely false negative, serves the stored result instead and sets meta.source_status to 'degraded'. A number that really was deregistered produces the same status, so treat 'degraded' as a reason to check the number again later. The other statuses: 'live' is a fresh upstream answer, 'cached' is a stored result served without calling the upstream, 'unavailable' is a stored result served during an outage, and 'fallback' is a national register confirming the number while VIES was down.
Is it safe to accept a stale cached VAT validation?
meta.stale: true means the stored result is older than the cache window and was served only because the upstream was unavailable, and meta.cached_at tells you when the original check ran. The result shows what the member state recorded on that day, and a registration can end after it. A workable policy: accept a stale valid result for routine orders and flag the record for a fresh check once the member state is back. For high-value orders, hold the decision until a fresh check succeeds.
What happens when VIES is down for a number I have never validated?
With nothing stored and no national register answer, Avatcado returns a 503 with a machine-readable code: upstream_member_state_unavailable when the last VIES answer was an availability error, a TIMEOUT fault from VIES included, or upstream_unavailable when the last call to VIES failed or ran into Avatcado's own 30 second limit. It never returns valid: false for a number it could not check, and the 503 does not count against your monthly quota. Handle it as unchecked: let the customer continue, store the number, and validate it again once the member state is back. If VIES hangs on every attempt, the request can reach the API's time limit before either code is returned; treat a timeout or a dropped connection the same way. For background jobs, retry with exponential backoff.
Sources
- VIES on the Web: frequently asked questions European Commission, accessed November 12, 2026
- VIES on the Web: technical information European Commission, accessed November 12, 2026
- VIES checkVatService WSDL European Commission, accessed November 12, 2026
- VIES REST API contract (check-status) European Commission, accessed November 12, 2026
Related guides
VIES API Guide: REST Endpoint, SOAP & Integration
Use the official VIES REST API from Node.js, handle HTTP 200 faults, preserve consultation evidence, compare SOAP, and plan for member-state downtime.
Validate EU VAT Numbers via API: Developer Guide
Learn how to validate EU VAT numbers, plus UK, Swiss, Norwegian, and Australian VAT/GST, via REST API. Covers VIES, HMRC, TypeScript, Python, and test mode.
How to Validate VAT Numbers in TypeScript
Validate EU, UK, Swiss, Norwegian, and Australian VAT/GST numbers in TypeScript with @avatcado/node. Covers error handling, batch validation, and test mode.
Async VAT Validation: Webhooks and Batch Processing
Learn how to validate VAT numbers asynchronously using webhooks and batch processing. Covers checkout latency, bulk revalidation, and VIES downtime resilience.