Services
reachable outage no data One segment per hour, last 90 hours
-
WebsiteHTTP
reachable
- Uptime 24h
- 83.33%
- Uptime 7d
- 83.33%
- Uptime 30d
- 83.33%
-
BewerbungsportalHTTP
reachable
- Uptime 24h
- 100%
- Uptime 7d
- 100%
- Uptime 30d
- 100%
-
Bewerbungen-APIHTTP
reachable
- Uptime 24h
- 98.94%
- Uptime 7d
- 98.94%
- Uptime 30d
- 98.94%
-
NotebookLM KlonHTTP
reachable
- Uptime 24h
- 100%
- Uptime 7d
- 100%
- Uptime 30d
- 100%
Incidents
-
Websiteresolved
Sep 17, 19:58 to 20:079 min
How it works
A single Go binary without a framework, measurements are stored in SQLite.
- Checks
- HTTP checks the status code and optionally a keyword in the response body. TCP only checks whether the port accepts a connection. FiveM queries info.json and players.json of the FXServer, only the player count and version are shown.
- Scheduler
- Every target runs in its own goroutine with its own interval. A small random offset (jitter) keeps all checks from starting at the same moment.
- Incidents
- An incident only starts after several failed checks in a row, a single hiccup does not raise an alert. A mail goes out when a service goes down and when it is back.
- Security
- Passwords hashed with argon2id, a CSRF token in every form, checks against internal addresses are blocked (SSRF), plus a strict CSP without inline scripts. Addresses and error messages are never shown publicly.