Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Flying Sphinx

    51 Flying Sphinx incidents · aprile 2015 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

    Robigus Outage

    Inizio 7 settembre 2026 alle ore 21:23 UTC · 25m

    IssuesIncidente minore
    Componenti interessati
    Robigus
    1. 7 settembre 2026 alle ore 21:23 UTCmonitoring

      Il server principale Robigus si è schiantato inaspettatamente, incidendo alla ricerca e all'indicizzazione di alcuni clienti. E 'stato restaurato, e le operazioni sono di nuovo alla normalità. Attualmente tenere d'occhio le cose per garantire la stabilità è tornato.

    2. 7 settembre 2026 alle ore 21:48 UTCresolved

      Tutto è tornato alla normalità, questo incidente è considerato risolto. Chiedo scusa per l'interruzione!

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Unexpected server crash: Mors

    Inizio 13 settembre 2024 alle ore 16:20 UTC · 4h 32m

    OutageIncidente critico
    Componenti interessati
    Mors
    1. 13 settembre 2024 alle ore 16:20 UTCinvestigating

      The Mors server has unexpectedly crashed, working on bringing up a replacement.

    2. 13 settembre 2024 alle ore 16:26 UTCidentified

      A server is now booted, working on restoring Sphinx daemons.

    3. 13 settembre 2024 alle ore 16:39 UTCmonitoring

      Sphinx daemons and all other services are now running as expected. Please get in touch if problems are persisting.

    4. 13 settembre 2024 alle ore 20:52 UTCresolved

      No further issues have cropped up. This incident is resolved.

    API requests are failing due to a third-party issue.

    Inizio 7 novembre 2022 alle ore 00:33 UTC · 1h 57m

    OutageIncidente critico
    Componenti interessati
    API
    1. 7 novembre 2022 alle ore 00:33 UTCidentified

      We're seeing a failure from an essential third-party API which is stopping our own requests from working - actions that involve reindexing or restarting Sphinx daemons aren't being completed. Search requests are not impacted by this change, though. The issue has been raised with the third-party vendor, and we're hoping for a swift resolution.

    2. 7 novembre 2022 alle ore 02:02 UTCmonitoring

      The third-party has implemented a fix, errors on our side have stopped but will continue to monitor the situation.

    3. 7 novembre 2022 alle ore 02:30 UTCresolved

      All functionality has returned to normal. Thanks for your patience, and if you're finding any problems are persisting, please do get in touch.

    Robigus primary server has stopped responding

    Inizio 14 luglio 2021 alle ore 01:46 UTC · 1h 26m

    OutageIncidente maggiore
    Componenti interessati
    Robigus
    1. 14 luglio 2021 alle ore 01:46 UTCidentified

      The primary server for Robigus has stopped responding unexpectedly. Impacted customers have been switched over to the failover server, and should have search queries working again. A new failover will be created shortly.

    2. 14 luglio 2021 alle ore 02:57 UTCmonitoring

      New failover is now running. If any customers are seeing issues persist, please do get in touch.

    3. 14 luglio 2021 alle ore 03:12 UTCresolved

      All systems are back to normal now.

    Instability for Averna, Strenua

    Inizio 4 maggio 2021 alle ore 06:30 UTC · 0m

    Pending
    1. 4 maggio 2021 alle ore 07:01 UTCresolved

      Both Averna and Strenua servers had some instability in their services, but that has been resolved and everything is back to normal. If any customers continue to be affected, please do get in touch.

    Robigus temporarily not responding.

    Inizio 3 marzo 2021 alle ore 03:39 UTC · 9m

    OutageIncidente maggiore
    Componenti interessati
    Robigus
    1. 3 marzo 2021 alle ore 03:39 UTCmonitoring

      The robigus server had stopped responding, but fixes have been applied, things should be working again, but monitoring the situation to confirm.

    2. 3 marzo 2021 alle ore 03:48 UTCresolved

      The incident has been resolved, all services are functioning as expected. If you're seeing any lingering issues, please do get in touch!

    Robigus was temporarily overloaded.

    Inizio 4 settembre 2020 alle ore 21:47 UTC · 1h 9m

    OutageIncidente critico
    Componenti interessati
    Robigus
    1. 4 settembre 2020 alle ore 21:47 UTCmonitoring

      Robigus was temporarily overloaded, but is now responding to search requests and API calls. Further investigation is underway to determine the initial cause of the problem.

    2. 4 settembre 2020 alle ore 22:39 UTCmonitoring

      The primary Robigus server has gotten worse, so the failover has been promoted as the new primary, with all affected customers migrated. If you're still seeing issues, please get in touch. A new failover server is now being prepared.

    3. 4 settembre 2020 alle ore 22:56 UTCresolved

      New failover is standing by, everything should be functioning properly. Please get in touch if that's not the case.

    Unexpected Robigus downtime

    Inizio 25 agosto 2020 alle ore 22:38 UTC · 53m

    OutageIncidente maggiore
    Componenti interessati
    Robigus
    1. 25 agosto 2020 alle ore 22:38 UTCidentified

      The primary server for Robigus-hosted customers has stopped responding unexpectedly, so the failover has now been promoted (and is actively serving search queries). A new failover will be set up.

    2. 25 agosto 2020 alle ore 23:16 UTCmonitoring

      The new failover is in place, the new primary is running as expected.

    3. 25 agosto 2020 alle ore 23:31 UTCresolved

      Everything's back to normal - but if any customers are still coming across issues, please get in touch.

    New Robigus primary is having issues…

    Inizio 2 luglio 2020 alle ore 22:00 UTC · 31m

    OutageIncidente maggiore
    Componenti interessati
    Robigus
    1. 2 luglio 2020 alle ore 22:00 UTCidentified

      The primary that was switched over to yesterday is having some teething issues, so I've shifted affected customers over to the new failover instead while things are fixed up. Everything should already be working again, and I'll get the underlying problem fixed.

    2. 2 luglio 2020 alle ore 22:18 UTCmonitoring

      The old primary is now in a happy state (and thus can be considered the new failover). The new primary is serving queries and processing API requests without any issues. Keeping an eye on things.

    3. 2 luglio 2020 alle ore 22:31 UTCresolved

      No further issues have cropped up, everything's back to working smoothly, so this issue is considered resolved. If anyone's still seeing problems on their side, please do get in touch.

    Robigus primary has failed.

    Inizio 1 luglio 2020 alle ore 19:02 UTC · 35m

    OutageIncidente maggiore
    Componenti interessati
    Robigus
    1. 1 luglio 2020 alle ore 19:02 UTCidentified

      The primary server for Robigus has failed unexpectedly. Impacted customers have now been switched to the failover server, and search requests should be being served again. A new failover is now being prepared.

    2. 1 luglio 2020 alle ore 19:29 UTCmonitoring

      Robigus replacement failover is set up, and search queries and API calls should be operating normally for all customers.

    3. 1 luglio 2020 alle ore 19:37 UTCresolved

      Everything's continuing to work as expected, this issue is considered resolved. Please get in touch if you're finding any problems persist.

    DNS resolution issues

    Inizio 14 aprile 2020 alle ore 09:14 UTC · 2h 0m

    OutageIncidente maggiore
    Componenti interessati
    Lime
    1. 14 aprile 2020 alle ore 09:14 UTCidentified

      Our DNS provider is having issues from their European node that impacts Lime (the server for our eu-west customers). Searching should remain unaffected, but API requests for indexing and other daemon actions are currently failing. We've been in touch with the DNS provider, and expect there'll be a resolution soon.

    2. 14 aprile 2020 alle ore 09:15 UTCidentified

      We are continuing to work on a fix for this issue.

    3. 14 aprile 2020 alle ore 10:42 UTCmonitoring

      Our DNS provider has fixed the issue and API requests are now working again.

    4. 14 aprile 2020 alle ore 11:14 UTCresolved

      There have been no further disruptions, this incident is considered resolved.

    Mors is not responding.

    Inizio 4 novembre 2019 alle ore 13:29 UTC · 24m

    OutageIncidente critico
    Componenti interessati
    Mors
    1. 4 novembre 2019 alle ore 13:29 UTCinvestigating

      The current More instance is not responding, so a replacement server is being fired up to take its place.

    2. 4 novembre 2019 alle ore 13:39 UTCmonitoring

      The new Mors instance is in place and responding to API calls and search queries.

    3. 4 novembre 2019 alle ore 13:53 UTCresolved

      This incident has been resolved, and all systems are operating as expected. If you're finding any problems persisting, do get in touch.

    Robigus Primary Server has stopped responding.

    Inizio 17 settembre 2019 alle ore 22:30 UTC · 3h 4m

    OutageIncidente maggiore
    Componenti interessati
    Robigus
    1. 17 settembre 2019 alle ore 22:30 UTCidentified

      We've switched over to the secondary server, so customers should have queries and API calls working again. The cause of the initial issue is not yet clear.

    2. 18 settembre 2019 alle ore 01:34 UTCresolved

      Robigus has a new secondary server (with the old secondary working smoothly as the new primary). Everything should be responding as expected now - do get in touch if any issues are still cropping up.

    Lime Rebooted

    Inizio 6 giugno 2019 alle ore 00:31 UTC · 4m

    Pending
    Componenti interessati
    Lime
    1. 6 giugno 2019 alle ore 00:31 UTCmonitoring

      Lime unexpectedly restarted (possibly due to a broader issue in eu-west-1), but came back up within a few minutes with all Sphinx daemons. Everything is back to normal.

    2. 6 giugno 2019 alle ore 00:34 UTCresolved

      Lime has returned to being fully operational. If any customers are seeing issues persist, please do get in touch.

    Averna has crashed.

    Inizio 24 gennaio 2019 alle ore 22:05 UTC · 22m

    OutageIncidente critico
    Componenti interessati
    Averna
    1. 24 gennaio 2019 alle ore 22:05 UTCidentified

      Averna has crashed, currently bringing up a replacement server.

    2. 24 gennaio 2019 alle ore 22:12 UTCmonitoring

      Replacement is up and running, with indexing and search requests responding accordingly.

    3. 24 gennaio 2019 alle ore 22:27 UTCresolved

      This issue is now resolved: Averna's returned to operating smoothly. If you're still seeing issues, please get into touch.

    Averna is not responding

    Inizio 21 novembre 2018 alle ore 17:02 UTC · 17m

    OutageIncidente critico
    Componenti interessati
    Averna
    1. 21 novembre 2018 alle ore 17:02 UTCinvestigating

      Working on getting it restored.

    2. 21 novembre 2018 alle ore 17:11 UTCmonitoring

      New instance for averna is now up and running.

    3. 21 novembre 2018 alle ore 17:19 UTCresolved

      Everything's operating as expected again. Please get in touch if you're finding that's not the case for you!

    Sphinx daemons not responding on Robigus

    Inizio 3 ottobre 2018 alle ore 08:49 UTC · 0m

    Pending
    Componenti interessati
    Robigus
    1. 3 ottobre 2018 alle ore 08:49 UTCresolved

      Earlier today, Robigus stopped responding to search requests (connections to Sphinx daemons). The part of the Flying Sphinx infrastructure that failed was the Sphinx proxy on your original server - it stopped responding to any TCP requests (though the logs had no suggestion as to why). Clearly, this is a critical part of everything - if the proxy’s down, you can’t connect to your Sphinx daemon at all (and that’s essential in both searching and regenerating). I usually get downtime alerts (with a dedicated phone + SMS messages which should wake me up if it’s the middle of the night), but this wasn’t triggered by the proxy failing. So, I’ve made the following changes: * If the proxy does not respond to health checks, it’s considered a major server failure, and thus I will get SMS alerts. * Also, if it’s not responding to health checks, Monit will restart the proxy process, so resolution should be sorted out within a minute. This is now all in place, but I’ll continue to think through better ways of handling such situations. I’m very sorry for the downtime!

    Carmenta is down

    Inizio 21 settembre 2018 alle ore 07:52 UTC · 52m

    OutageIncidente critico
    Componenti interessati
    Carmenta
    1. 21 settembre 2018 alle ore 07:52 UTCidentified

      Greatly delayed alert, but Carmenta has unexpectedly restarted itself and crashed halfway through the process. Working on getting a replacement sorted now, expected resolution in 40 minutes.

    2. 21 settembre 2018 alle ore 08:24 UTCmonitoring

      A new server for Carmenta is running, affected customers should find things are working now. Continuing to monitor to confirm that the issue is resolved.

    3. 21 settembre 2018 alle ore 08:45 UTCresolved

      Everything's now back to normal. Will make sure such fixes don't get delayed so badly again! If anyone's still seeing problems persist, please get in touch.

    Wrong SSL Certificate

    Inizio 20 aprile 2018 alle ore 04:41 UTC · 1h 40m

    Pending
    1. 20 aprile 2018 alle ore 04:41 UTCidentified

      As part of some DNS changes, SSL requests for flying-sphinx.com were briefly returning an invalid certificate (lasting about 10 minutes). This has been resolved, but if you're seeing the problem persist, please do get in touch.

    2. 20 aprile 2018 alle ore 04:42 UTCmonitoring

      Marking this issue as resolved given the certificate is now correct again. Will continue to monitor for any affected services.

    3. 20 aprile 2018 alle ore 06:21 UTCresolved

      There was one more glitch from the certificate provider, but things have been smooth since, so marking this as resolved.

    Issues with requesting actions

    Inizio 29 dicembre 2017 alle ore 12:26 UTC · 18m

    Pending
    1. 29 dicembre 2017 alle ore 12:26 UTCidentified

      While general server maintenance was happening, a bug was introduced for API actions. This has been fixed, and behaviour has returned to normal. Search daemons/requests were unaffected.

    2. 29 dicembre 2017 alle ore 12:34 UTCmonitoring

      Maintenance has finished, behaviour remains as expected.

    3. 29 dicembre 2017 alle ore 12:45 UTCresolved

      This issue is now resolved. If you're seeing any persistent problems, please do get in touch.