🇳🇱VIES Status for the Netherlands
Whether the NL node is answering right now, every outage we have recorded, and the hours it fails most often. Read from the European Commission’s own availability feed every 15 minutes.
Right Now
Read 13:36 UTC · Thursday, 13 August 2026- Last 24 hours
- 100.00%
- Last 7 days
- 99.85%
- Last 30 days
- 99.86%
- Rank among member states
- #15 of 28
Figures cover 7 days of our samples (725 for NL), capped at 30 days — not a full month yet unless it says so. All member states averaged 98.78% over the same window.
When the Netherlands Was Unavailable
1 separate outage, 15 min of observed downtime in total. Times are UTC. Sampling is every 15 minutes, so each window is accurate to within one interval on each side.
| Date | Window (UTC) | Length | Reported state |
|---|---|---|---|
| Sunday, 9 August 2026 | 04:31 – 04:46 | 15 min | Unavailable |
Day by Day
One column per UTC day. The number above a column is the percentage of readings that failed that day; a blank means every reading came back.
The Hours the Netherlands Goes Quiet
In our samples, the weakest hour is 04:00–05:00 UTC at 96.88% across 32 readings, and the weakest day is Sunday at 98.92%. That is a description of what we recorded, not a schedule — treat it as a hint about when to retry, not a promise.
By hour of day (UTC)
By weekday
Weekday × Hour
Collecting. A weekday-by-hour grid needs at least 14 days of samples before each of its 168 slots holds more than a reading or two — we have 7. Publishing it now would be showing you noise.
What Happens to Your Checks When the Netherlands Is Down
Nothing validates against a member state that is not answering — not vatnode, not any other provider, not the tax authority’s own portal. VIES stores no data of its own: every answer comes from the member state live, so there is no cache to fall back on and no way to fake one honestly.
What an API can do is fail in a way you can act on. A NL outage comes back as VIES_UNAVAILABLE with HTTP 503 — never as “invalid”, which would have you rejecting real customers over someone else’s downtime. Monitoring re-runs the check through the day and tells you when the answer finally lands.
For the Netherlands there is no national fallback route today — VIES is the only official source vatnode can reach, so a NL outage is a hard stop until the node returns. When it does answer, the response carries the registered name and address alongside the validity flag.
Full error semantics are in the API docs. For vatnode’s own uptime rather than VIES, see System Status.
Netherlands VAT Number Format and Checks
- VIES prefix
- NL
- Format
- NL + 9 digits + B + 2 digits
- Example
- NL805734958B01 — Booking.com BV
- Standard VAT rate
- 21% — Belasting over de toegevoegde waarde (btw)
Questions People Ask
- Is VIES down for the Netherlands right now?
- No. At our last reading the NL node was answering VIES requests. The reading is at most 15 minutes old, and a member state can drop out between samples.
- Why does a valid Dutch VAT number fail to validate?
- If the number is well-formed and the NL node is unavailable, the failure is upstream, not in the number. VIES returns a service error rather than "invalid", and any provider that turns that into "invalid" is lying to you. vatnode returns a distinct VIES_UNAVAILABLE error with HTTP 503 so your code can retry instead of rejecting a real customer.
- Does the Netherlands publish a VIES maintenance schedule?
- The Commission publishes a general VIES maintenance notice, but member states take their own systems down without announcing it to API consumers. That is why this page exists: the recorded history shows when the NL node was actually unreachable, whatever the schedule says.
- Can I still validate a Dutch VAT number during an outage?
- Not against VIES. What you can do is queue the check and retry — vatnode's monitoring re-runs a subscription's checks through the day and tells you when the answer finally lands, so a customer is not blocked by a member state's downtime.
- Where does this data come from?
- From the European Commission's own check-status endpoint, sampled every 15 minutes and kept. It is the Commission's view of its member states, not an independent probe, so it can lag a node going down and it describes reachability rather than whether one particular number validates.