yasoon had 21 outages in the last 2 years totaling 1092h 26m of downtime — averaging 0.9 incidents per month.
There were 21 yasoon outages since June 17, 2024 totaling 1092h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.
For a few hours today, posting Microsoft Teams channel messages from the Jira UI or via an Automation rule resulted in timeouts or errors. The outage seems to be resolved now, but we are monitoring.
We have identified an incident where a subset of users will see error messages when trying to login with their Microsoft account. Upon investigation we discovered that Microsoft seems to be rolling out a set of changed browser headers which are causing issues. We are working on a fix - in the meantime, re-trying to login for a few times seems to solve the issue for most users.
Microsoft seems to have rolled back the change, we'll be monitoring and working on an implementation that works around this new header, should it roll out eventually.
We are currently investigating an incident where the Smart Connect for Jira app is not accessible in Microsoft Teams. From the first look of it, it seems that this is a Microsoft Teams issue, as the app continues to work on mobile. We have raised the issue with Microsoft. https://github.com/OfficeDev/microsoft-teams-library-js/issues/2982
We have identified an issue with the Microsoft Teams platform that affects apps on a certain feature/schema version. We are trying to fast-track an app update to a previous version which is apparently not affected by this bug. We are also trying to escalate the bug within Microsoft.
As far as we can tell, a fix on the Microsoft side was successful and the app can be used in Microsoft Teams again. We'll be monitoring in case the issue re-appears. Apologies for the interruption.
Yesterday we experienced a full service outage from approximately 8:30 PM CET until 22:45 PM CET, due to a spike in database usage in our main database. We'll do a full investigation and post a post-mortem soon.
We are currently seeing a bug affecting the Atlassian Forms API, regarding to the new conditional section logic. Please refrain from updating Forms until the bug is fixed, otherwise the conditions will not be evaluated correctly in our Microsoft Teams portal app.
We are in active contact with Atlassian to get the bug fixed as soon as possible, please refrain from updating your Forms, if possible, until this issue is resolved.
Atlassian is working on a fix for this issue, please let us know in case you are affected, Atlassian has the ability to roll back the change temporarily on a case by case basis.
We got an update from Atlassian engineering and they expect the bug to be fixed in "a weeks time". We'll update the incident accordingly once the fix is available.
A fix has been rolled out by Atlassian for the issue. The new conditional logic for Forms should now work inside the JSM portal inside teams. We apologize for the disruption!
We are in touch with Atlassian to resolve this degradation. Customers can see long running board load times with some board running into timeouts.
This seems to have resolved itself, although we do not have any any acknowledgement from from Atlassian on the issue. We'll continue to investigate.
We are seeing a re-occurrence of the issue that happened a few weeks ago. We are currently seeing an increased amount of errors in the chat functionality, coming from the Microsoft Graph API. We'll provide an update once we have more information.
We are continuing to work with Microsoft on the issue and hope to have an update soon. If you see errors when creating chats, please try to create the chat again. It's also possible that the chat is created in Teams, despite an error being shown in Jira.
We are seeing some improvements to this issue but are closely monitoring this. Still awaiting feedback from Microsoft on the issue.
We are continuing to monitor for any further issues.
This incident has been resolved on the Microsoft side, chats can now created normally again.
We experienced an incident due to an infrastructure change, that resulted in automated chat & email backup actions not executing. We are currently looking into possibilities of re-running the failed actions. Backups have been failing since 2025/12/19 14:00 UTC.
Approval Bot notifications have not been send on Dec 19th between 9 - 16 o'clock.
We have identified an issue where the Outlook add-in currently does not load, due to a Microsoft CDN not being available. Please also track the following issue: https://github.com/OfficeDev/office-js/issues/6249
The Microsoft Azure Frontdoor incident, which was causing our add-in not to function properly, has been resolved.
We are made aware of some of our Microsoft 365 Automation actions failing in Jira Cloud instances. We have identified the issue and rolled back the responsible code & infrastructure change. The change was implemented in preparation to fully support Atlassian Cloud data residency. We are currently monitoring the issue and apologize for the interruption.
This incident has been resolved.
Creating and loading of chats might not work reliably, additional Microsoft entities may be affected aswell. See official status on Microsoft here: https://admin.microsoft.com/Adminportal/Home?#/servicehealth/:/alerts/TM1087772
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
The incident has been resolved
Creating Outlook meetings in all yasoon Products is currently not working. We are currently investigating the issue.
The problem was identified and we performed a rollback.
This incident has been resolved.
We are currently investigating an issue that our apps cannot be installed from the Atlassian Marketplace.
We have identified the issue and a fix will be rolling out shortly.
A fix has been implemented and we are monitoring our error logs. The problem originated from a changed service on Atlassian Cloud side, where a security certificate was returned with a different mime-type since early morning on the 31th of January, causing our security validation to fail.
This incident has been resolved.
We experienced an issue where Jira calendars with sharing permissions were not functioning correctly in the Confluence Calendars app (cloud only) for approximately 13 hours. This incident was due to a faulty dependency in our cloud infrastructure, which prevented the calendars from being loaded correctly. We investigated the root cause and implemented a bug fix.
For about three hours, we had in issue with our webhook processing which did not execute our handlers correctly. In addition to that, our automatic retry process also did not work as expected, so a few Todo sync updates and built-in preset automations were not processed correctly. We are investigating the root cause of this failure in more depth.
We experienced an issue on Friday, the 29th of November, where some of our automated rules were not executing or delayed by a few hours. Due to a code change on our side our production queueing infrastructure experienced a major congestion, where we needed to clear out a few failed executions that were being retried over and over again, blocking all other events from being processed. We will be looking into improving the robustness of this particular queue.
We are currently experiencing a major outage due to overflowing caches. We are trying to restore availability as soon as possible.
A infrastructure fix has been implemented and we are monitoring the results. We will share a postmortem soon.
This incident has been resolved, we have not seen any recurrence of the problem. We'll implement additional measures to prevent this scenario from happening again.
Triggers in our application used for Jira automation fail with the error "Queue not initialized". Root cause has been identified and a fix is currently being deployed
The issue has been resolved, sorry for the inconvenience. We'll implement better monitoring going forward to prevent this concrete error from happening again.
It currently is not possible to use the Outlook calendar in Jira team managed projects. We are looking into it - sorry about the inconvenience!
This incident has been resolved.
Due to an expired secret, some functions of the Teams bot were not working correctly. We are working on a custom alerting solution that will notify us in advance in the future, as Microsoft does not send out any notifications proactively.