Few questions were raised on the Slingshot forums, and we have a response for interest.
1)What exactly happened?
We were upgrading the configuration on our caches to resolve a known issue with YouTube. The upgrade contained a bug which resulted in the caching issues experienced by some customers.
2) When did it happen? What are the possible time ranges we need to consider.
We received complaints between 4:00pm – 4:40pm based on customer calls into the Contact Centre. The fault was resolved within a 15 minute window, however the caches were subsequently turned off by our engineers.
3)What was affected? Do you have a list of sites that we should check to ensure we weren't affected?
Cached sites. Any sites which were not secure (HTTPS) were affected.
4)Why it happened?
An error by our vendor caused the fault.
5)What steps have been taken to ensure it doesn't happen again?
Caching is currently off and we are working to provide the facility to disable caching for any individual customers that do not want to be cached. When comparing browsing speeds to some of our competitors, our speeds are twice as fast with caching, so the end user may notice a difference in performance.
Our vendors have flown in engineers to complete an audit of the platform and configuration. We will then be retesting all of the hardware in a lab environment until we are 100% certain that all issues around caching are resolved. We will then reintroduce the caches into a small in-house test group, before we are 100% satisfied that it provides the performance boost that we want to deliver to our customers with ZERO issues.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.