6 Replies Latest reply on May 3, 2018 5:58 PM by Sarah O'Meara

    2017.1 stopped working today

    gregor.scott

      It started when I (foolishly, perhaps) tried to open a new tab to our Jive instance.

      I first noticed that it wsa not responding when I saw the footer message:

       

      This eventually produced this outcome

       

      That is all we get at the moment.

      (yes - I have a sev-1 private case open, created at 2:05pm AEST)

       

      This is the 3rd full outage of Jive since we migrated, which brings us to a total of 3 outages in our 3 year journey

       

       

      Anyone else having issues with accessing their 2017.1 AWS cloud instance?