tag:status.jexo.io,2005:/historyJexo Status - Incident History2024-03-29T05:22:59ZJexotag:status.jexo.io,2005:Incident/200977992024-02-28T18:26:33Z2024-02-28T18:26:33ZAtlassian API not working properly<p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>18:26</var> UTC</small><br><strong>Resolved</strong> - This incident is now resolved.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>17:15</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented by Atlassian and we are monitoring the results.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>14:26</var> UTC</small><br><strong>Identified</strong> - 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.</p>tag:status.jexo.io,2005:Incident/184732702023-09-13T00:05:37Z2023-09-13T00:05:37ZSwanly scheduled downtime<p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>00:05</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>00:03</var> UTC</small><br><strong>Update</strong> - Scheduled maintenance is still in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>12</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>11</var>, <var data-var='time'>20:43</var> UTC</small><br><strong>Scheduled</strong> - On 12/Sep/2023 between 11:00 PM and 12:00 AM UTC, there will be scheduled downtime for approximately 1 hour. We will be using this time to upgrade Swanly with new features.<br />During this maintenance window, Swanly app will be inaccessible.<br />We appreciate your patience and understanding.</p>tag:status.jexo.io,2005:Incident/163239832023-03-07T11:36:03Z2023-03-07T11:36:03ZIssue with loading Foxly app<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>11:36</var> UTC</small><br><strong>Resolved</strong> - After providing fixes we have been monitoring the entire app performance and can confirm now that incident is resolved.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:48</var> UTC</small><br><strong>Update</strong> - 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.</p><p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>18:29</var> UTC</small><br><strong>Monitoring</strong> - We deployed a fix to resolve problems with loading Foxly main page and the app is now operational.<br />We're monitoring the changes and for now the Foxly in issue panel is disabled.</p><p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>13:49</var> UTC</small><br><strong>Investigating</strong> - 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.</p>tag:status.jexo.io,2005:Incident/159420142023-01-31T09:29:01Z2023-01-31T09:29:01ZIssues with loading Foxly Priority poker game<p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>09:29</var> UTC</small><br><strong>Resolved</strong> - The incident has been resolved - Foxly Priority poker is loading as expected.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>12:08</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jan <var data-var='date'>27</var>, <var data-var='time'>04:46</var> UTC</small><br><strong>Identified</strong> - We have identified the source of the issue and are implementing a fix.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>13:39</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>13:35</var> UTC</small><br><strong>Investigating</strong> - 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.</p>tag:status.jexo.io,2005:Incident/158125272023-01-10T23:30:38Z2023-01-10T23:30:38ZUpgrading infrastructure - planned maintenance<p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>23:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>23:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>17:46</var> UTC</small><br><strong>Scheduled</strong> - On 10/01/2023 between 11:00 PM and 11:30 PM UTC, there will be scheduled downtime for approximately 4 mins. We will be using this time to upgrade our infrastructure.<br />During this maintenance window, Octo app and Foxly app will be partially inaccessible.<br />We appreciate your patience and understanding.</p>tag:status.jexo.io,2005:Incident/119826652022-10-13T22:50:20Z2022-10-13T22:50:20ZDNS Issues for Jexo Apps<p><small>Oct <var data-var='date'>13</var>, <var data-var='time'>22:50</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>13</var>, <var data-var='time'>22:49</var> UTC</small><br><strong>Update</strong> - Service fully recovered</p><p><small>Oct <var data-var='date'>13</var>, <var data-var='time'>22:33</var> UTC</small><br><strong>Update</strong> - Service returned to America, pending domain recovery in Europe and Asia</p><p><small>Oct <var data-var='date'>13</var>, <var data-var='time'>22:17</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p>tag:status.jexo.io,2005:Incident/107110972022-07-28T18:33:08Z2022-07-28T18:33:08ZSwanly application now loading<p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>18:33</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>18:32</var> UTC</small><br><strong>Update</strong> - Swanly is now loading without the issues. Thank you for your patience.<br />The issue was caused by AWS data center outage.</p><p><small>Jul <var data-var='date'>28</var>, <var data-var='time'>17:36</var> UTC</small><br><strong>Investigating</strong> - The Swanly app is currently not loading due to the outage on AWS data centers 👉 https://aws-status.info/<br /><br />We're monitoring AWS updates and inform you of any changes to the status. Apologies for any inconvenience.</p>tag:status.jexo.io,2005:Incident/105834632022-07-14T21:15:34Z2022-07-14T21:15:34ZIssues with Loading the Foxly Application<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>21:15</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>21:13</var> UTC</small><br><strong>Update</strong> - 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.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>21:10</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>20:16</var> UTC</small><br><strong>Investigating</strong> - Some customers might experience issues with Loading Foxly application.<br />We're currently investigating issues and deploying a hotfix to renew the normal loading of the app.</p>tag:status.jexo.io,2005:Incident/79301882021-09-06T20:17:29Z2021-09-06T20:17:29ZApps lost permissions causing errors on install and beyond<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>20:17</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>18:55</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>18:54</var> UTC</small><br><strong>Monitoring</strong> - 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</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>17:26</var> UTC</small><br><strong>Identified</strong> - Seems like the Atlassian team found the issue and are currently working on a fix: https://developer.status.atlassian.com/incidents/vl7q4vwdh1gz</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>16:44</var> UTC</small><br><strong>Update</strong> - 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</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>14:22</var> UTC</small><br><strong>Investigating</strong> - This outage is not caused by our apps directly and it is widespread in the Marketplace app ecosystem as other vendors are reporting it. <br /><br />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.<br /><br />This incident primarily affects users that have installed our apps post 8:00AM UTC today on the 6th of September.<br /><br />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.</p>tag:status.jexo.io,2005:Incident/75533602021-07-21T07:32:01Z2021-07-21T07:32:01ZFoxly unresponsive issues<p><small>Jul <var data-var='date'>21</var>, <var data-var='time'>07:32</var> UTC</small><br><strong>Resolved</strong> - We've been monitoring the performance after providing a fix and can now confirm, that the issue is resolved.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>14:59</var> UTC</small><br><strong>Update</strong> - 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.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>08:50</var> UTC</small><br><strong>Update</strong> - The crash was fixed however currently Automation for Jira changes do not reflect in the app. We're working on a fix for it.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>07:14</var> UTC</small><br><strong>Monitoring</strong> - A fix has been deployed and the application is back up and running. We are monitoring.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>05:53</var> UTC</small><br><strong>Identified</strong> - We identified the issue, applied a fix and currently deploying to production</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>05:52</var> UTC</small><br><strong>Investigating</strong> - 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</p>tag:status.jexo.io,2005:Incident/60613992021-01-20T01:00:42Z2021-01-20T01:00:42ZScheduled Server Maintenance<p><small>Jan <var data-var='date'>20</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>20</var>, <var data-var='time'>00:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>18:22</var> UTC</small><br><strong>Update</strong> - We want to make you aware that this Wednesday (20/01/2021) at 12:00am UTC, there will be scheduled downtime for approximately 1 hour. We will be using this time to add more capacity to our infrastructure.<br />During this maintenance window, Swanly app will be partially inaccessible.<br />We appreciate your patience and understanding.</p><p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>18:21</var> UTC</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>18:16</var> UTC</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>18:14</var> UTC</small><br><strong>Scheduled</strong> - We want to make you aware that this Wednesday (20/01/2021) at 12:00am UTC, there will be scheduled downtime for approximately 1 hour. We will be using this time to add more capacity to our infrastructure.<br />During this maintenance window, Swanly app will be partially inaccessible.<br />We appreciate your patience and understanding.</p>tag:status.jexo.io,2005:Incident/28249062019-08-05T22:49:00Z2021-01-14T11:39:51ZThis is an example incident<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>22:49</var> UTC</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>22:39</var> UTC</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>22:45</var> UTC</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>23:15</var> UTC</small><br><strong>Investigating</strong> - 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.</p>