about peppolstatus
Public measurement for public infrastructure.
PeppolStatus independently monitors the Peppol e‑invoicing network — access points, SMPs, the SML registry, certificate rotations, and participant changes — and publishes what it sees.
Why this exists
An outside view keeps everyone honest
Peppol is becoming mandated infrastructure for e‑invoicing across Europe. Yet there has been no independent, public measurement of it.
When a delivery fails, every party debugs their own stack first. Network-level incidents get discovered through support tickets, one confused sender at a time. An always-on outside view shortens that loop: it tells you whether the problem is yours or the network's before you spend an afternoon looking in the wrong place.
How we measure
Continuous, independent, timestamped
An auto-discovered fleet covers every reachable access point and SMP host — currently 1,284 endpoints and 9M+ participants. Continuous sweeps run from multiple European vantage points, around the clock.
An outage is only called when independent probes agree. This quorum means a single probe's bad network path never becomes a false alarm. Each check is timed layer by layer, so a slow TLS handshake reads differently from a dead TCP socket:
- DNS
- TCP
- TLS
- HTTP
Change detection tracks certificate rotations and participants joining, leaving, and migrating between providers. Every figure carries a real timestamp, and gaps in the data are shown as gaps — never smoothed over.
Independence, disclosed
Who builds this, and the interest behind it
PeppolStatus is not run, endorsed, or funded by OpenPeppol or any Peppol authority.
It is built by the engineers at e‑invoice.be, who operate a Peppol access point of their own and believe infrastructure this critical deserves public measurement.
That creates an obvious question: does the operator go easy on its own endpoints? It does not. e‑invoice.be's own access point is monitored by the same probes, on the same schedule, with no special treatment. We disclose the interest here so you can weigh it against what you see.
Principles
What we hold to
Free and private
The public dashboard is free. No account, no tracking.
Color means status
Status color is never decorative. Green, amber, and red mean up, degraded, and down — and nothing else.
Honest data over impressive data
Real timestamps, no invented precision. When something is not built yet, "coming soon" says coming soon.
Fast and light
The site stays quick because it gets checked mid-incident, often from a phone, often under load.
Who it's for
The people who depend on the rails
Ops teams
Access-point and SMP operators deciding, mid-incident, "is it us or the network?"
Integrators & ERP vendors
Confirming the network is up before blaming their own code.
Go-to-market teams
Watching who joins, who leaves, and who migrates between providers.
Consultants & compliance
Teams who need the rails they recommend to be observable.
Contact
Get in touch, or go to the data
Questions, corrections, or a host we should be watching? Email hello@peppolstatus.com.