Apr 19, 09:06 CEST
This incident is now resolved. We will publish a full postmortem within 7 days.
Apr 12, 16:24 CEST
We are still monitoring system performance. Metrics indicate that overall performance on all affected products remains stable.
We will keep monitoring and provide another update at 16:00 CEST.
Apr 12, 13:28 CEST
Based on extensive monitoring and system metrics the performance on all affected products is restored. We are fully aware of the impact and we keep the overall status as monitoring until tomorrow morning.
Apr 11, 15:24 CEST
We will continue monitoring and performing verification during the next 3 hours.
Next update 15.00 CEST
Apr 11, 12:05 CEST
We have been monitoring the effects of the fix released and are currently in the verification process.
Next update 12.00 CEST
Apr 11, 09:49 CEST
A fix is released in our production environment we will continue monitoring. Next step will be doing a verification on affected clients.
Apr 10, 16:11 CEST
We have tested a potential fix and are preparing a releasing in our production environment.
Next update 16.00 CEST
Apr 10, 15:14 CEST
We are unable to confirm the incident is solved, although logs and testing suggest that performance is improved. We are currently testing a new update. Rest assured we are focusing all our resources to find a solution as quickly as possible.
Next update 15.00 CEST
Apr 10, 12:13 CEST
We are still monitoring all systems and verifying that efforts made to permanently solve timeout errors that some clients experience in products interacting directly with meeting information, has an effect.
Next Update 12.00 CEST
Apr 10, 10:06 CEST
We have released an update to our production environment that have mitigated the issues. Both our internal testing, testing on test environments and monitoring of the released update suggest that system performance on affected clients is restored. However the status will be kept as monitoring until a complete verification has been made. Following this will be a post mortem further elaborating on this incident. We will keep monitoring for at least 12 hours
Apr 9, 18:54 CEST
We are still running tests on the update, and preparing release of update on our production environment. We will change status to monitoring and post a new update as soon as this is released and running.
Apr 9, 17:54 CEST
We are still running tests on the update
Next update will be 17:30 CEST
Apr 9, 16:35 CEST
We are currently testing an update on our test environment.
Next update will be 16:30 CEST unless we have the update ready for deployment in production
Apr 9, 15:38 CEST
We have identified the root cause of the incident but are having trouble mitigating the effects. We are within the next hour deploying an update and will continue to monitor the impact after this.
Next update 15:30 CEST
Apr 9, 14:32 CEST
We have been monitoring the released fix but we can't confirm it to be a permanent solution to the problem and continue investigation.
Next Update will be 14:30 CEST
Apr 9, 13:31 CEST
We continue monitoring and contacting clients with open support tickets on this incident.
Next Update will be 13:30 CEST
Apr 9, 12:37 CEST
We continue monitoring on the deployed fix and have begun contacting clients with open support tickets on this incident.
Next Update will be 12:30 CEST
Apr 9, 11:32 CEST
A fix is deployed and we are currently monitoring. The impact before the deployment of the fix has been minor but our test suggest that the fix will fully restore performance. During the next hour we continue monitoring and from 11.00 CEST clients with open support tickets will be contacted and the incident will not be marked as resolved before everything is confirmed fully operational.
Next Update will be 11:30 CEST
Apr 9, 10:12 CEST
We have done extensive testing and are currently testing a solutions to the sporadic timeout errors that some clients are experiencing. The status is kept as Investigation but will be changed to monitoring as soon as a fix deployed and verified.
Next update 10.00 CET
Apr 9, 08:43 CEST
We continue investigating and finding solutions to sporadic timeout errors that some clients experience in products that interact directly with meeting information. Even though the impact is not significant on all clients we keep product status on Degraded performance until this is 100% identified or resolved. The AskCody Statuspage will be updated as soon as we have new information regarding this incident
Apr 6, 17:42 CEST
We continue investigation on the issue. Next update 17:30 CET
Apr 6, 16:09 CEST
Next update 16:00
Apr 6, 15:03 CEST
We continue investigation on the issue. ActivityView performance is still degraded but with much lower impact.
Apr 6, 14:38 CEST
A temporary solution for ActivityView is release and we continue investigation of degraded performance. Next update 14:30 CET
Apr 6, 13:30 CEST
We are still investigating the issue, we have a temporary solution for ActivityView that we are rolling out during the next hour. This is not a permanent fix but will result in significantly less errors on the screens affected. Next update will be 13:30
Next update 11:00 CET
Apr 6, 12:15 CEST
We are still investigating the issue, unfortunately we do not have a root cause yet.
Next update will be 12:00 CET
Apr 6, 11:04 CEST
We are still investigating the issue
Next update 11:00 CET
Apr 6, 10:04 CEST
We are still investigating sporadic timeout errors. Our research and logging suggest this is mainly related to ActivityView and not Today+, but until we have this 100% identified, we will keep the status Degraded performance on all products that interact directly with meeting information. Meeting+ and Welcome+ degraded performance status is related to the add-ins, the add-ins is functioning but can experience timeout errors in some cases. Our logging and testing suggest that impact on RoomFinder is very limited but the status will not be changed before it is confirmed fully operational across all clients. Next update will be 10.00 CET.
Apr 6, 09:03 CEST
Since this morning we have been investigating some sporadic issues reported by multiple clients. These issues where related to getting meeting information from Exchange via AskCody Services. We have actively been investigating and monitoring this during the day but are unable to find any possible causes to this issue. Further, all our operational logging and monitoring are not suggesting any degraded performance. We change the status to monitoring based on our investigation and urge affected clients to report any issues to our support. We continue investigation and monitoring, next update will be tomorrow 9:00 CET
Apr 5, 17:52 CEST
We are still investigating Degraded Performance on products showing meeting activities. Next update will be 17.30 CET
Apr 5, 16:41 CEST
We are still investigating Degraded Performance on products showing meeting activities. Next update will be 16.30 CET
Apr 5, 15:27 CEST
We are still investigating Degraded Performance on products showing meeting activities. Next update will be 15.30 CET
Apr 5, 14:35 CEST
We are still investigating the incident and it has been escalated to also include add-ins.
Next update will be 14:30 CET
Apr 5, 13:32 CEST
We are currently investigating Degraded Performance on some ActivityViews. Next update will be 13.30 CET
Apr 5, 12:25 CEST