Historial de interrupciones de Pianoio

1. August 15, 2026 at 9:00 AM UTCmonitoring

   Piano identificó un problema que afectaba el acceso a Piano Insight para algunos usuarios. El certificado que causa los errores ha sido renovado, y la solución ha sido verificada internamente. Estamos monitoreando para confirmar que la cuestión está totalmente resuelta y compartiremos una nueva actualización en breve.

2. August 15, 2026 at 9:12 AM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

3. August 15, 2026 at 9:24 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 5, 2026 at 10:01 AM UTCinvestigating

   Estamos experimentando un problema con la generación de informes. Nuestro equipo está consciente y trabajando activamente para resolverlo.

2. August 5, 2026 at 10:59 AM UTCmonitoring

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

3. August 5, 2026 at 12:40 PM UTCresolved

   This incident has been resolved.

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

1. July 27, 2026 at 8:30 AM UTCidentified

   Piano está experimentando un problema que afecta a la entrada y registro de usuarios en la región de la UE. La ventana de inicio de sesión puede no abrirse o no responder. Hemos identificado la causa y nuestro equipo está implementando una solución. Compartiremos una actualización tan pronto como se disponga de más información.

2. July 27, 2026 at 8:34 AM UTCidentified

   Piano ha identificado que este problema afecta a la entrada y registro en todas las regiones, no sólo la UE como se informó inicialmente. Los usuarios de todas las regiones pueden experimentar los mismos síntomas: la ventana de inicio de sesión no se abre o no responde. Nuestro equipo sigue implementando la solución. Compartiremos una actualización tan pronto como se disponga de más información. Componentes afectados: Registro + Iniciar sesión - id.piano.io Registro + Iniciar sesión - Australia - id-au.piano.io Registro + Acceder - Asia - id-ap.piano.io Registro + Iniciar sesión - UE - id.piano.io

3. July 27, 2026 at 8:35 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

4. July 27, 2026 at 8:57 AM UTCidentified

   Piano puede confirmar este problema de hecho sólo afecta a las regiones de EE.UU. y de la UE, así como el entorno Sandbox. AP y AU no están afectados. Nos disculpamos por cualquier confusión causada por la actualización anterior. Sandbox no tiene un componente de página de estado dedicado ya que no es parte de la infraestructura de producción, esta actualización se proporciona para la visibilidad. Nuestro equipo sigue implementando la solución. Compartiremos una actualización tan pronto como se disponga de más información.

5. July 27, 2026 at 9:20 AM UTCmonitoring

   Piano ha implementado una solución en todas las regiones y entornos afectados, incluyendo Sandbox. La funcionalidad de registro y registro ha sido restaurada y funciona normalmente. Seguiremos vigilando la situación y proporcionaremos más información si surgen problemas.

6. July 27, 2026 at 2:50 PM UTCresolved

   Este incidente ha sido resuelto.

7. August 3, 2026 at 1:20 PM UTCpostmortem

   RCA for the incident can be found at [**this link**](https://rca.piano.io/wp-content/uploads/2026/07/2026-07-27-RCA-Identity-Management-login-issues.pdf).

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

1. July 24, 2026 at 7:51 AM UTCinvestigating

   Tras el mantenimiento de bases de datos programadas recientemente en la región de AP, hemos identificado una brecha de datos que afecta a las secciones de Registro de Suscripción e Insights de Suscripción del Dashboard Editor. Algunos clientes pueden notar que las compras recientes aún no se reflejan en el informe de la suscripción Log, y algunas mediciones en las entradas de suscripción pueden parecer temporalmente inconsistentes. Nuestro equipo está regenerando los datos afectados y espera que esto se resuelva en los próximos días. Compartiremos una actualización tan pronto como tengamos más información.

2. July 27, 2026 at 8:04 AM UTCmonitoring

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

3. July 27, 2026 at 8:39 AM UTCmonitoring

   Hemos restaurado los datos afectados para las entradas de suscripción, y las mediciones ahora deben estar mostrando correctamente. El informe de la suscripción Log aún no se ha recuperado por completo, y algunas compras recientes todavía pueden faltar de esta opinión. Nuestro equipo continúa regenerando los datos restantes. Compartiremos una actualización tan pronto como tengamos más información.

4. July 28, 2026 at 12:22 AM UTCresolved

   La brecha de datos que afecta al Registro de Suscripción se ha resuelto plenamente y todas las compras recientes en la región de la AP se reflejan correctamente en el informe. Combinado con la fijación anterior a la Insights de suscripción, ambas áreas afectadas del panel Publisher han sido restauradas a la normalidad. Este incidente ya está resuelto. Gracias por su paciencia mientras completamos la regeneración de datos.

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

1. July 23, 2026 at 12:31 PM UTCinvestigating

   Actualmente estamos investigando una cuestión que afecta a la entrega de muros de pago y experiencias para los editores en Asia y Australia. Algunas solicitudes no se completan con éxito. Nuestro equipo de ingeniería está trabajando activamente para identificar la causa raíz y restaurar el servicio normal. Compartiremos una actualización tan pronto como tengamos más información.

2. July 23, 2026 at 1:00 PM UTCidentified

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

3. July 23, 2026 at 1:07 PM UTCmonitoring

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

4. July 23, 2026 at 3:50 PM UTCresolved

   Un problema de infraestructura interna que afecta a una dependencia del sistema de backend en nuestro centro de datos de Tokio causó fallas de autenticación que encadenó en fallos de solicitud para la API de Audience. Debido a que el tráfico de Compositores para Asia (AP) y Australia (AU) viajó por este caso, ambas regiones vieron fallos de las solicitudes de Compositor. Este incidente ha sido resuelto. Nuestro equipo de ingeniería identificó la causa y restauró el sistema afectado; el servicio ha vuelto a la normalidad en todas las regiones. Nos disculpamos por cualquier inconveniente que esto pueda haber causado.

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

1. July 20, 2026 at 8:36 PM UTCidentified

   Estamos observando retrasos en el procesamiento de datos en el backend del perfil de usuario causado por los esfuerzos de mejora de datos para gestionar el prefijo cx y el ID de aplicación del compositor. Si está utilizando la API de actualización de perfil externo de cxense (https://api.cxense.com/profile/user/external/update) observará 1-2 horas de retrasos al leer el mismo perfil utilizando (https://api.cxense.com/profile/user/external/update). Nuestro equipo ahora está conciliando los datos de nuevo en una visión única y correcta, y esta reconciliación es la fuente del retraso continuo. No se han perdido datos, todos los eventos están siendo procesados, actualmente con un retraso aproximado de 1–2 horas. Nos disculpamos por la molestia y compartiremos una actualización como el atraso claro

2. July 21, 2026 at 11:52 AM UTCidentified

   Los retrasos en el procesamiento de datos continúan en el backend de Perfiles de Usuario, con retrasos actuales de 1–2 horas. Hemos identificado que un cambio reciente de datos llevó a un aumento significativo del volumen de datos para un subconjunto de clientes, que es el principal impulsor del atraso. Nuestro equipo está aumentando cuidadosamente el rendimiento de procesamiento y supervisa de cerca la estabilidad general del sistema para evitar introducir nuevas cuestiones. Somos optimistas sobre la estabilización de la situación pronto y compartiremos una actualización tan pronto como tengamos más información.

3. July 22, 2026 at 6:30 AM UTCmonitoring

   El procesamiento de datos en el backend de Perfiles de usuario de Piano ha vuelto a casi en tiempo real y el atraso se aclara. Estamos estableciendo este incidente a Monitoreo mientras nuestro equipo completa la limpieza residual del cambio de datos anterior. Compartiremos otra actualización una vez que el incidente se resuelva completamente.

4. July 24, 2026 at 8:38 PM UTCresolved

   El incidente se ha resuelto después de la vigilancia durante más de 24 horas. Estamos viendo el procesamiento de los datos en tiempo real

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

1. July 20, 2026 at 7:46 PM UTCidentified

   Estamos observando retrasos en el procesamiento de datos en el respaldo del perfil de usuario causado por los esfuerzos de mejora de datos para gestionar el prefijo cx y el ID de aplicación del compositor. Si está utilizando la API de actualización de perfil externo de cxense (https://api.cxense.com/profile/user/external/update) observará 1-2 horas de retrasos al leer el mismo perfil utilizando (https://api.cxense.com/profile/user/external/update). Nuestro equipo ahora está conciliando los datos de nuevo en una visión única y correcta, y esta reconciliación es la fuente del retraso continuo. No se han perdido datos, todos los eventos están siendo procesados, actualmente con un retraso aproximado de 1–2 horas. Nos disculpamos por la molestia y compartiremos una actualización como el atraso claro

2. July 20, 2026 at 8:31 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

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

1. June 22, 2026 at 2:59 PM UTCinvestigating

   We are currently experiencing a minor service disruption affecting user logins to the Piano dashboards, caused by an ongoing outage on Cloudflare's side. Our team is actively monitoring the situation. We apologize for any inconvenience this may cause and appreciate your patience. Further updates will be provided as soon as more information becomes available. For reference: https://www.cloudflarestatus.com/incidents/v3yl7jqmqj51

2. June 22, 2026 at 5:30 PM UTCmonitoring

   The incident has been mitigated, along with our provider's resolution. We will continue to monitor the situation.

3. June 23, 2026 at 1:02 AM UTCresolved

   This incident has been resolved.

1. June 9, 2026 at 9:52 AM UTCinvestigating

   Since approximately 11:00 PM (UTC) on June 8, 2026, there have been intermittent delays loading files into Snowflake. The average load duration is currently about 10 minutes, compared to the usual under 2 minutes. The issue has been identified and a ticket has been opened with Snowflake.

2. June 10, 2026 at 9:55 AM UTCresolved

   The incident has been resolved and is no longer affecting Piano Analytics. We apologise for the inconvenience caused.

3. June 10, 2026 at 9:55 AM UTCpostmortem

   **Incident explanation:** The latency was caused by an issue on our cloud data platform provider's side. An internal infrastructure configuration change introduced resource contention that affected workloads with high ingestion concurrency, leading to elevated response times and intermittent timeouts when loading files. The change has been reverted by the provider, and ingestion performance has fully returned to its normal baseline. **Actions performed:** Opened and tracked an incident with our data platform provider and provided detailed monitoring evidence to support their investigation. Deployed mitigations on our streaming ingestion stack (increased service scaling and improved handling of stalled ingestion calls) to limit customer impact during the incident. Temporarily tuned ingestion timeout and retry settings to keep file loading as stable as possible while the root cause was being addressed. Continuously monitored ingestion latency and error rates until performance returned to normal. Confirmed full recovery, then reverted the temporary configuration to restore standard behaviour and avoid masking any future issues. **Actions to come:** Continued close monitoring of ingestion latency over the coming days to confirm lasting stability. Keep the temporary mitigation patterns configurable in the code so they can be re-applied quickly should a similar provider-side degradation occur.

1. May 29, 2026 at 2:31 AM UTCinvestigating

   We are currently experiencing an issue with the Content Crawler, which is failing to crawl content. Our team is actively investigating the root cause. We will provide further updates as more information becomes available.

2. May 29, 2026 at 2:31 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 29, 2026 at 8:39 AM UTCidentified

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

4. May 29, 2026 at 9:24 AM UTCmonitoring

   A fix has been implemented and all Content pipeline services have been restored. Some processing delays may persist while the crawling backlog clears. We will continue to monitor and confirm full resolution.

5. May 29, 2026 at 2:03 PM UTCresolved

   This incident has been resolved.

6. June 4, 2026 at 9:00 AM UTCpostmortem

   RCA report for the incident is available at [**this link**](https://docs.piano.io/wp-content/uploads/2026/06/2026-05-29-RCA-Content-Crawler-Service-Disruption-1.pdf).

1. May 28, 2026 at 4:27 PM UTCidentified

   We identified an issue in our systems starting around 10:20 UTC that is currently degrading CXSense platform responsiveness over the /public/user/id endpoint. As a result, some users may experience failed requests, while others may experience longer response times and timeouts. Our engineering team is actively investigating and working on mitigation efforts. We will continue to provide updates as more information becomes available.

2. May 28, 2026 at 5:10 PM UTCmonitoring

   A fix has been implemented and we are currently monitoring the results. At this time, API performance has returned to normal operation levels and the platform is behaving as expected again. We will continue monitoring closely to ensure stability.

3. May 29, 2026 at 3:53 AM UTCresolved

   This incident has been resolved.

4. June 15, 2026 at 9:25 AM UTCpostmortem

   RCA report for the incident is available at [**this link**](https://docs.piano.io/wp-content/uploads/2026/06/2026-05-28-RCA-Audience-API-Failures-happening-in-Europe-environment.pdf).

1. May 20, 2026 at 10:19 AM UTCmonitoring

   On 20 May 2026, starting at approximately 09:58 UTC, we identified an issue affecting Piano Activation in the US environment, impacting the Dashboard, Piano ID authentication, and checkout flows. A fix has been applied and the platform is now operating normally. We are continuing to monitor the situation and further details will follow. We apologise for any inconvenience caused.

2. May 20, 2026 at 12:41 PM UTCresolved

   The incident has been resolved. All services are operating normally. Between approximately 09:58 and 10:11 UTC, users in the US region may have experienced issues accessing the Piano Dashboard, signing in via Piano ID, or completing checkout flows. This was caused by a routine configuration update to our US environment that introduced a conflict and disrupted traffic routing to the affected services. Our team identified the issue, rolled back the change, and confirmed full recovery shortly after. To prevent this from happening again, we are reviewing our release process and will validate the change in a controlled manner before re-applying it. We apologize for the inconvenience and thank you for your patience.

1. May 15, 2026 at 8:03 AM UTCidentified

   We are currently experiencing degraded performance across the Publisher Dashboard in the AP environment, with data taking up to 3 hours longer than usual to reflect recent changes. This may affect any section of the Dashboard — including user search, reporting, and other data views. Our engineering team has identified the underlying cause and is actively working on a resolution. We will provide updates as the situation progresses.

2. May 16, 2026 at 7:16 AM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 1:48 PM UTCinvestigating

   We are currently investigating issues affecting the execution of experiences in our European region for segmentation that relies on custom field rules. Impacted users may notice that experiences are not triggering as expected, not reaching the desired outcome. Our engineering team is actively investigating the issue.

2. May 13, 2026 at 2:02 PM UTCmonitoring

   The issue has been identified and fixed; we're currently monitoring the experience executions.

3. May 13, 2026 at 6:00 PM UTCresolved

   This incident has been resolved.

4. May 15, 2026 at 9:39 AM UTCpostmortem

   An infrastructure update to the EU environment introduced an incompatibility that prevented Composer from retrieving Custom Fields. The issue was limited to the EU region and did not affect other environments. The update introduced a behavioural change in the network routing layer where a configuration setting that had previously been relied upon was no longer honoured under the new setup. This incompatibility was not detected during pre-production testing, as the test environments did not fully replicate the conditions needed to surface the issue. The root cause was identified and the configuration gap was addressed promptly. Piano is taking steps to improve parity between pre-production and production environments and to strengthen the validation process ahead of future infrastructure changes to prevent similar issues.

1. May 13, 2026 at 8:52 AM UTCresolved

   Between 07:42 and 07:52 AM UTC, Piano experienced elevated error rates affecting the Publisher API and ID API in the EU environment. The incident occurred during an ingress upgrade from a deprecated version to the current supported version, which caused a routing configuration incompatibility. The issue lasted approximately 10 minutes and has been fully resolved. Publisher Dashboard, Checkout, and access controls in Composer operated normally throughout the incident and were not affected.

1. May 8, 2026 at 10:21 PM UTCinvestigating

   We are currently experiencing a production incident on Piano Analytics products. Please excuse us for any inconvenience caused.

2. May 8, 2026 at 10:21 PM UTCresolved

   The issue has been resolved and all Piano Analytics tools and interfaces are fully available. We are currently catching up the delay in real-time data retrieval.

1. May 8, 2026 at 6:04 AM UTCinvestigating

   Composer is experiencing a service incident affecting C1X segmentation in both EU and US regions. Impact includes high error rates, degraded segment lookup, and degraded widget performance. The issue started at approximately 22:00 UTC on May 7 and continues with periods of instability. Our team is actively investigating the issue.

2. May 8, 2026 at 9:26 AM UTCmonitoring

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

3. May 8, 2026 at 5:36 PM UTCresolved

   The incident has been resolved.

1. May 6, 2026 at 1:17 PM UTCidentified

   We are currently experiencing an issue with Composer in our sandbox environment; the Composer module and experiences fail to load. Our team has identified the root cause and is actively working to resolve the issue. We will provide updates as more information becomes available.

2. May 6, 2026 at 1:43 PM UTCmonitoring

   The team has deployed a fix, and the issue has been resolved. Experiences are executing, and the Composer module is working normally. We will continue monitoring the remediation.

3. May 6, 2026 at 1:44 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. May 7, 2026 at 6:28 AM UTCresolved

   This incident has been resolved.

1. May 5, 2026 at 8:21 AM UTCmonitoring

   Between 06:48 and 07:05 UTC, Piano ID API experienced elevated error rates in the US cluster. Requests requiring user authentication, token verification, and user profile retrieval were affected. Other Piano services including Composer and VX subscription management were not impacted. Service has been fully restored and all systems are operating normally. We apologize for any disruption caused during this incident.

2. May 5, 2026 at 8:21 AM UTCresolved

   This incident has been resolved.

1. April 27, 2026 at 4:57 PM UTCinvestigating

   We have found an issue with our priority rules for API interaction on server/edge in Composer. The dev team is currently investigating. Clients may find their list order being changed or unsorted without any user interaction. We will continue updating this incident once we identify the root cause.

2. April 27, 2026 at 6:37 PM UTCinvestigating

   Our team has restored the priority rules to their pre-incident state while we continue to investigate the root cause. We advise customers to avoid making changes to priority rules until the investigation is complete. We will provide further updates as more information becomes available.

3. April 27, 2026 at 10:01 PM UTCmonitoring

   The issue has been identified and mitigated; we will continue monitoring the remediation.

4. April 28, 2026 at 9:20 AM UTCresolved

   This incident has been resolved.

5. April 28, 2026 at 2:04 PM UTCpostmortem

   RCA report for the incident is available at [**this link**](https://docs.piano.io/wp-content/uploads/2026/04/2025-05-06-RCA-Experience-Priority-Data-Incident.pdf).