All Systems Operational

VIES Uptime Monitor

How often VIES, HMRC and the Swiss, Norwegian and Australian VAT registers answered the checks Avatcado sent them, and how fast, measured on Avatcado's own production traffic. The figures cover the last 30 days unless you pick another range, and the page refreshes every 5 minutes.

Updated just now

Uptime

97.9%

Avg Response

2259ms

P95 Response

12180ms

Error Rate

2.1%

Avg attempt no.

4.0

Avg attempt no. averages the attempt number over every call to the registers: 1.0 means no check needed a retry, and checks that needed many attempts weigh more.

Uptime by registry

Last 30 days

VIES
27 EU states + XI
VIES: 97.6% uptime across 27 monitored countries; outage: MT, EL, SK; degraded: PL, DK, FR.
97.6%
HMRC
GB
HMRC: 100% uptime across 1 monitored country.
100%
BFS UID
CH, LI
BFS UID: 100% uptime across 2 monitored countries.
100%
BRONNOYSUND
NO
BRONNOYSUND: 100% uptime across 1 monitored country.
100%
ABR
AU
ABR: 100% uptime across 1 monitored country.
100%

operational degraded outage1 cell = 1 monitored country

Slowest countries

CountryAvg responseUptimeStatus
RO๐Ÿ‡ท๐Ÿ‡ดRomania
11401ms100%OK
LU๐Ÿ‡ฑ๐Ÿ‡บLuxembourg
7992ms96.3%FLAKY
CZ๐Ÿ‡จ๐Ÿ‡ฟCzech Republic
5009ms98.4%OK
BE๐Ÿ‡ง๐Ÿ‡ชBelgium
3500ms98.4%OK
DK๐Ÿ‡ฉ๐Ÿ‡ฐDenmark
3245ms87.8%FLAKY
LV๐Ÿ‡ฑ๐Ÿ‡ปLatvia
3070ms100%OK
FR๐Ÿ‡ซ๐Ÿ‡ทFrance
2986ms93.6%FLAKY
SE๐Ÿ‡ธ๐Ÿ‡ชSweden
2924ms98.2%OK

Over the last 30 days, 97.9% of checks sent to VIES, HMRC and the other registers got a usable answer after Avatcado's retries on VIES. Calls to the registers took 2259ms on average, with a P95 of 12180ms.

Lithuania had the highest uptime, at 100%, and Malta the lowest, at 20%.

Reading this page: the figures below measure VIES and the other VAT registers Avatcado calls. Avatcado's own API availability is not part of them.

Why VIES goes down

VIES holds no VAT numbers itself. The European Commission runs it as a relay: it forwards each check to the tax authority of the member state that issued the number and returns whatever that system replies. Each member state runs its own system, with its own limit on parallel requests and its own maintenance windows, so availability differs by country. The per-country table below shows which member states failed most often in the selected range.

VIES returns errors such as MS_UNAVAILABLE and MS_MAX_CONCURRENT_REQ without saying when to try again, so each caller has to decide when to retry and what to do when a check never completes. In a B2B billing flow that must verify the customer's VAT number before invoicing under the reverse charge (Council Directive 2018/1910, with the consultation number as optional evidence of the check), an unanswered check means the invoice waits or goes out unverified.

What Avatcado does when VIES fails

Avatcado calls VIES (and HMRC, the Swiss BFS UID Register, the Norwegian Brรธnnรธysund Register and the Australian ABR) for you and adds three things on top:

  • A cache of recent valid results. When a register cannot answer, the most recent stored result for that number can be served. Requests that carry a requester VAT number skip the cache by default, so a consultation number is always the product of a fresh VIES check; pass cache=true to accept a stored result instead, which repeats the consultation number from the earlier check with the same requester.
  • Retries on fault codes that can clear, such as MS_UNAVAILABLE, and on transport timeouts, with a short constant delay plus jitter. The rule is the same for every EU member state; HMRC and the other registers get one attempt per check.
  • A machine-readable error when a country cannot answer and there is no stored result, unless VIES hangs on every attempt and the request reaches the API's own time limit first. The upstream error code is passed through, so your system can decide whether to block the transaction, retry it later, or accept it and check the number again afterwards.

On Pro and Business plans, a check VIES cannot answer can also go to the national register in the 10 EU countries that have one, before a stored result is used.

What the numbers below mean

Uptime is the share of checks that got a usable answer from the register after Avatcado's retries on VIES. The other registers get one attempt per check. Each check counts once, however many attempts it took, and a check VIES failed counts as failed even when a national register or a stored result answered it afterwards. A check answered from the cache is not counted itself: Avatcado then re-checks the number in the background, a re-check that gets a usable answer counts as a successful check, and a re-check that fails is not recorded. Test keys are left out; checks made through the demo checker on this site are included. Response times are measured per call to the register, so each retry adds a call. The Avg attempt no. figure averages the attempt number over those calls: 1.0 means no check needed a retry, and checks that needed many attempts weigh more.

These are Avatcado's own observations, not an official EU statistic. A country with few checks in the selected range has a noisier figure, because one failure moves its rate further. Two kinds of check are missing from the data: failed background re-checks, and requests cut off by the API's own time limit before they finished. Both are failures, so the uptime shown can be higher than the registers' real availability and higher than what callers experienced. In the registry bars and the per-country table, a country shows as degraded from 5% failed checks and as an outage above 20%.

Almost every VAT validation API checks EU numbers through the same VIES service, so these failures reach all of them. When you compare vendors, ask what each one returns when VIES has no answer.

Per-country breakdown

Each country in the selected range, highest error rate first. Avg Response and P95 Response are per call to the register. Avg attempt no. is the average attempt number over those calls: 1.0 means no check needed a retry, and checks that needed many attempts weigh more.

๐Ÿ‡ฒ๐Ÿ‡นMalta
20%

Avg Response

34ms

Error Rate

80%

๐Ÿ‡ฌ๐Ÿ‡ทGreece
27.3%

Avg Response

385ms

Error Rate

72.7%

๐Ÿ‡ธ๐Ÿ‡ฐSlovakia
75%

Avg Response

149ms

Error Rate

25%

๐Ÿ‡ต๐Ÿ‡ฑPoland
84.6%

Avg Response

743ms

Error Rate

15.4%

๐Ÿ‡ฉ๐Ÿ‡ฐDenmark
87.8%

Avg Response

3245ms

Error Rate

12.2%

๐Ÿ‡ซ๐Ÿ‡ทFrance
93.6%

Avg Response

2986ms

Error Rate

6.4%

๐Ÿ‡ณ๐Ÿ‡ฑNetherlands
95.4%

Avg Response

2764ms

Error Rate

4.6%

๐Ÿ‡ฑ๐Ÿ‡บLuxembourg
96.3%

Avg Response

7992ms

Error Rate

3.7%

๐Ÿ‡ฆ๐Ÿ‡นAustria
97.7%

Avg Response

2109ms

Error Rate

2.3%

๐Ÿ‡ซ๐Ÿ‡ฎFinland
97.8%

Avg Response

461ms

Error Rate

2.2%

๐Ÿ‡ฉ๐Ÿ‡ชGermany
97.8%

Avg Response

2192ms

Error Rate

2.2%

๐Ÿ‡ธ๐Ÿ‡ชSweden
98.2%

Avg Response

2924ms

Error Rate

1.8%

๐Ÿ‡ง๐Ÿ‡ชBelgium
98.4%

Avg Response

3500ms

Error Rate

1.6%

๐Ÿ‡จ๐Ÿ‡ฟCzech Republic
98.4%

Avg Response

5009ms

Error Rate

1.6%

๐Ÿ‡ฎ๐Ÿ‡นItaly
99.4%

Avg Response

2318ms

Error Rate

0.6%

๐Ÿ‡ต๐Ÿ‡นPortugal
99.7%

Avg Response

1753ms

Error Rate

0.3%

๐Ÿ‡ฑ๐Ÿ‡นLithuania
100%

Avg Response

523ms

Error Rate

0%

๐Ÿ‡จ๐Ÿ‡พCyprus
100%

Avg Response

480ms

Error Rate

0%

๐Ÿ‡ฑ๐Ÿ‡ปLatvia
100%

Avg Response

3070ms

Error Rate

0%

๐Ÿ‡จ๐Ÿ‡ญSwitzerland
100%

Avg Response

271ms

Error Rate

0%

๐Ÿ‡ง๐Ÿ‡ฌBulgaria
100%

Avg Response

1386ms

Error Rate

0%

๐Ÿ‡ณ๐Ÿ‡ดNorway
100%

Avg Response

210ms

Error Rate

0%

๐Ÿ‡ท๐Ÿ‡ดRomania
100%

Avg Response

11401ms

Error Rate

0%

๐Ÿ‡ธ๐Ÿ‡ฎSlovenia
100%

Avg Response

674ms

Error Rate

0%

๐Ÿ‡ช๐Ÿ‡ชEstonia
100%

Avg Response

159ms

Error Rate

0%

๐Ÿ‡ฆ๐Ÿ‡บAustralia
100%

Avg Response

2084ms

Error Rate

0%

๐Ÿ‡ช๐Ÿ‡ธSpain
100%

Avg Response

364ms

Error Rate

0%

๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom
100%

Avg Response

96ms

Error Rate

0%

๐Ÿ‡ญ๐Ÿ‡ทCroatia
100%

Avg Response

237ms

Error Rate

0%

๐Ÿ‡ญ๐Ÿ‡บHungary
100%

Avg Response

213ms

Error Rate

0%

๐Ÿ‡ฎ๐Ÿ‡ชIreland
100%

Avg Response

496ms

Error Rate

0%

๐Ÿ‡ฑ๐Ÿ‡ฎLiechtenstein
100%

Avg Response

129ms

Error Rate

0%

Response times by country

Average time per call to the register, in milliseconds, slowest first (up to 20 countries). Each retry is a separate call.

Error distribution

The fault codes Avatcado recorded most often across all countries, counted per call to the register, so retries are included and one failing check can add several. The uptime figures above count each check once.

What these VIES codes mean: MS_MAX_CONCURRENT_REQ, MS_UNAVAILABLE, TIMEOUT

Retries on every plan, national registers on Pro and Business

When VIES has no answer, Avatcado retries the check, then on Pro and Business asks the national register in 10 EU countries. The free plan includes 500 checks a month.

Frequently asked questions

It depends on the member state, because VIES passes each check to the system of the country that issued the number. The European Commission publishes no uptime guarantee for VIES. This page shows the share of Avatcado's checks that each member state answered, measured on Avatcado's production traffic, so you can compare countries over 24 hours to 90 days.

VIES forwards each check to the system of the member state that issued the number, and each member state runs its own system, so response times differ by country. When a member state has too many requests in progress it answers MS_MAX_CONCURRENT_REQ, and the retry adds time. Avatcado retries those errors automatically and can answer a repeat check from its cache.

Avatcado first retries the check. If VIES still has no answer, on Pro and Business plans it checks the national register for the 10 EU countries that have one: Romania, the Czech Republic, Finland, France, Latvia, Slovakia, Slovenia, Croatia, Estonia and Belgium; see the full coverage page for how each one behaves. Otherwise it returns the most recent stored result for that number, marked meta.cached: true. If there is no stored result, you receive a 503 error with a machine-readable error code, unless VIES hangs on every attempt and the request reaches the API's own time limit first. Requests that send a requester VAT number skip the register and the stored result unless they opt in.

It retries fault codes that can clear, such as MS_UNAVAILABLE and timeouts, with a short delay plus jitter. On Pro and Business plans it then asks the national register in the 10 EU countries that have one. After that it can serve the most recent stored result for the number, and if there is none it returns an error with a machine-readable code, unless VIES hangs on every attempt and the request reaches the API's own time limit first.

Every 5 minutes. The figures come from Avatcado's production calls to VIES, HMRC and the Swiss, Norwegian and Australian registers, with test keys left out. The status badge at the top of the page covers only the last 15 minutes.

VIES (VAT Information Exchange System) validates VAT numbers for all 27 EU member states plus Northern Ireland. HMRC validates UK VAT numbers separately since Brexit. Avatcado provides a single endpoint that automatically routes to the correct service based on the VAT number prefix, so you don't need to integrate both services.