Status
System status.
Current operational state of the Rewalz platform.
All systems operational
| Component | Status | Details |
|---|---|---|
| Database | Operational | 375 ms |
| E-mail delivery | Operational | 25 ms |
Last checked at 9/15/26, 11:42:46 PM
This page probes live on every request. It is not cached.
What is measured here
- Database
- Whether the database answers and how fast. It carries everything you see in Rewalz. If it does not answer, no list opens.
- E-mail delivery
- Whether the outgoing mail queue is being worked off. Invitations, notifications and candidate correspondence would be affected. Your data never is.
- Operating mode
- Which mode this environment runs in. If this says anything other than live operation, you are looking at a demonstration with invented data.
What the colours mean
- Operational
- Everything answers within the expected time. If something is still stuck on your side, it is not stuck here.
- Degraded
- It works, but slower than it should. Pages build sluggishly, saving takes a moment. Nothing is lost.
- Down
- This part is not answering. We know before you write, and we are on it.
All green and something still does not work for you?
Then it is somewhere this page does not measure. Write to us with the page address and roughly the time, that saves the first round of questions.
Report a problemIncidents
Every disruption that hit someone outside the company, with what caused it and what prevents it from happening again. Including the ones that hit a single person.
- Resolved
The activation link led to a page that did not exist
- Anyone approved from the waitlist could not set their password and could not get in. The link in the confirmation mail ended on an error page. Every newly approved account was affected.
- After redeeming the token the application redirected to an address that has never existed in this project. On top of that the account stayed in the invited state, and the data layer deliberately grants no session to such an account.
- A check now holds every redirect target and every link on the sign-in path against a page that actually exists. It runs on every change. On top of that there is now a forgot-password flow, so a spent link no longer locks anybody out.
- Resolved
Approving a waitlist application broke off halfway
- The company was created, the account was not. What remained was a tenant with no way in and an application marked as approved. A second attempt was blocked, because a decision is final.
- The component that creates the account on the authentication side had never been wired up. The comment in its place claimed the opposite.
- A composition check now requires every declared component to be genuinely bound. The path from approval to delivered mail was then walked once from end to end.
Ready to see it yourself?
Sign up and we will write as soon as a place is free.