EU VAT guide

MS_MAX_CONCURRENT_REQ VIES error

MS_MAX_CONCURRENT_REQ means the selected member-state VAT registry is receiving too many concurrent requests through VIES.

MS_MAX_CONCURRENT_REQ means the selected member-state VAT registry is receiving too many concurrent requests through VIES.

Country-specific limit

The VIES gateway may be reachable while a single national registry is overloaded or rate-limited.

A German VAT check and a French VAT check can therefore return different availability outcomes at the same moment.

How to handle it

Retry later and consider per-country concurrency limits if you run repeated validations.

Do not convert this response into invalid customer VAT data.

Back off per country, not globally

The limit is the member state's, so throttling your whole queue punishes the 27 countries that were answering fine. Keep one concurrency budget per country code and one retry clock per country code.

Exponential backoff with jitter beats a fixed delay here: a fixed delay makes every one of your workers come back at the same instant and trip the same limit again.

Before you tune anything, check whether that registry is simply unavailable. Rate limiting and an outage produce the same failed batch and need opposite responses — one wants slower retries, the other wants no retries at all until it returns.

Validating VAT numbers at volume?

Join the batch/API list for CSV validation, retries, audit exports, and developer access.

Explore API & batch options

Related VIES guides

Check a VAT number

You can paste the full VAT ID with country prefix, or choose the country and enter the local number.