Uptime history
| Month | API | Port 25 | Port 465 | Port 587 | Dashboard | Link tracking |
|---|---|---|---|---|---|---|
| November 2026Nov 2026so far | 100 % | 100 % | 100 % | 100 % | 100 % | 100 % |
| October 2026Oct 2026 | 99.39 % | 99.98 % | 99.4 % | 99.4 % | 99.48 % | No measurement |
How a percentage is counted
- Every minute, a probe outside Sendora's network checks the API, SMTP for receiving on port 25 and for sending on ports 465 and 587, the dashboard, and link tracking.
- A check is down from the first of two or more failed minutes in a row until it passes again. A single failed minute does not count.
- A minute in which the probe reached neither of two services outside Sendora's network is not counted, since the fault lay with the probe.
- Days and months are in Stockholm time. A percentage is rounded down, so any downtime shows below 100 %.
Download the results
Each closed month's results, one line of JSON a minute, compressed with gzip.
What a line holds
minute- The minute measured, in UTC.
probe- Which probe measured it.
checks- For
api,smtp25,smtp465,smtp587,dashboardandtrack: theoutcome, the time taken inms, the HTTP status or SMTP replycodethat failed the check, if any, and for SMTP the days left on the certificate,certDays. A line from before the probe checked port 25 has nosmtp25, and port 25 was not measured in its minute. A line from before the probe checked link tracking has notrack, and link tracking was not measured in its minute. reference- The outcomes of the two services outside Sendora's network. A minute in which neither is
okwas not measured.
An outcome is ok, or why the check failed: timeout, dns, refused, reset, certificate, tls, status, body, greeting, ehlo, starttls, quit or error.