VIES Error

GLOBAL_MAX_CONCURRENT_REQ_TIME

Global VIES time-based rate limit active

What does GLOBAL_MAX_CONCURRENT_REQ_TIME mean?

The GLOBAL_MAX_CONCURRENT_REQ_TIME error indicates that the entire VIES system's time-based rate limit has been triggered. This isn't about concurrent requests at this instant. It's about total request volume over a time window across the whole system.

This is the most severe rate limiting error. It means VIES is protecting itself from overall overload, affecting all users and all member states.

When does this error occur?

  • During extreme high-traffic events across the EU
  • When multiple large organizations are running bulk validations simultaneously
  • During end-of-quarter or tax deadline rushes
  • Less common than per-country limits, but more impactful

Why is this different from GLOBAL_MAX_CONCURRENT_REQ?

Error Meaning
GLOBAL_MAX_CONCURRENT_REQ Too many simultaneous requests right now
GLOBAL_MAX_CONCURRENT_REQ_TIME Too many total requests over a time period

Time-based limits persist longer because the system tracks your request history, not just current load.

System-wide throttling in effect

This error affects the entire VIES infrastructure. All users experience degraded service when this limit is active. Reduce your request rate significantly.

How to handle GLOBAL_MAX_CONCURRENT_REQ_TIME

1. Use a service with alternative data sources

VatDB's architecture doesn't rely exclusively on VIES. We maintain connections to multiple official EU and national databases. When VIES is throttling globally, we validate through alternative channels. Use webhooks to receive results when validation completes asynchronously.

2. Back off significantly

This isn't a momentary spike. Reduce your request rate substantially. Use longer delays between retries, starting with 1 minute and doubling on each attempt.

3. Queue and defer

Move non-urgent validations to background processing. Accept transactions and validate asynchronously later.

Validate without VIES limits

VatDB doesn't depend solely on VIES. When global rate limits hit, we route to official national databases and alternative sources. Your validations continue while others wait for VIES to recover. Use webhooks to handle async validation seamlessly.

Try VatDB Free

Frequently Asked Questions

How long do global time-based limits last?
Longer than instant limits. Expect 5 to 30 minutes for the time window to reset, depending on overall system load. During severe events, throttling may persist for hours.
Does this affect all users or just me?
GLOBAL limits affect all VIES users. However, your individual request rate contributes to the limit. Heavy users are more likely to trigger and experience these limits.
Should I switch to a different IP to avoid this?
No. Global limits are system-wide, not per-IP. Switching IPs doesn't help and may trigger IP_BLOCKED errors if you appear to be evading limits.
How does VatDB handle global VIES throttling?
VatDB's architecture doesn't rely exclusively on VIES. We maintain connections to official national databases and other authoritative sources. When VIES is throttling globally, we validate through alternative channels. Webhooks notify you when validation completes.