MS_MAX_CONCURRENT_REQ_TIME
Member state time-based rate limit active
What does MS_MAX_CONCURRENT_REQ_TIME mean?
The MS_MAX_CONCURRENT_REQ_TIME error is a variant of the standard rate limit error that relates to time-based throttling in the member-state path. In practice, this usually reflects sustained traffic pressure toward that country's backend, not only your own request stream. VIES does not fully disclose its internal throttling logic, so client or IP-level policies may also contribute.
This is subtly different from MS_MAX_CONCURRENT_REQ: - MS_MAX_CONCURRENT_REQ: Concurrent requests at this moment exceed limits - MS_MAX_CONCURRENT_REQ_TIME: Requests over a time period exceed limits
When does this error occur?
- During sustained high-volume traffic toward one member state
- When overall demand (including other users) exceeds that country's sustained throughput
- When your own traffic pattern contributes to a time-window throttle
Time windows
The exact time windows are not published. Based on observed behavior they may include: - Short window: Requests per second limit - Medium window: Requests per minute limit - Long window: Requests per hour limit
Hitting one or more of these thresholds can trigger the error.
Slow down your request rate
This error indicates time-window throttling on the member-state path. Your traffic may be part of the trigger, but shared load from other users can also cause it. Reduce throughput and retry with backoff.
How to handle MS_MAX_CONCURRENT_REQ_TIME
1. Use a high-volume VAT validation service
VatDB manages request rates across all data sources automatically. Our infrastructure handles thousands of validations per minute without hitting rate limits by connecting to multiple official EU and national databases. Use webhooks to receive results asynchronously without rate limit concerns.
2. Implement proper rate limiting
Don't just retry. Reduce your request rate. Limit to 1 request per second per country and add delays between requests.
3. Spread requests across time
If you have bulk validations, spread them out rather than running them all at once.
4. Use queuing
Queue requests and process them at a sustainable rate instead of attempting immediate validation.
High-volume VAT validation without rate limits
VatDB manages request rates across multiple official EU and national databases automatically. Our infrastructure handles thousands of validations per minute without hitting rate limits. Use webhooks to receive results asynchronously. Scale your validation without throttling headaches.
Try VatDB FreeFrequently Asked Questions
What's the difference between MS_MAX_CONCURRENT_REQ and MS_MAX_CONCURRENT_REQ_TIME?
MS_MAX_CONCURRENT_REQ usually indicates an immediate concurrent-capacity limit. MS_MAX_CONCURRENT_REQ_TIME indicates a time-window throttle. Both can be influenced by shared member-state load, and VIES does not publish the exact internal rules.
How long should I wait before retrying?
Longer than for standard rate limits. Wait at least 10 to 30 seconds, then resume at a slower rate. The time window needs to expire before your request count resets.
Can I avoid this by spreading requests across countries?
Often yes, because pressure is typically member-state specific. But this is not guaranteed: VIES may also apply broader or undisclosed controls.
How does VatDB handle high-volume validation?
VatDB distributes requests intelligently across multiple official sources and manages per-country rate limits automatically. We process high volumes by using our infrastructure's capacity rather than maxing out VIES limits. Webhooks let you handle results asynchronously.