9 Jexo incidents · August 2019 — official updates, affected components, duration and resolution details.
Atlassian has identified a problem with Connect Apps API that widely affects Cloud apps. You might experience problems loading Swanly, Foxly, and Octo due to this incident. We are closely monitoring Atlassian's status updates so our apps are back to operational state.
A fix has been implemented by Atlassian and we are monitoring the results.
This incident is now resolved.
Some customers are experiencing issue with loading Foxly app (initial page). Our engineering team is currently investigating it and we will come back with an update shortly.
We deployed a fix to resolve problems with loading Foxly main page and the app is now operational. We're monitoring the changes and for now the Foxly in issue panel is disabled.
We have identified the source of the issue and implemented another fix, Foxly panel in the issue details screen is back to normal operation. We are monitoring the results.
After providing fixes we have been monitoring the entire app performance and can confirm now that incident is resolved.
Some customers are experiencing issues with loading Foxly Priority poker game. Our engineering team is currently investigating it and we will come back with an update shortly.
We are continuing to investigate this issue.
We have identified the source of the issue and are implementing a fix.
A fix has been implemented and we are monitoring the results.
The incident has been resolved - Foxly Priority poker is loading as expected.
The issue has been identified and a fix is being implemented.
Service returned to America, pending domain recovery in Europe and Asia
Service fully recovered
This incident has been resolved.
The Swanly app is currently not loading due to the outage on AWS data centers 👉 https://aws-status.info/ We're monitoring AWS updates and inform you of any changes to the status. Apologies for any inconvenience.
Swanly is now loading without the issues. Thank you for your patience. The issue was caused by AWS data center outage.
This incident has been resolved.
Some customers might experience issues with Loading Foxly application. We're currently investigating issues and deploying a hotfix to renew the normal loading of the app.
We are continuing to investigate this issue.
We released a fix for an issue related to a high amount of webhooks received from Jira by Foxly. The app is now loading and is operational. We're monitoring the performance of the app.
This incident has been resolved.
This outage is not caused by our apps directly and it is widespread in the Marketplace app ecosystem as other vendors are reporting it. It affects Jira and Confluence apps that require ADMIN privileges. Our apps require such privileges to create custom fields when installing the app. These custom fields are needed for the app to properly function. This incident primarily affects users that have installed our apps post 8:00AM UTC today on the 6th of September. We are communicating with the Atlassian Ecosystem Support team and other affected Vendors and we will update the status here as soon as we have news from Atlassian team in charge of this.
Atlassian acknowledged the issue and their team is investigating for the cause. There is now a status page incident on their end: https://developer.status.atlassian.com/incidents/vl7q4vwdh1gz
Seems like the Atlassian team found the issue and are currently working on a fix: https://developer.status.atlassian.com/incidents/vl7q4vwdh1gz
A fix was implemented and the Atlassian team is currently monitoring: https://developer.status.atlassian.com/incidents/vl7q4vwdh1gz?_ga=2.57608490.1868789609.1630793205-1581854486.1625682701
We are continuing to monitor for any further issues.
This incident has been resolved.
Foxly is unresponsive and constantly loading for most users. This was caused by a release deployed yesterday. Due to faulty code the side effect has been gradually building up to the tipping point and resulted in the app starting to crash and not respond today at 6AM BST
We identified the issue, applied a fix and currently deploying to production
A fix has been deployed and the application is back up and running. We are monitoring.
The crash was fixed however currently Automation for Jira changes do not reflect in the app. We're working on a fix for it.
We have deployed a fix and now Automation for Jira changes do reflect in the app. Application is back to normal operation. We will keep on monitoring the performance.
We've been monitoring the performance after providing a fix and can now confirm, that the issue is resolved.
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
As you continue to work through the incident, update your customers frequently.
Let your users know once a fix is in place, and keep communication clear and precise.
Empathize with those affected and let them know everything is operating as normal.