VIES Error

GLOBAL_MAX_CONCURRENT_REQ

Global VIES concurrent request limit reached

What does GLOBAL_MAX_CONCURRENT_REQ mean?

The GLOBAL_MAX_CONCURRENT_REQ error means the entire VIES system, not just a specific member state, has reached its maximum capacity. The EU's central VAT validation infrastructure is overloaded and rejecting new requests.

This is a more severe error than MS_MAX_CONCURRENT_REQ because it affects all countries, not just one. When this happens, no VAT validations can succeed through VIES.

When does this error occur?

  • During periods of extremely high traffic across the EU
  • When multiple large systems are bulk-validating VAT numbers simultaneously
  • During EU-wide business events (tax deadlines, end of quarter)
  • Less common than per-country limits, but more disruptive when it happens

Why is this a problem?

Unlike member state rate limits where you might validate against a different country, global rate limits block everything. If your application depends on real-time VAT validation, this error can halt critical business processes like checkout flows or invoice generation.

This affects everyone

When GLOBAL_MAX_CONCURRENT_REQ occurs, every application using VIES is affected. There's nothing special about your request. The entire system is at capacity.

How to handle GLOBAL_MAX_CONCURRENT_REQ

1. Use a service with fallback data sources

VatDB maintains connections to multiple official EU and national databases that operate independently of VIES. When the central EU system is overloaded, these alternative sources often remain available. Set up webhooks to get notified when your validation completes.

2. Implement exponential backoff with longer delays

Global limits typically take longer to clear than per-country limits. Start with longer initial wait times and use more aggressive backoff multipliers.

3. Have a fallback strategy

Consider what your application should do when validation is impossible: - Accept the transaction and validate asynchronously later - Show a user-friendly message and allow retry - Queue the validation for background processing

Don't let VIES outages block your business

VatDB validates VAT numbers using multiple official data sources. When VIES hits global rate limits, we route requests to national databases automatically. Your validations succeed even when the EU system is down. Use webhooks to handle async validation seamlessly.

Try VatDB Free

Frequently Asked Questions

What's the difference between GLOBAL_MAX_CONCURRENT_REQ and MS_MAX_CONCURRENT_REQ?
MS_MAX_CONCURRENT_REQ means one country's limit is reached, so you might still validate other countries. GLOBAL_MAX_CONCURRENT_REQ means the entire VIES system is overloaded and no validations can succeed.
How often does GLOBAL_MAX_CONCURRENT_REQ occur?
Less frequently than per-country limits, but it does happen during peak periods. It's more common around tax deadlines, quarter ends, and other EU-wide business events.
Should I use longer retry delays for global limits?
Yes. Global limits affect the entire system and typically take longer to clear. Use longer initial delays and more aggressive backoff multipliers.
How does VatDB handle global rate limits?
VatDB connects to national databases that operate independently of the central VIES system. When VIES is at global capacity, we automatically route requests to available national sources. You can also use webhooks to receive results asynchronously when sources become available.