EU VAT guide
GLOBAL_MAX_CONCURRENT_REQ VIES error
GLOBAL_MAX_CONCURRENT_REQ means the VIES service is receiving too many concurrent requests globally.
GLOBAL_MAX_CONCURRENT_REQ means the VIES service is receiving too many concurrent requests globally.
Meaning
This is a traffic-limit response from the VIES side. It does not tell you whether the VAT number is valid or invalid.
High-volume tools should slow down, queue checks, and retry later instead of increasing concurrency.
For API integrations
Treat this error as retryable and store it as an unavailable status until a later validation succeeds or fails.
Avoid exposing this as a customer data issue; it is an upstream capacity condition.
Validating VAT numbers at volume?
Join the batch/API list for CSV validation, retries, audit exports, and developer access.
Related VIES guides
- MS_MAX_CONCURRENT_REQ VIES errorMS_MAX_CONCURRENT_REQ means one national VAT registry is refusing concurrent VIES requests, not that the VAT number is bad. How to back off safely, plus live per-country VIES status.
- INVALID_INPUT VIES errorFix INVALID_INPUT errors when sending EU VAT numbers to VIES.
- EU VAT number formatCountry-by-country basics for EU VAT number formats before a VIES check.
- VAT number format checkCheck whether a VAT number format looks valid before running a VIES lookup.
- VIES name and address resultsWhy VIES sometimes returns a company name and address and sometimes does not.
- Batch VAT validationHow batch EU VAT validation should handle VIES retries, evidence, and privacy.