yasoon Outage History

yasoon degraded · 1 active incident View live status →

There were 7 yasoon outages since February 5, 2026 totaling 935h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.yasoon.com

Notice March 24, 2026

Brief Microsoft Teams Bot API outage

Detected by Pingoru
Mar 24, 2026, 08:08 PM UTC
Resolved
Mar 24, 2026, 06:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 24, 2026, 08:08 PM UTC

    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.

Read the full incident report →

Minor March 4, 2026

Some users are facing issues logging in with their Microsoft account

Detected by Pingoru
Mar 04, 2026, 08:12 PM UTC
Resolved
Mar 06, 2026, 08:38 AM UTC
Duration
1d 12h
Affected: Microsoft 365 for Jira
Timeline · 2 updates
  1. identified Mar 04, 2026, 08:12 PM UTC

    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.

  2. resolved Mar 06, 2026, 08:38 AM UTC

    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.

Read the full incident report →

Major February 16, 2026

Smart Connect for Jira not accessible in Teams

Detected by Pingoru
Feb 16, 2026, 08:57 AM UTC
Resolved
Feb 18, 2026, 08:19 PM UTC
Duration
2d 11h
Affected: Microsoft 365 for Jira
Timeline · 3 updates
  1. investigating Feb 16, 2026, 08:57 AM UTC

    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

  2. identified Feb 17, 2026, 09:34 AM UTC

    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.

  3. resolved Feb 18, 2026, 08:19 PM UTC

    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.

Read the full incident report →

Notice February 10, 2026

Service downtime due to spike in main database

Detected by Pingoru
Feb 10, 2026, 08:00 AM UTC
Resolved
Feb 09, 2026, 07:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 10, 2026, 08:00 AM UTC

    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.

Read the full incident report →

Major February 6, 2026

Bug in Atlassian Forms API causing issues with new conditional sections

Detected by Pingoru
Feb 06, 2026, 08:42 AM UTC
Resolved
Mar 04, 2026, 01:06 PM UTC
Duration
26d 4h
Affected: Microsoft 365 for Jira
Timeline · 5 updates
  1. identified Feb 06, 2026, 08:42 AM UTC

    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.

  2. identified Feb 09, 2026, 08:07 AM UTC

    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.

  3. identified Feb 10, 2026, 08:20 AM UTC

    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.

  4. identified Feb 17, 2026, 09:32 AM UTC

    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.

  5. resolved Mar 04, 2026, 01:06 PM UTC

    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!

Read the full incident report →

Minor February 6, 2026

Degradation in Jira cloud agile (boards) API performance affecting Teams board views

Detected by Pingoru
Feb 06, 2026, 08:38 AM UTC
Resolved
Feb 10, 2026, 08:19 AM UTC
Duration
3d 23h
Affected: Microsoft 365 for JiraAtlassian Developer Jira Cloud APIs
Timeline · 2 updates
  1. monitoring Feb 06, 2026, 08:38 AM UTC

    We are in touch with Atlassian to resolve this degradation. Customers can see long running board load times with some board running into timeouts.

  2. resolved Feb 10, 2026, 08:19 AM UTC

    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.

Read the full incident report →

Major February 5, 2026

Increase amount of errors around Chat functionality

Detected by Pingoru
Feb 05, 2026, 01:02 PM UTC
Resolved
Feb 10, 2026, 08:17 AM UTC
Duration
4d 19h
Affected: Microsoft 365 for Jira
Timeline · 5 updates
  1. identified Feb 05, 2026, 01:02 PM UTC

    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.

  2. identified Feb 06, 2026, 08:43 AM UTC

    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.

  3. monitoring Feb 09, 2026, 08:05 AM UTC

    We are seeing some improvements to this issue but are closely monitoring this. Still awaiting feedback from Microsoft on the issue.

  4. monitoring Feb 09, 2026, 08:05 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 10, 2026, 08:17 AM UTC

    This incident has been resolved on the Microsoft side, chats can now created normally again.

Read the full incident report →

Looking to track yasoon downtime and outages?

Pingoru polls yasoon's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when yasoon reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track yasoon alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring yasoon for free

5 free monitors · No credit card required