Live access point status · independent

Is Tickstar down?

No. Tickstar looks operational right now. We monitor the 6 Peppol hosts Tickstar publishes — access points, SMPs, or both — from several locations, every few minutes. No crowd-sourced reports, no self-declared uptime.

Current verdict

Operational

Monitored hosts: 6
Hosts down now: 0
30-day uptime: 99.99%
Incidents, 30 days: 1

Over 90 days: 99.77% uptime across 3 recorded incidents · weakest host smp.tickstar.com.

Rebuilt hourly · data as of 20 Sept 2026, 19:30 UTC · GET /v1/providers/public/tickstar

Scope

What this page can and cannot see

The verdict above is an outside-in measurement of the hosts Tickstar publishes to the Peppol network. That is a narrow claim on purpose, so here is both halves of it:

We can see whether each published access point and SMP host answers, how quickly, whether its TLS certificate is valid and when it expires, and whether a failure is agreed on by probes in more than one location.
We cannot see anything inside Tickstar: message queues, a backlog draining after an incident, your own credentials or contract, a document rejected by validation, or a recipient's ERP that accepted a document and then did nothing with it. Those fail while every host reads up.
A Peppol failure is usually partial. Your send crosses your operator, the SML lookup, the recipient's SMP and the recipient's access point. This page covers one of those four for one operator. The network-wide status page covers the fleet.

Context

Who Tickstar is on the network

Tickstar serves 1,079,396 Peppol participants that we can attribute to it, which ranks it #1 in our directory — its largest market is France with 437,356 participants. This page exists because it is one of the 37 largest operators we monitor; we publish one for every provider above 30,000 attributed participants that we hold a live reading for.

FAQ

Is Tickstar down? Common questions

Is Tickstar down right now?

No. Tickstar looks operational right now. We probe the 6 hosts Tickstar publishes on the Peppol network every few minutes from several locations and require agreement between probes before calling anything down. Over the last 30 days those hosts responded 99.99% of the time, across 1 recorded incident. The verdict at the top of this page is rebuilt every hour.

My invoices to Tickstar are failing but this page says operational. Why?

Because we measure reachability, not delivery. Our probes check that Tickstar's Peppol endpoints answer correctly from the outside. They cannot see the operator's internal queues, your credentials or contract status, a document your counterparty's system rejected, or a recipient's ERP that accepted the document and then dropped it. A send that fails while every host reads up is far more often one of those than a network outage — start with the recipient's Peppol ID in the directory lookup.

Does Tickstar publish its own status page?

Some operators do and some do not, and either way an operator's own status page is reported by the operator. This one is not: it is independent, continuous measurement from outside their network, published whether it flatters them or not, and it uses the same probes and the same thresholds as every other operator we monitor. Both readings are useful — theirs knows what they are doing about it, ours knows what the network can see.

PeppolStatus is independent of Tickstar. How we probe, how we reach a verdict, and how we handle our own access point: the about page. Every check is in the free API.