Resolved -
The system is performing as expected. Response times remain stable and fast. We will close this incident, but will continue to monitor the situation.
Jan 21, 11:17 CET
Update -
The results so far are positive, with significantly improved response times. We will continue to monitor the system and will share further updates as needed.
Jan 21, 09:40 CET
Monitoring -
The update has been completed and an improvement has been implemented. We will continue to monitor the results and provide a new update tomorrow morning.
Jan 20, 23:54 CET
Update -
Response times have noticeably improved, but they are still not yet optimal. For this reason, an additional update will be performed tonight at 22:00 to further reduce the load on the system. We will monitor the results afterwards.
Jan 20, 16:58 CET
Update -
We are continuing to investigate the issue.
Jan 20, 15:30 CET
Update -
From now on, we will provide an update every hour. The investigation is still ongoing.
Jan 20, 14:30 CET
Update -
The overall performance has improved but is still not optimal. The investigation remains ongoing.
Jan 20, 13:56 CET
Update -
An improvement has been implemented, this had a noticeably positive effect. We will continue monitoring.
Jan 20, 13:07 CET
Update -
A reboot has been performed, and we are monitoring its effects. The performance is still degraded, and the root cause is still under investigation.
Jan 20, 12:30 CET
Update -
We will provide an update every 30 minutes via the status page. The issue related to availability has been identified. The investigation into the performance is still ongoing.
Jan 20, 12:03 CET
Update -
We are continuing to investigate this issue.
Jan 20, 11:32 CET
Update -
The issue is still under investigation.
Jan 20, 10:49 CET
Investigating -
Unfortunately, the previous fix did not resolve the issue. We are continuing our investigation and hope to provide a solution soon.
Jan 20, 09:45 CET
Monitoring -
A fix has just been implemented, and we will continue to monitor the situation closely in the coming period.
Jan 19, 20:24 CET
Update -
We believe we have found the cause of the problem. Tonight at 8:00 PM CET, we will be performing an update that should potentially resolve this issue. The update will have no impact on Nmbrs accessibility. We are closely monitoring the situation and will update you on the outcome.
Jan 19, 16:56 CET
Update -
The root cause is currently being investigated, and we are working on identifying a solution.
Jan 19, 12:31 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 19, 10:11 CET
Investigating -
We have received a notion of slowness in our application. We are investigating the root cause of this matter and will update this incident as soon as possible
Jan 19, 09:55 CET