This page will be updated with warnings about scheduled maintenance, and with information during critical outages.
What happened: Today at approximated 12:00 UTC (23 April 2018) (midnight NZST 24th April) Vinsight went offline. This was due to hardware infrastructure at one of our data-centres experiencing a failure, and this caused Vinsight to go offline. Due to the timing of the incident, our initial response was slow. Once we were aware Vinsight was down, we spent time diagnosing the issue. Before we brought Vinsight back online we decided to do a full backup image of the affected service to mitigate further risks, and while this meant it took longer to bring Vinsight online, we felt it was a prudent thing to do. Once the backups were complete we brought Vinsight back online. What we could improve upon: We understand that our customers are global and operate in many time-zones around the world and that at certain times of the year, our customers can be working 24 hours a day. So while we are happy with the amount of time it took to diagnose, backup and re-instate the service, we have identified it took too long to become aware of the issue. We are working to implement systems to improve our first response times for outages that are outside of our normal business hours. We do have a status page that keeps people up to date if Vinsight is offline for either planned or unplanned maintenance. We discovered that many people did not see this because they were not correctly re-directed to the status page during the outage. We have identified and implemented a way so that anyone trying to go to any Vinsight page during an outage will be correctly redirected to the status page. We understand how disruptive any unplanned outage can be, and appreciate your patience and understanding. Regards Simon Lampen CEO
Don't see your issue posted here? Let us know!