Peppol Access Point status and uptime monitor
Check the current status, measured uptime and response time of Peppol Access Point AS4 endpoints and selected public provider APIs.
An AS4 endpoint is the network address an Access Point uses to receive Peppol messages from other Access Points. A public provider API is a separate interface offered by a provider for customer or system integrations. It is not part of the standardized Peppol transport. The two categories are monitored and reported separately.
Qvalia checks each listed endpoint every five minutes and reports the share of checks that receive an HTTP response below 500. The figures measure endpoint reachability, not successful Peppol message processing, delivery or contractual availability.
- Check interval: every 5 minutes
- Method: HTTPS request from UptimeRobot
- Counted as responding: any HTTP response below 500 within 30 seconds
- Endpoints: taken from each provider’s public SMP registration
| Provider | Country | Now | 24 h | 7 d | 30 d | 90 d | Avg. response (24 h) |
|---|---|---|---|---|---|---|---|
| Qvalia AB PSE000094 | SE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 332 ms |
| @GP POP000474 | FR | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 285 ms |
| Aruba PEC PIT000503 | IT | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 550 ms |
| Axway PBE000078 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 362 ms |
| B2Brouter Global SL POP000016 | ES | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 740 ms |
| Banqup SA PBE000122 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 357 ms |
| BIAC Log Sa PLU000514 | LU | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 427 ms |
| Billberry POP000739 | EE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 653 ms |
| Billit nv PBE000076 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 308 ms |
| Centara ehf PIS000601 | IS | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 437 ms |
| Comarch S.A. PPL000238 | PL | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 427 ms |
| Comax PBE000704 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 480 ms |
| Crediflow AB PSE000091 | SE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 484 ms |
| Digiteal PBE000079 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 331 ms |
| Document Centric Solutions PIE000136 | IE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 251 ms |
| DocuMI srl PIT000296 | IT | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 638 ms |
| E Stream MSC Sdn Bhd PMY000621 | MY | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 724 ms |
| eConnect International B.V. PNL000052 | NL | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 336 ms |
| ecosio InterCom GmbH PDE000092 | DE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 298 ms |
| Edicom Capital SL POP000045 | ES | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 420 ms |
| EDITEL SA PPL000120 | PL | Responding | 97.52 % | 99.65 % | 99.92 % | 99.97 % | 588 ms |
| eFaktura s. r. o. PSK001097 | SK | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 575 ms |
| eVision MessageXchange PAU000349 | AU | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 744 ms |
| Fast Accounting Co., Ltd. PJP000449 | JP | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 682 ms |
| Horus Software PBE000593 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 493 ms |
| InExchange Factorum AB PSE000086 | SE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 323 ms |
| LE VILLAGE CONNECTE PFR001199 | FR | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 296 ms |
| Logiq AS PNO000020 | NO | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 340 ms |
| Moneybird Holding B.V. PNL000072 | NL | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 526 ms |
| NTT DATA Business Solutions PDE000400 | DE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 629 ms |
| Octopus NV PBE000068 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 538 ms |
| Odoo SA PBE000461 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 350 ms |
| Oversea-Chinese Banking Corporation (OCBC) PSG000372 | SG | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 431 ms |
| Qonto POP000727 | FR | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 279 ms |
| Serensia POP000729 | FR | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 257 ms |
| SESAMi (Singapore) Pte Ltd PSG000251 | SG | Responding | 100.00 % | 98.87 % | 99.74 % | 99.91 % | 895 ms |
| SME Norway PNO000931 | NO | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 519 ms |
| Sovos Saphety POP000249 | PT | Responding | 100.00 % | 98.81 % | 99.72 % | 99.91 % | 495 ms |
| Storecove (Datajust B.V.) PNL000151 | NL | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 357 ms |
| SUPER G POP000771 | FR | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 251 ms |
| Teamleader NV PBE000718 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 465 ms |
| Tickstar PSE000018 | SE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 299 ms |
| TKC Corporation PJP000507 | JP | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 730 ms |
| TNGSTN Expert System AB PSE000024 | SE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 251 ms |
| Tradeshift POP000178 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 335 ms |
| Visma Software International AS PNO000063 | NO | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 370 ms |
| Wolters Kluwer Belgium NV PBE000067 | BE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 321 ms |
| Provider | Country | Now | 24 h | 7 d | 30 d | 90 d | Avg. response (24 h) |
|---|---|---|---|---|---|---|---|
| Qvalia AB PSE000094 | SE | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 283 ms |
| B2Brouter Global SL POP000016 | ES | Responding | 100.00 % | 100.00 % | 100.00 % | 100.00 % | 434 ms |
Last updated October 5, 2026 18:31. Providers are listed alphabetically after Qvalia.
FAQ
How can I compare services between Peppol Access Points?
Uptime shows whether an endpoint is reachable. When choosing a provider, document and country coverage, integration options, certifications, delivery models and pricing also matter. Our Peppol provider comparison sets out these points across providers, based on each vendor’s own public sources.
Is this an official Peppol measurement?
No. OpenPeppol does not publish Access Point availability. These are Qvalia’s own measurements, using public endpoints and the method described below.
Does “Not responding” mean a provider is down?
Not necessarily. It means our check did not get a valid answer from the endpoint we monitor. The cause can be on the provider’s side, on the network path to our monitoring location, or an endpoint that has moved. See “How to read the results” below.
Does a high percentage mean a provider delivers invoices reliably?
Not on its own. The check shows that the endpoint answers. Message processing, validation and delivery are not measured.
How was the list of providers chosen?
From participants in the Peppol Directory and the AS4 endpoints their SMPs publish, sampled across 37 countries in September 2026. The list is not complete.
Is an Access Point missing from the monitor?
Contact us with the provider name and country. If available, include its Peppol AP ID and public AS4 endpoint. We will verify the details and add the Access Point when it meets the criteria described in How we measure. New providers are added as monitoring capacity allows.
Work with Qvalia
Qvalia operates a certified Peppol Access Point (PSE000094) and its own SMP, with information security and business continuity management systems certified to ISO/IEC 27001 and ISO 22301.
- Already a Peppol Service Provider? Keep your Peppol identity and let Qvalia operate the infrastructure behind it.
- Adding e-invoicing to your product? Send and receive through Qvalia’s Access Point with one API.
- Looking for a Peppol Access Point provider for your business?
How we measure
- We look up the AS4 endpoint each Access Point has published in its Service Metadata Publisher (SMP), using a participant registered with that provider in the Peppol Directory.
- UptimeRobot sends an HTTPS GET request to that endpoint every five minutes, with a 30-second timeout. Every provider is checked with the same interval, timeout and thresholds.
- An endpoint is counted as responding when it returns any HTTP status below 500. AS4 endpoints only accept signed POST messages, so a GET normally returns 200, 404 or 405. Those all show that the server is reachable.
- It is counted as not responding on a timeout, a connection or TLS failure, or a status of 500 or higher.
- Percentages show the share of checks in each period where the endpoint responded. Measurement for a provider starts on the date its monitor was created.
- Public APIs are measured the same way, against the base URL each provider documents for its API.
How to read the results
- Responding: the endpoint answered our most recent check.
- Not responding: the endpoint did not answer our most recent check. This is a measurement result, not a statement that the provider’s service was unavailable to its customers. A result of not responding can have causes unrelated to the provider’s service:
- The provider has moved its endpoint or renewed its Peppol certificate, and our monitor still checks the old address.
- A network issue between our monitoring location and the provider.
- A disruption in our own monitoring.
- No data: measurement has not started, or is paused while we verify that we are checking the right endpoint.
How we keep the results accurate
- Endpoints are re-checked against each provider’s SMP registration every quarter, and whenever an endpoint has not responded for more than 24 hours.
- If an endpoint has moved, we update the monitor to the address the provider now publishes.
- If we cannot confirm the cause of an extended outage, we pause measurement for that provider and show no data until it is resolved.
- Measurement logs are kept so that every figure on this page can be traced.
What the figures do not show
- Whether a provider accepts, validates or delivers Peppol messages. A responding endpoint can still reject messages.
- Contractual SLAs or the provider’s own availability reporting.
- Planned maintenance. Maintenance windows are counted like any other outage, for every provider, including Qvalia.
- Availability from every region. Checks currently run from UptimeRobot’s North America location.
- Latency as experienced by users in Europe. Response times are measured from North America and include the network distance from there. They are comparable between providers, not to the delivery time of a Peppol message.
- Providers with several endpoints are represented by the endpoint published for the sampled participant.
Missing an AP?
If you operate one of the listed endpoints and believe a figure or endpoint is wrong, or want your endpoint removed, contact us.