Is E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) down?
Down
Yes, E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) is down.
It has failed every check since 27 Oct 2026, 20:32 UTC (13 days 18 h, 11 checks). Latest error: initialize returned HTTP 404. It last passed on 27 Oct 2026, 07:08 UTC.
Latest check
- Last check
- 6 h ago (10 Nov 2026, 08:38 UTC)
- Response time
- Not measured (typical 98 ms)
- Next check
- In about 3 days
- How often
- About every 33 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 33 hours over the last 7 days.
Outages in the last 30 days
1 outage, 13 days 18 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 27 Oct 2026, 20:32 UTC | Ongoing, 13 days 18 h so far | 11 | initialize returned HTTP 404 |
Times are when our checks ran, about every 33 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 08:38 UTC | initialize returned HTTP 404 | 404 | 260 ms |
| 7 Nov 2026, 03:41 UTC | initialize returned HTTP 404 | 404 | 232 ms |
| 5 Nov 2026, 22:21 UTC | initialize returned HTTP 404 | 404 | 230 ms |
| 4 Nov 2026, 13:09 UTC | initialize returned HTTP 404 | 404 | 232 ms |
| 3 Nov 2026, 03:50 UTC | initialize returned HTTP 404 | 404 | 306 ms |
| 1 Nov 2026, 18:59 UTC | initialize returned HTTP 404 | 404 | 248 ms |
| 31 Oct 2026, 12:38 UTC | initialize returned HTTP 404 | 404 | 212 ms |
| 30 Oct 2026, 04:25 UTC | initialize returned HTTP 404 | 404 | 245 ms |
| 28 Oct 2026, 23:21 UTC | initialize returned HTTP 404 | 404 | 259 ms |
| 28 Oct 2026, 09:43 UTC | initialize returned HTTP 404 | 404 | 290 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 33 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.