Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Flocabulary

    6 Flocabulary incidents · ottobre 2021 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

    AWS Outage Impacting Services

    Inizio 20 ottobre 2025 alle ore 15:01 UTC · 6h 12m

    OutageIncidente maggiore
    Componenti interessati
    Flocabulary
    1. 20 ottobre 2025 alle ore 15:01 UTCmonitoring

      We are currently experiencing a service disruption due to an ongoing AWS outage impacting Flocabulary systems. Our team is actively monitoring the situation and implementing mitigations to restore service as soon as possible. Thank you for your patience.

    2. 20 ottobre 2025 alle ore 17:33 UTCmonitoring

      Service is partially restored. The team continues to monitor the situation.

    3. 20 ottobre 2025 alle ore 18:26 UTCmonitoring

      We are continuing to monitor signs of recovery in our host infrastructure.

    4. 20 ottobre 2025 alle ore 19:33 UTCmonitoring

      Service has been restored and Flocabulary is operational. We continue to monitor system performance closely to ensure stability.

    5. 20 ottobre 2025 alle ore 21:14 UTCresolved

      Service has been fully restored following the earlier AWS outage. All Flocabulary systems are now operational and stable. We will continue to monitor to ensure sustained performance. Thank you for your patience and understanding during this disruption.

    Issues while completing Vocab Games

    Inizio 19 dicembre 2024 alle ore 14:26 UTC · 1d 23h

    IssuesIncidente minore
    Componenti interessati
    Flocabulary
    1. 19 dicembre 2024 alle ore 15:05 UTCidentified

      Users may experience issues while completing Vocab Games. We have identified the issue and are working to remediate it.

    2. 19 dicembre 2024 alle ore 16:13 UTCidentified

      We are continuing to work on remediating the issue. In the meantime, new attempts at Vocab Games won't be able to be completed.

    3. 19 dicembre 2024 alle ore 17:54 UTCidentified

      We continue to actively work on remediating the issue. In the meantime, new attempts at Vocab Games won't be able to be completed. We apologize for the inconvenience during this time period as we work to fully restore Vocab Game functionality.

    4. 20 dicembre 2024 alle ore 14:15 UTCidentified

      We continue to actively work on remediating the issue. In the meantime, new attempts at Vocab Games won't be able to be completed, however, other assigned activities remain unaffected. We apologize for the inconvenience during this time period as we work to fully restore Vocab Game functionality.

    5. 21 dicembre 2024 alle ore 14:13 UTCresolved

      Issues with completing Vocab Games have been resolved. We apologize for the inconvenience during this time period and we will continue to monitor.

    Issues with accessing Flocabulary.com application

    Inizio 4 aprile 2024 alle ore 19:18 UTC · 1h 32m

    OutageIncidente maggiore
    Componenti interessati
    Flocabulary
    1. 4 aprile 2024 alle ore 19:18 UTCinvestigating

      We are currently investigating an issue with users being able to reach Flocabulary.com

    2. 4 aprile 2024 alle ore 19:24 UTCidentified

      The issue has been identified and the team is currently working to resolve

    3. 4 aprile 2024 alle ore 20:39 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 4 aprile 2024 alle ore 20:50 UTCresolved

      This incident has been resolved

    Issue Logging In

    Inizio 17 novembre 2022 alle ore 01:23 UTC · 2h 32m

    IssuesIncidente minore
    Componenti interessati
    Flocabulary
    1. 17 novembre 2022 alle ore 01:23 UTCinvestigating

      We are currently experiencing an issue that is preventing certain users from logging into Flocabulary. We are working to resolve this issue as soon as possible.

    2. 17 novembre 2022 alle ore 01:56 UTCidentified

      The issue has been identified and a fix is being implemented. We are working to restore normal operation as quickly as possible.

    3. 17 novembre 2022 alle ore 03:40 UTCidentified

      We have restored the login functionality for users accessing Flocabulary with both SSO and username/passwords. We are still working to restore login for our Clever users

    4. 17 novembre 2022 alle ore 03:55 UTCresolved

      Login via SSO, Clever, and username/password has been fully restored.

    Flocabulary Outage

    Inizio 11 aprile 2022 alle ore 18:03 UTC · 37m

    Pending
    Componenti interessati
    Flocabulary
    1. 11 aprile 2022 alle ore 18:03 UTCinvestigating

      Flocabulary is currently experiencing an interruption in service, we are investigating.

    2. 11 aprile 2022 alle ore 18:16 UTCidentified

      We have located the source of the issue and are working on full recovery on the service. In the intermediate time, access to and performance of Flocabulary may vary.

    3. 11 aprile 2022 alle ore 18:22 UTCmonitoring

      The underlying issue have been remediated and Flocabulary has returned to normal functioning. We are monitoring closely to ensure everything remains working as expected.

    4. 11 aprile 2022 alle ore 18:23 UTCmonitoring

      We are continuing to monitor for any further issues.

    5. 11 aprile 2022 alle ore 18:40 UTCresolved

      This incident is resolved. We've remediated the issue and will continue to monitor closely.

    Users are unable to watch Flocabulary videos

    Inizio 22 ottobre 2021 alle ore 15:02 UTC · 36m

    OutageIncidente maggiore
    Componenti interessati
    Flocabulary
    1. 22 ottobre 2021 alle ore 15:02 UTCidentified

      The issue has been identified and a fix is being implemented.

    2. 22 ottobre 2021 alle ore 15:03 UTCidentified

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

    3. 22 ottobre 2021 alle ore 15:08 UTCidentified

      Both authenticated and unauthenticated users are experiencing issues watching Flocabulary videos. We are currently working on a fix to this issue.

    4. 22 ottobre 2021 alle ore 15:39 UTCresolved

      We have deployed a fix and this issue is now resolved. We will continue to monitor