Status
Is Ottom working right now?
Checked 2026-10-19 15:40 UTC, when you loaded this page. This is a live check, not a cached summary.
Services
| Service | State | Answered in | What it affects |
|---|---|---|---|
| Database | PASS | 75 ms | Scan history, findings and your report. |
| Scan queue | PASS | 73 ms | Where a scan waits for a runner. If this is down, new scans do not start. |
| Evidence storage | PASS | 262 ms | Screenshots and traces from the buy attempt. |
| Email record | PASS | 7 ms | Our record of what we have emailed you. Email still sends if this is down. |
What we can and cannot tell you
No incidents have been recorded here yet. Read that as exactly what it says: nothing has been written to this log. It is not a measurement, and it is not a record of uptime.
Ottom is young, and this page is new. We would rather show you an empty log and say so than publish a number we cannot stand behind.
There is no uptime percentage on this page. A figure like “99.9%” is a claim about every minute in a window. We can observe two things: whether our dependencies answer when you load this page, and which incidents a person wrote down. Neither of those adds up to a measurement of availability, so publishing one would mean inventing it.
An external monitor checks Ottom from outside the cluster, on the reasoning that on-cluster monitoring dies with the cluster. When it has enough history to support a real number, that number will appear here, and it will say which window it covers and what measured it.
If something is wrong and this page says it is not
Tell us: [email protected]. That opens a ticket a person reads. The checks above prove our own services answered. They cannot prove your scan behaved, and if those two disagree we want to know before you do.