Flying Sphinx incident

API is struggling.

Major Resolved View vendor source →

Flying Sphinx experienced a major incident on April 26, 2015, lasting 2h 34m. The incident has been resolved; the full update timeline is below.

Started
Apr 26, 2015, 01:34 AM UTC
Resolved
Apr 26, 2015, 04:09 AM UTC
Duration
2h 34m
Detected by Pingoru
Apr 26, 2015, 01:34 AM UTC

Update timeline

  1. investigating Apr 26, 2015, 01:34 AM UTC

    Looking into the cause, seems to be related to the Redis provider.

  2. identified Apr 26, 2015, 01:48 AM UTC

    Just a quick addition: Searching is unaffected by this, but any Sphinx commands (stop, start, index) are not being processed. I've contacted the Redis provider, looking for a fast resolution there, but if there's no movement soon, will look into new infrastructure.

  3. monitoring Apr 26, 2015, 03:50 AM UTC

    Okay, switched Redis providers, we're back to normal. Greatly apologise for the delay (and have raised a ticket with Pingdom to follow up on why their alerts are not currently coming through to my 24/7 phone, which would have led to this being resolved sooner).

  4. resolved Apr 26, 2015, 04:09 AM UTC

    Considering this issue resolved. Redis is purring along, API calls are being processed. If you've spotted any issues that are still occurring, do get in touch.