Is anything broken?
What we watch
Each bar is one day. Green is a day with no failed check; amber means it was up but slow; red means at least one per cent of checks failed. A gap means we were not watching yet.
Erioun
Operational 117 ms 100.00%Erioun API
Operational 65 ms 100.00%Kaeros
Operational 405 ms 100.00%Kaeros API
Operational 38 ms 100.00%Job Opportunities API
Operational 1400 ms 100.00%Job Opportunities API — data
Operational 35 ms 100.00%The machines underneath
Two servers, both ours, both in the European Union. The company site and its support system deliberately do not live on the same machine as the products — one outage should not take down the thing you would use to find out about it.
Application host
DegradedProducts and client workloads
- RegionEU · Poland
- Operated byTZEKOS.EU
- BackupsNightly, encrypted, off-site
- Last health report2 min ago
Studio host
OperationalThis site, its portal and image builds
- RegionEU · Poland
- Operated byTZEKOS.EU
- BackupsNightly, encrypted, off-site
- Last health report5 min ago
Exact processor, memory and disk figures are not published here. They tell an attacker how much headroom there is to exhaust, and they tell a customer nothing they cannot read off the uptime history above.
What happened, and what we did
Written by a person, never generated. Incidents stay here after they are resolved — a status page that deletes its own history is a marketing page.
Nothing to report. There have been no incidents, maintenance windows or announcements since this page went up.
What we promise when it breaks
A response within 24 hours, written into the contract. Deliberately not an uptime percentage — a response is something one person can guarantee, and it is what actually matters at eight in the morning when the booking form is down.