Historial de interrupciones de Blueshift

1. July 15, 2026 at 5:24 AM UTCinvestigating

   Estamos viendo cuestiones de capacidad informática tanto en los centros de datos estadounidenses como en la UE. Muchos grupos están funcionando a capacidad limitada, por lo que habrá retrasos y retrasos en el procesamiento.

2. July 15, 2026 at 5:28 AM UTCidentified

   Estamos trabajando con ayuda de las vacas para aumentar las cuotas, esto puede tomar algún tiempo (unas horas).

3. July 15, 2026 at 11:52 AM UTCidentified

   Aún no tenemos plena capacidad. Estamos tratando de resolver esto pronto.

4. July 15, 2026 at 5:56 PM UTCmonitoring

   Estamos empezando a ver la capacidad volver. Los atrasos han crecido muy grandes - tomarán muchas horas para drenar.

5. July 15, 2026 at 9:30 PM UTCresolved

   Este incidente se ha resuelto y el atraso ha vuelto a niveles normales.

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

1. July 13, 2026 at 6:40 PM UTCinvestigating

   Nuestro servicio de validación de correo electrónico no está disponible actualmente debido a un problema en curso. Estamos trabajando activamente para restaurar el servicio lo más rápido posible. Nos disculpamos por la molestia y apreciamos su paciencia.

2. July 13, 2026 at 7:48 PM UTCmonitoring

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

3. July 13, 2026 at 8:24 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 10, 2026 at 7:48 PM UTCinvestigating

   En estos momentos estamos investigando el problema.

2. July 10, 2026 at 8:15 PM UTCmonitoring

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

3. July 10, 2026 at 8:49 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 10, 2026 at 10:14 AM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 10, 2026 at 10:44 AM UTCidentified

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

3. July 10, 2026 at 10:57 AM UTCmonitoring

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

4. July 10, 2026 at 11:37 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 5, 2026 at 9:02 PM UTCinvestigating

   We are currently investigating this issue.

2. June 5, 2026 at 9:13 PM UTCidentified

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

3. June 5, 2026 at 9:26 PM UTCmonitoring

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

4. June 5, 2026 at 10:35 PM UTCresolved

   This incident is resolved now, dashboard is stable now - app.getblueshift.com.

1. May 20, 2026 at 5:39 PM UTCinvestigating

   We are currently investigating this issue.

2. May 20, 2026 at 5:56 PM UTCidentified

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

3. May 20, 2026 at 6:07 PM UTCmonitoring

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

4. May 20, 2026 at 6:42 PM UTCresolved

   This incident has been resolved.

1. April 6, 2026 at 5:58 AM UTCinvestigating

   We are currently investigating this issue.

2. April 6, 2026 at 5:59 AM UTCinvestigating

   The issue we saw 30 mins back is not completely solved - will keep this page open until we resolve it fully.

3. April 6, 2026 at 6:32 AM UTCmonitoring

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

4. April 6, 2026 at 8:45 AM UTCresolved

   This incident has been resolved.

1. April 6, 2026 at 5:24 AM UTCinvestigating

   We are currently investigating this issue.

2. April 6, 2026 at 5:35 AM UTCidentified

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

3. April 6, 2026 at 5:38 AM UTCmonitoring

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

4. April 6, 2026 at 5:47 AM UTCresolved

   This incident has been resolved.

1. March 18, 2026 at 3:10 PM UTCinvestigating

   We are currently investigating this issue.

2. March 18, 2026 at 3:45 PM UTCidentified

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

3. March 18, 2026 at 3:53 PM UTCmonitoring

   We have added a fix and are monitoring the system.

4. March 18, 2026 at 5:50 PM UTCresolved

   This incident has been resolved.

1. March 7, 2026 at 8:39 AM UTCidentified

   We are seeing some issues with a database that backs campaigns. While we work to fix the issue you will see some campaigns failures.

2. March 7, 2026 at 9:52 AM UTCidentified

   This problem needs a temporary pausing of all campaigns. We are doing that now.

3. March 7, 2026 at 10:17 AM UTCidentified

   Expecting campaigns to be paused for another 30 mins

4. March 7, 2026 at 11:20 AM UTCidentified

   Have unpaused campaigns. Monitoring for campaigns to get stable.

5. March 7, 2026 at 11:30 AM UTCmonitoring

   Campaign sends are going out normally. Will keep monitoring this.

6. March 7, 2026 at 12:21 PM UTCresolved

   This incident has been resolved.

1. January 10, 2026 at 9:30 AM UTCinvestigating

   We are currently investigating this issue.

2. January 10, 2026 at 9:40 AM UTCidentified

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

3. January 10, 2026 at 9:42 AM UTCmonitoring

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

4. January 10, 2026 at 10:13 AM UTCresolved

   This incident has been resolved.

1. January 9, 2026 at 7:04 PM UTCinvestigating

   We are currently investigating this issue.

2. January 9, 2026 at 7:18 PM UTCidentified

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

3. January 9, 2026 at 7:18 PM UTCmonitoring

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

4. January 9, 2026 at 7:22 PM UTCresolved

   This incident has been resolved.

1. December 5, 2025 at 9:08 AM UTCinvestigating

   We are currently investigating this issue.

2. December 5, 2025 at 9:10 AM UTCinvestigating

   We are currently seeing errors for following Blueshift sites: https://developer.blueshift.com https://academy.blueshift.com https://blueshift.com

3. December 5, 2025 at 9:16 AM UTCinvestigating

   We do see these Blueshift sites loading now https://developer.blueshift.com https://academy.blueshift.com https://blueshift.com Further updates on the cloudflare outage are available here: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

4. December 5, 2025 at 9:18 AM UTCidentified

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

5. December 5, 2025 at 9:26 AM UTCmonitoring

   All Blueshift pages are working normally now.

6. December 5, 2025 at 12:06 PM UTCresolved

   This incident has been resolved.

1. November 25, 2025 at 11:51 PM UTCinvestigating

   We are currently investigating this issue.

2. November 25, 2025 at 11:52 PM UTCinvestigating

   Stats updates are lagging as such the reporting data in dashboard will be slightly outdated.

3. November 25, 2025 at 11:57 PM UTCidentified

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

4. November 26, 2025 at 12:28 AM UTCmonitoring

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

5. November 26, 2025 at 2:15 AM UTCresolved

   This incident has been resolved.

1. November 6, 2025 at 4:29 PM UTCinvestigating

   We are currently investigating this issue.

2. November 6, 2025 at 4:44 PM UTCidentified

   The visual editor uses a 3rd party SAAS vendor. This incident is related to some connectivity issues with this vendors endpoint. The issue has happened multiple times today and we are working with the vendor to fix this.

3. November 6, 2025 at 5:41 PM UTCmonitoring

   The visual editor is now operational. We will keep monitoring and working with the vendor to implement a permanent fix.

4. November 6, 2025 at 5:44 PM UTCmonitoring

   The visual editor is not loading again. The issue is intermittent. We are working with the vendor to fix.

5. November 6, 2025 at 7:34 PM UTCmonitoring

   The visual editor is operational since 45 mins. Will continue monitoring this.

6. November 6, 2025 at 9:05 PM UTCresolved

   This incident has been resolved.

1. November 6, 2025 at 2:27 PM UTCinvestigating

   We are currently investigating this issue.

2. November 6, 2025 at 3:06 PM UTCidentified

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

3. November 6, 2025 at 3:07 PM UTCmonitoring

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

4. November 6, 2025 at 3:44 PM UTCresolved

   This incident has been resolved.

1. October 30, 2025 at 1:28 PM UTCinvestigating

   We are currently investigating issues with visual editor not loading in our US datacenter. We are working with the third party visual editor plugin to resolve this.

2. October 30, 2025 at 1:57 PM UTCidentified

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

3. October 30, 2025 at 1:59 PM UTCmonitoring

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

4. October 30, 2025 at 2:04 PM UTCresolved

   This incident has been resolved.

1. August 16, 2025 at 6:21 PM UTCinvestigating

   We are currently investigating this issue.

2. August 16, 2025 at 7:22 PM UTCidentified

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

3. August 16, 2025 at 7:55 PM UTCidentified

   We are currently applying a fix to the slowness issue. This process will take many hours. The system is stable now - however latencies are still higher than normal. We will keep this status page open until the fix is completely rolled out.

4. August 16, 2025 at 8:52 PM UTCmonitoring

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

5. August 16, 2025 at 8:54 PM UTCresolved

   This incident has been resolved.

1. June 4, 2025 at 5:20 AM UTCinvestigating

   We are seeing errors with displaying campaigns graphs in various dashboard pages.

2. June 4, 2025 at 5:44 AM UTCidentified

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

3. June 4, 2025 at 5:47 AM UTCmonitoring

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

4. June 4, 2025 at 6:11 AM UTCresolved

   This incident has been resolved.

1. May 27, 2025 at 1:55 AM UTCinvestigating

   We are currently investigating this issue.

2. May 27, 2025 at 2:08 AM UTCidentified

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

3. May 27, 2025 at 2:13 AM UTCmonitoring

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

4. May 27, 2025 at 2:24 AM UTCmonitoring

   We are continuing to monitor for any further issues.

5. May 27, 2025 at 2:29 AM UTCresolved

   This incident has been resolved.