We are conducting our monthly maintenance activity during the aforementioned time frame. Normally the maintenance will not lead to a downtime of the system, but the system might be briefly unavailable during this period.
We are monitoring our system after the maintenance closely to assure that it’s operating normally.
If you have any questions or concerns, please get in touch with us using https://support.idnow.de
Sincerely Yours,
IDnow DevOps Team
Posted on
Oct 9, 08:13 CEST
Resolved -
The Network connectivity has been successfully restored. No other issues have been found during our monitoring phase.
Best Regards
Oct 14, 07:55 CEST
Update -
Our datacenter provider informed us, that the current issue has been resolved. We were also informed, that another short network interruption will occur.
Oct 14, 02:24 CEST
Monitoring -
The network connectivity issues have been resolved. The system is available again. We are monitoring the system closely right now and are processing our post-incident checklist.
Incident start: 2019-10-14 00:16 UTC+2 Incident end: 2019-10-14 01:25 UTC+2
Oct 14, 01:59 CEST
Identified -
We are in contact with our datacenter provider to analyze the network connectivity issues.
Oct 14, 00:54 CEST
Update -
We identified network connectivity issues. We are investigating the root cause.
Oct 14, 00:38 CEST
Investigating -
We are experiencing a service unavailability of our services. We are investigating.
Incident start: 2019-10-14 00:15 UTC+2
Oct 14, 00:26 CEST
Completed -
The scheduled maintenance has been completed.
Oct 10, 08:01 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 10, 07:30 CEST
Scheduled -
We will deploy a new release during the mentioned timeframe.
There can be short period of time where our service may not be available.
Oct 9, 10:56 CEST
Resolved -
We have been monitoring the system extensively and the applied measures are successful. The root cause analysis is ongoing.
During the incident duration, the system was 3 times not fully available for approx. 10-15 minutes each time.
Incident start: 2019-10-09 11:35 UTC+2 Incident end: 2019-10-09 12:59 UTC+2
Oct 9, 16:06 CEST
Monitoring -
We applied additional corrective measures and are monitoring the system closely right now. The system has been working properly for the last 50 minutes.
Oct 9, 13:49 CEST
Identified -
The incident is being re-opened as we are experiencing again a service degradation. We are continuing our investigations.
Oct 9, 12:55 CEST
Monitoring -
We applied corrective measures and the system is available again. We are starting with the root cause analysis of this incident.
Incident start: 2019-10-09 11:35 UTC+2 Incident end: 2019-10-09 11:45 UTC+2
Oct 9, 11:49 CEST
Investigating -
We're experiencing an performance degradation and are currently looking into the issue. We will provide regular updates on the issue.
Incident start: 2019-10-09 11:35 UTC+2
Oct 9, 11:40 CEST
Resolved -
The fix has been deployed at 18:00 and esigning are now working correctly again also for our Swiss customers.
Impact: eSignings in our Swiss data center could not be completed on Android devices
Oct 3, 20:23 CEST
Identified -
We have identified an issue in our Android app. We are currently preparing the fix for the app and will deploy it as soon as possible.
Oct 3, 15:57 CEST
Investigating -
Service Impact: We are investigating an issue that sometimes esignings can not be finished using Android devices. We are already in contact with our Swiss service partner for esigning for further analysis.
NOTE: This does not affect our German services or customer using iOS or web in the Swiss data center.
Oct 3, 13:09 CEST
Resolved -
After applying the corrective measures on the DB cluster, the system is operating within normal thresholds. We are closing this incident.
Impact: during the incident time, we experienced a degraded performance situation where not all requests could be served within the expected threshold or not be served at all.
We are still analyzing the root cause and will update once the analysis finished.
Incident start: 2019-10-01 15:44 UTC+2 Incident end: 2019-10-01 16:31 UTC+2
Oct 1, 18:36 CEST
Monitoring -
The corrective measures which have been applied to the DB cluster are successful. We are starting with the root cause analysis to provide more details.
Incident start: 2019-10-01 15:44 UTC+2 Incident end: 2019-10-01 16:31 UTC+2
Oct 1, 17:05 CEST
Identified -
We identified the root cause in within the DB cluster and started to apply corrective measures.
Oct 1, 16:43 CEST
Investigating -
We are experiencing right now a performance degradation which we are analyzing.
Oct 1, 16:14 CEST
Completed -
The new release deployment has been successfully executed. We successfully verified all post-update-actions and monitored the system closely. We are closing this maintenance action now.
Oct 1, 11:28 CEST
Update -
We are continuing to verify the maintenance items.
Oct 1, 08:11 CEST
Verifying -
We are verifying the new release deployment.
Oct 1, 08:09 CEST
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 1, 07:15 CEST
Scheduled -
We will deploy a new release on 2019-10-01 starting 07:15 UTC+2 until 08:00 UTC+2. During this time frame there will be short periods of time where the system is not available.
Sep 26, 21:28 CEST