История сбоев Askcody

1. 7 сентября 2026 г. в 10:06 UTCidentified

   Комнаты на информационных панелях Info и Дисплеи конференц-залов могут периодически показывать ошибку («ErrorUnauthorized») вместо встреч, а другие функции чтения календарей через локальное соединение Exchange могут периодически влиять, включая сохранение или обновление учетных данных соединения Exchange. Клиенты на Exchange Online (Microsoft 365) соединения не затронуты. Сама информация о встречах не повреждена — встречи, заказы и заказы не потеряны. Следующее обновление появится в ближайшее время.

2. 7 сентября 2026 г. в 10:15 UTCmonitoring

   Было введено исправление, и службы восстанавливаются. Информационные панели, дисплеи конференц-залов и другие функции чтения локальных календарей бирж в регионе ЕС снова подтверждены работой, и показатели ошибок вернулись к норме. Сохранение и обновление учетных данных подключения Exchange также работает снова. Мы продолжим мониторинг, прежде чем это будет решено.

3. 7 сентября 2026 г. в 10:43 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 31 августа 2026 г. в 09:32 UTCidentified

   Пострадавшие пользователи: сервисы AskCody Регион: Европа Мы определили причину частичного отключения в сервисе AskCody и приступили к работе над решением. Пользователи могут столкнуться с этой проблемой, поскольку поставки не отслеживаются и не могут заказать услуги, в том числе проблемы в части Услуг портала управления. Следующее обновление будет представлено как можно скорее

2. 31 августа 2026 г. в 13:03 UTCresolved

   После мониторинга реализованного решения в сервисе AskCody решен вопрос, связанный с частичным отключением, и пострадавшие компоненты в настоящее время работают.

Автоматический перевод официального обновления инцидента.

1. 21 апреля 2026 г. в 10:49 UTCinvestigating

   Affected Users: Workplace Central, Maps, All Bookings Region: Global We are currently experiencing issues with Workplace Central, Maps, All Bookings and are now investigating the impact. Users may experience this issue as locations not loading and slow response times. As a temporary workaround, users can reload the page or open it in a new browser window. The next update will be provided as soon as possible.

2. 21 апреля 2026 г. в 13:10 UTCmonitoring

   We have identified the issue being a faulty DB configuration. A fix has been applied and we are monitoring the platform.

3. 23 апреля 2026 г. в 06:59 UTCresolved

   The incident has been resolved and the affected components are operational again.

1. 14 января 2026 г. в 13:32 UTCidentified

   Affected Users: AskCody Insights Customers Region: Global Since 2 Jan 2026, AskCody insights has not been collecting data for meetings, due to a database misconfiguration. All other data in AskCody is intact and safe otherwise. We are actively working on a fix and all AskCody Insights data will be restored after the fix is applied.

2. 16 января 2026 г. в 13:03 UTCresolved

   Affected Users: AskCody Insights Customers Region: Global We have restored all AskCody Insights missing data and the module is operational again.

1. 23 декабря 2025 г. в 12:02 UTCinvestigating

   We are seeing unstable connections to the Exchange Web Services integration that powers our add-ins and other services dealing with Exchange meetings directly. Currently, it seems to only affect EU customers, but we are investigating the extent and impact as well as the root cause, and will keep you updated.

2. 23 декабря 2025 г. в 20:13 UTCmonitoring

   We have identified a small set of customers affected by this issue. We have hardened our systems to handle the effect of unintentional misconfigurations, but load-based side effects can still occasionally affect other customers. We are monitoring the platform and will provide updates when additional actions are taken and/or the impact has subsided.

3. 29 декабря 2025 г. в 08:56 UTCresolved

   After monitoring the implemented solution, the issue related to the EWS connectivity and the degraded performance has been resolved, and the incident will now be closed.

1. 29 октября 2025 г. в 16:13 UTCinvestigating

   Affected Users: All Region: All customers in all regions We are currently experiencing a major outage on all components of the platform and are now investigating the cause. Users may experience this issue as errors saying the site cannot be reached. The next update will be provided at 8 pm CEST, unless cause is found before then, in which case we will update immediately. Major Outage Definition: A component is unavailable for all users. Affects the up-time calculation 100%.

2. 29 октября 2025 г. в 16:23 UTCidentified

   Affected Users: All Region: All customers in all regions Microsoft Azure appears to be heavily impacted and everything points to this as the cause of the outage: https://azure.status.microsoft/en-us/status. We will follow any development we can while this persist. The next update will be provided at 9 pm CEST, unless cause is found before then, in which case we will update immediately. Major Outage Definition: A component is unavailable for all users. Affects the up-time calculation 100%.

3. 29 октября 2025 г. в 19:18 UTCidentified

   The platform remains unavailable at this time, and we are continuing to monitor closely until full functionality is restored. Microsoft has deployed a fix for the ongoing Azure outage, and they are reporting gradual recovery across their services: https://azure.status.microsoft/en-us/status The next update will be provided at 10 pm CEST, unless the issue is resolved before then.

4. 29 октября 2025 г. в 20:39 UTCmonitoring

   Microsoft has deployed a fix for the ongoing Azure outage and reports continued recovery across their services: https://azure.status.microsoft/en-us/status. Our platform is now operational again, but users may still experience disturbances or degraded performance while Microsoft's services stabilize. We continue to monitor the situation closely. Next update will be provided when more relevant information is available.

5. 30 октября 2025 г. в 07:27 UTCresolved

   Affected Users: All Users - Worldwide After monitoring the implemented solution by Microsoft, the major outage has been resolved. AskCody has been operational ever since the initial solution was deployed by Microsoft. More information can be found on Microsoft's incident history page: https://azure.status.microsoft/en-us/status/history.

1. 16 октября 2025 г. в 10:17 UTCinvestigating

   Affected Users: AskCody Insights Region: Europe We are currently experiencing a major outage in AskCody Insights Reports and are now investigating the impact. The data collections is still running and only the reports are affected. The next update will be provided as soon as possible.

2. 16 октября 2025 г. в 10:48 UTCresolved

   Affected Users: AskCody Insights Region: Europe After monitoring the implemented solution, the major outage in AskCody Insights has been resolved and is now operational once again. The issue was connectivity issue of the AskCody Insights service. All data is intact and unaffected.

1. 8 октября 2025 г. в 07:34 UTCidentified

   Affected Users: AskCody Insights Region: North America AskCody Customers using Insights will experience missing data from 09 Sept 2025 till 01 Oct 2025. We have identified the issue in our data extraction and have fixed it, so new data is available and intact. We are currently working on getting the data for the affected dates as well. Next update will be provided as soon as possible.

2. 9 октября 2025 г. в 06:27 UTCmonitoring

   Affected Users: AskCody Insights Region: North America We have extracted the missing data and reports should show data again. We are monitoring the Insights module to ensure that everything continues to work.

3. 10 октября 2025 г. в 09:10 UTCresolved

   Affected Users: AskCody Insights Region: North America After monitoring and verifying that the Insights module is working as intended, we are closing the incident.

1. 15 сентября 2025 г. в 06:50 UTCidentified

   Affected Users: All users in Central and Maps Region: All Customers We have an outage and have immediately identified the cause of the major outage in AskCody Bookings, Central and Maps. We are working on implementing a solution. Users may experience this issue as errors stating they do not have access to one of these three modules. The next update will be provided at latest 11 am UTC+1. Major Outage Definition: A component is unavailable for all users. Affects the up-time calculation 100%.

2. 15 сентября 2025 г. в 07:34 UTCidentified

   We misinformed in that the Bookings Add-in is fully operational and not impacted. We are still working towards a solution to solve the outage on Central and Maps, where you as a user will experience the outage in the form of denied access.

3. 15 сентября 2025 г. в 08:03 UTCmonitoring

   Affected Users: Central, Maps Region: Europe We have implemented a solution to the major outages in Central and Maps. We are currently monitoring the status.

4. 15 сентября 2025 г. в 09:42 UTCresolved

   After monitoring the implemented solution, the major outage has been resolved and is now operational once again.

1. 13 августа 2025 г. в 13:06 UTCinvestigating

   Affected Users: [Add-in Users, Management Portal Users,.] Region: [Europe] We are currently experiencing a partial outage in the management portal and Outlook Add-ins and are investigating the issue. Users may experience this issue as timeouts and slow response times. As a temporary workaround, users can retry their requests after a few seconds. The next update will be provided as soon as possible.

2. 13 августа 2025 г. в 13:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 августа 2025 г. в 14:58 UTCmonitoring

   Affected Users: [Add-in Users, Management Portal Users] Region: [Europe] We have identified and fixed the issue and we are actively monitoring the platform.

4. 14 августа 2025 г. в 07:22 UTCidentified

   Affected Users: [Add-in Users, Management Portal Users,.] Region: [Europe] We can see that the issue persists and we are working on a solution. You will as a user continue to experience long loading times and timeouts. It will, in most cases help if you refresh the page/add-in. The next update will be provided as soon as we know more.

5. 14 августа 2025 г. в 11:24 UTCidentified

   Affected Users: [Add-in Users, Management Portal Users,.] Region: [Europe] We can see that the issue persists and we are working on a solution. You will as a user continue to experience long loading times and timeouts. It will, in most cases help if you refresh the page/add-in. We have a support case going with Microsoft to try and resolve this and will continue to work on the issue until it has been resolved. The next update will be provided as soon as we know more.

6. 15 августа 2025 г. в 06:39 UTCidentified

   Affected Users: [Add-in Users, Management Portal Users,.] Region: [Europe] We are still trying to solve this. You will as a user continue to experience long loading times and timeouts. It will, in most cases help if you refresh the page/add-in. We are in dialogue with Microsoft and will continue to work on the issue until it has been resolved.

7. 15 августа 2025 г. в 08:32 UTCidentified

   Affected Users: [Add-in Users, Management Portal Users,.] Region: [Europe] We are aware that access to platform disappeared entirely and expect it to be back shortly.

8. 15 августа 2025 г. в 09:13 UTCmonitoring

   Affected Users: [Add-in Users, Management Portal Users,.] Region: [Europe] The platform currently appears to be fully operational again and we are monitoring if this continues to be the case. You should not experience timeouts and loading errors currently.

9. 15 августа 2025 г. в 09:48 UTCinvestigating

   We can see that the issue persists and we are working on a solution. You will as a user continue to experience long loading times and timeouts. It will, in most cases help if you refresh the page/add-in. The next update will be provided as soon as we know more.

10. 15 августа 2025 г. в 12:51 UTCinvestigating

    The issue persists, and we are continuing to investigate possible causes. Users may still experience long loading times and timeouts. In many cases, refreshing the page or add-in can help temporarily. We are working to restore normal performance as soon as possible and will provide the next update once we have more information.

11. 18 августа 2025 г. в 07:06 UTCinvestigating

    We are unfortunately still not able to resolve this issue and while we work towards a solution, we are also trying to help mitigate the situation while we solve it by making the platform available to you without errors. We hope to install a small fix that should help provide access but with slow loading times (no timeouts) soon. Users may still experience long loading times. In many cases, refreshing the page or add-in can help temporarily. We are working to restore normal performance as soon as possible and will provide the next update once we have more information.

12. 18 августа 2025 г. в 13:29 UTCinvestigating

    We are still working to fully resolve this issue. In the meantime, we are taking steps to mitigate the impact and ensure you can continue using the platform without errors. A small fix will soon be deployed to improve access. While this may result in slower loading times, it should prevent timeouts. Please note that users may still experience delays. Refreshing the page or add-in often helps temporarily. We are committed to restoring normal performance as quickly as possible and will share another update as soon as we have more information.

13. 18 августа 2025 г. в 13:58 UTCmonitoring

    We have identified and isolated the issue affecting the platform, and it should now be operating normally. While the platform is accessible normally again, some users may continue to experience slower loading times. In these cases, refreshing the page or add-in will help. We are continuing to monitor performance closely and will provide further updates if needed.

14. 19 августа 2025 г. в 09:13 UTCresolved

    Affected Users: [Add-in Users, Management Portal Users] Region: Europe After monitoring the implemented solution, the issue related to the slowness/timeouts and the degraded performance has been resolved, and the incident will now be closed. The identified faulty endpoint has been isolated and the platform is operational again.

15. 19 августа 2025 г. в 10:40 UTCpostmortem

    # \[EU\] Latency and timeouts from secondary services - Post Mortem ‌ This Postmortem and technical timeline follows the announcement of degraded performance on the AskCody platform, beginning on Wednesday, August 13th. ## Summary On August 13th at 13:12 CEST, parts of the AskCody platform became unresponsive with very long response times and timeout errors. The errors were periodic and were not caused by any changes made by AskCody. This report describes the timeline and remediation steps taken to resolve the issue. ## Incident overview On August 13th, 2025, at 13:15 CEST, our team was alerted to a severe drop in availability on the [app.onaskcody.com](http://app.onaskcody.com/) domain, serving both our management portal, add-ins, and the check-in kiosks to our EU customers. The alert was in response to a steep increase in response times that had manifested a few minutes earlier. ## Investigation and actions taken ### Initial response August 13, at 13:15 CEST: Detected drop in availability and influx in response times. August 13, at 13:15 CEST: Extended team investigation into the cause and effects of the incident. No conclusive evidence. ### Investigation, temporary solutions, and monitoring May 14 - 15: Investigations extended to include Microsoft Azure services as PaaS resources seemed likely to be involved. Working with Microsoft to profile latency through their network and services. ### Critical discovery August 18, 13:00 CEST: Tracking led to the identification of periodically failing calls to a third-party service that had made changes to their ingestion on the 13th. ### Resolution August 18,. 14:00 CEST: The issue was mitigated, and the incident status was set to “monitoring”. ## Root cause analysis The root cause of the incident was a misconfigured request to a third-party service. We had received timely advice to alter the configuration, but the fact that the endpoint still periodically accepted requests made the troubleshooting more complex. ## Preventative and supplementary measures To prevent similar incidents in the future, we have: * Extended alerting systems for availability tests. ## Conclusion Though this incident was not classified as **critical**, we still consider the impact to be serious. We apologize for any inconvenience caused by the service degradation and assure you that our platform is fully operational again. We remain committed to maintaining the highest security standards, following Microsoft best practices, and will continue to take proactive measures to safeguard our services. If you have any questions or need further information, please do not hesitate to contact our support team. Thank you for your understanding and continued trust in AskCody. Sincerely, **AskCody**

1. 1 апреля 2025 г. в 08:57 UTCinvestigating

   Affected Users: Global We are currently experiencing a major outage in the AskCody platform and are now investigating the impact. Users may experience this issue as Service unavailable errors. The next update will be provided as soon as possible

2. 1 апреля 2025 г. в 09:04 UTCinvestigating

   North America is operational again after a small down time. We are continuing to investigate this issue.

3. 1 апреля 2025 г. в 09:29 UTCmonitoring

   Affected Users: EU A temporary disturbance in our database caused the outage. All data is secure, safe and intact. We have implemented a solution to the major outages in all AskCody components and are currently monitoring the status.

4. 1 апреля 2025 г. в 12:49 UTCresolved

   The incident has been resolved.

1. 14 марта 2025 г. в 13:50 UTCinvestigating

   Region: EU Customers We are currently experiencing issues with Cost Centers being unavailable. Users may experience this issue as Cost Centers either being unavailable or appear as "Hidden". The next update will be provided at latest 16:00 CET

2. 14 марта 2025 г. в 13:52 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 14 марта 2025 г. в 13:52 UTCidentified

   We are continuing to work on a fix for this issue.

4. 14 марта 2025 г. в 14:07 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 14 марта 2025 г. в 14:08 UTCresolved

   This incident has been resolved.

1. 4 февраля 2025 г. в 18:25 UTCidentified

   Affected Users: Delegate users Region: All customers We are currently experiencing issues with an error that occurs while booking services in delegate scenarios through the AskCody Services add-in, and we are investigating the cause. Users may experience this issue as being issued an error that states the meeting does not exist, but it may also occur in other formats. It is, however, specific for delegate bookings where you want to add services. As a workaround we recommend reserving a booking to order services without the delegate scenario or to contact the service provider to have them aid with ad-hoc bookings for urgent matters. The next update will be provided as soon as we know more, Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

2. 5 февраля 2025 г. в 05:58 UTCresolved

   Affected Users: Delegate users Region: All customers The issue related to the error stating the meeting does not exist and the degraded performance has been resolved, and this incident will now be closed.

1. 22 января 2025 г. в 08:54 UTCinvestigating

   We are currently investigating an issue causing partial outage in North America. Users might experience slow load times and failures.

2. 22 января 2025 г. в 09:05 UTCinvestigating

   Region: [North America] Customers We are currently experiencing a partial outage in North America and are investigating the issue. Users may experience this issue as slow response times and failures. The next update will be provided at 2 hour intervals or as soon as we have identified the issue.

3. 22 января 2025 г. в 10:50 UTCmonitoring

   Region: [North America] Customers We have implemented a solution for a faulty network configuration. Users might experience slow response times and failures while the fix propagates.

4. 22 января 2025 г. в 14:42 UTCresolved

   Region: [North America] Customers After monitoring the implemented solution the issue related to the partial outage has been resolved, and the affected components are now operational.

1. 17 декабря 2024 г. в 11:36 UTCidentified

   Affected Users: Azure AD synced users Region: Europe We have identified an ongoing issue with some of our Azure AD synchronization's and are investigating how to resolve the issue. For some customer on the European platform, this means that user changes are currently not being synced. As a temporary workaround, admin users can still manually create and add users and hosts, apply memberships and roles, to provide the necessary access while we work to resolve this. Everything will be restored once the sync is resolved, which will also help overwrite the manual added users during this period. The next update will be provided as soon as possible, Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

2. 8 января 2025 г. в 08:17 UTCmonitoring

   Affected Users: Azure AD synced users Region: Europe We have implemented a solution for the issue and are seeing most syncs are working as intended again. We do have a few we are awaiting and will monitor them, to ensure they also come back on track. We will continue to monitor all syncs over the next hours and days to ensure everything stays operational. The next update will be provided as soon as we have more. Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

3. 13 января 2025 г. в 08:37 UTCidentified

   Affected Users: Azure AD synced users Region: Europe We did not find resolution in our implemented fix and will continue to work to resolve this matter. This means the Azure AD sync will not function properly and may not push your changes through. You can still resolve to manuel edits and all will be sorted once the Azure AD integration is up and running again. We apologise for the inconvenience and extra effort it puts on all and will work as fast as we can to resolve the matter. Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

4. 15 января 2025 г. в 14:19 UTCresolved

   Affected Users: Azure AD synced users Region: Europe After monitoring the implemented solution, the issue related to the Azure AD sync and the degraded performance has been resolved, and the incident will now be closed. Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

1. 25 ноября 2024 г. в 10:12 UTCidentified

   Microsoft is experiencing worldwide issues with Exchange online, which can affect the ability to book meetings and see resource availability. AskCody is following the incident updates and we urge our customers to do the same. All AskCody services are up and operational, but can be affected by the Exchange online outage. More info: Only for exchange admins: https://portal.office.com/adminportal/home?#/servicehealth X: https://x.com/MSFT365Status/status/1860973220662280356

2. 25 ноября 2024 г. в 12:11 UTCidentified

   All AskCody systems are still operational, however the issue with Microsoft Exchange is ongoing and the following update was shared by Microsoft: Users may be unable to access Exchange Online using the following impacted connection methods: - Outlook on the web - Outlook desktop client Users may be unable to use the following features within Microsoft Teams: - Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings. - Users are unable to create chat, add users and create or edited meetings. Scope of impact: Impact is specific to users who are served through the affected infrastructure. Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.

3. 25 ноября 2024 г. в 14:38 UTCmonitoring

   A fix by Microsoft has been implemented and should be applied to the affected users. For more info: https://x.com/MSFT365Status/status/1861047970143019048 As before, AskCody is up and operational.

4. 8 января 2025 г. в 08:13 UTCresolved

   This incident has been resolved.

1. 21 октября 2024 г. в 19:31 UTCinvestigating

   Affected Users: All users who access AskCody Central, Maps or the mobile app. We are currently experiencing a partial outage in AskCody Central, Maps and the mobile app. and are investigating the issue. Users may experience this issue as a error "Code 400", when trying to change the selected location. The next update will be provided as soon as we know more, or latest Tuesday 22nd 8 am CEST

2. 21 октября 2024 г. в 19:51 UTCresolved

   This incident has been resolved. We were able to identify the issue to be related to an update released to the AskCody Platform, which we therefore rolled back. All components are again fully operational.

1. 16 сентября 2024 г. в 09:22 UTCinvestigating

   Affected Users: Add-in and AskCody Management Portal users Region: Europe We are currently experiencing a major outage in accessing AskCody add-ins, check-in kiosks and the management portal and are now investigating the impact and cause. Users may experience this issue as being unable to login. The next update will be provided at latest: 2 pm CEST

2. 16 сентября 2024 г. в 11:28 UTCinvestigating

   We are continuing to investigate the issue. From a user perspective, the issue still persists, but we are making progress in identifying the root cause. Next update will latest be at 3.30 PM CEST. Should we see a reliable improvement in stability before 3.30 PM CEST, we will make sure to post it here.

3. 16 сентября 2024 г. в 13:25 UTCmonitoring

   We identified the root cause of the incident, and a fix was implemented immediately. We are currently monitoring the results. For now, all components are once again stabil and fully operational.

4. 17 сентября 2024 г. в 10:00 UTCresolved

   The solution to the incident worked as expected, and is therefore to be considered as resolved.

1. 30 августа 2024 г. в 14:14 UTCidentified

   Affected Users: Add-in Users, Management Portal Users Region: Europe We have identified a degraded performance in accessing add-ins as well as the management portal. It can also appear on check-in kiosks and Displays Users may experience this issue as receiving af 500 internal error message. The next update will be provided as soon as possible Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

2. 30 августа 2024 г. в 14:14 UTCidentified

   We are continuing to work on a fix for this issue.

3. 30 августа 2024 г. в 17:50 UTCmonitoring

   Affected Users: Add-in Users, Management Portal Users Region: Europe The affected areas have been stable and we are currently monitoring the performance. The next update will be provided, should the situation change, at the earliest time possible. Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

4. 3 сентября 2024 г. в 06:55 UTCresolved

   Affected Users: Add-in Users, Management Portal Users Region: Europe The degraded performance has been resolved, and the incident will now be closed. Degraded Performance Definition: The affected component is working but is slow or otherwise impacted in a minor way. Does not affect downtime.

1. 5 августа 2024 г. в 13:16 UTCinvestigating

   Users affected: Customers on the EU Platform, trying to access Workplace Central. We are currently experiencing issues with Workplace Central on the EU Platform, and are now investigating the impact. Refreshing the page can potentially fix it. All other components are operational.

2. 5 августа 2024 г. в 13:53 UTCmonitoring

   Customers on the EU Platform can again successfully access Workplace Central from the Management Portal. We will continue to monitor the situation.

3. 9 августа 2024 г. в 10:14 UTCresolved

   This incident has been resolved.