Historial de interrupciones de Blocksi Manager Education Everywhere

1. September 1, 2026 at 6:23 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. September 1, 2026 at 6:27 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. September 1, 2026 at 6:28 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. September 1, 2026 at 6:28 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 1, 2026 at 5:59 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. September 1, 2026 at 6:01 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 1, 2026 at 6:05 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. September 1, 2026 at 6:06 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

5. September 1, 2026 at 6:39 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 7:56 AM UTCinvestigating

   Actualmente estamos realizando trabajos para asegurar el sitio web de Blocksi.net contra nuevas vulnerabilidades.

2. July 22, 2026 at 7:58 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 22, 2026 at 7:59 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 3:39 PM UTCidentified

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

2. July 13, 2026 at 6:28 PM UTCresolved

   This incident has been resolved.

3. July 13, 2026 at 6:28 PM UTCpostmortem

   apparently due to a lack of space on the storage - due to backup that were done on the space where the website was hosted that eat all space available. ‌ Restored July 4th website Restored June 27th database ‌ Litespeed cache plug prevented the website to start - had to contact senior support engineer at hosting company to get it solved. they renamed the folder and got it solved

1. February 25, 2022 at 4:47 PM UTCinvestigating

   When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

2. February 25, 2022 at 4:47 PM UTCidentified

   As you continue to work through the incident, update your customers frequently.

3. February 25, 2022 at 4:47 PM UTCmonitoring

   Let your users know once a fix is in place, and keep communication clear and precise.

4. February 25, 2022 at 4:47 PM UTCresolved

   Empathize with those affected and let them know everything is operating as normal.