AskCody incident

Exchange online incident

Notice Resolved View vendor source →

AskCody experienced a notice incident on November 25, 2024, lasting 43d 22h. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2024, 10:12 AM UTC
Resolved
Jan 08, 2025, 08:13 AM UTC
Duration
43d 22h
Detected by Pingoru
Nov 25, 2024, 10:12 AM UTC

Update timeline

  1. identified Nov 25, 2024, 10:12 AM UTC

    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. identified Nov 25, 2024, 12:11 PM UTC

    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. monitoring Nov 25, 2024, 02:38 PM UTC

    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. resolved Jan 08, 2025, 08:13 AM UTC

    This incident has been resolved.