Pianoio driftsforstyrrelser

1. 15. august 2026 kl. 09.00 UTCmonitoring

   Piano identificerede et problem, der påvirker adgangen til Piano Insight for nogle brugere. Det certifikat, der forårsager fejlene, er blevet fornyet, og fixet er blevet verificeret internt. Vi overvåger for at bekræfte, at spørgsmålet er helt løst, og vi vil snart dele en yderligere opdatering.

2. 15. august 2026 kl. 09.12 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

3. 15. august 2026 kl. 09.24 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 5. august 2026 kl. 10.01 UTCinvestigating

   Vi oplever et problem med rapportgenerationen. Vores team er bevidst om og aktivt arbejder på at løse det.

2. 5. august 2026 kl. 10.59 UTCmonitoring

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

3. 5. august 2026 kl. 12.40 UTCresolved

   This incident has been resolved.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 08.30 UTCidentified

   Piano oplever et problem, der påvirker login og registrering for brugere i EU-regionen. Indlogningsvinduet kan ikke åbnes, eller kan være uresponderende. Vi har identificeret årsagen, og vores team sender et fix. Vi vil dele en opdatering, så snart yderligere oplysninger er tilgængelige.

2. 27. juli 2026 kl. 08.34 UTCidentified

   Klaano har konstateret, at dette spørgsmål påvirker login og registrering på tværs af alle regioner, ikke kun EU som oprindeligt rapporteret. Brugere i alle regioner kan opleve de samme symptomer - login vindue undlader at åbne, eller bliver ulydhør. Vores hold fortsætter med at implementere fixet. Vi vil dele en opdatering, så snart yderligere oplysninger er tilgængelige. Berørte komponenter: Registrering + Login - US - id.piano.io Registrering + Login - Australien - id- au.piano.io Registrering + Login - Asien - id- ap.piano.io Registrering + Login - EU - id.piano.io

3. 27. juli 2026 kl. 08.35 UTCidentified

   Vi fortsætter med at arbejde på en løsning på dette problem.

4. 27. juli 2026 kl. 08.57 UTCidentified

   Piano kan bekræfte dette spørgsmål i virkeligheden kun påvirke USA 's og EU' s regioner samt miljøet i Sandbox. AP og AU påvirkes ikke. Vi undskylder for enhver forvirring forårsaget af den tidligere opdatering. Sandbox har ikke en dedikeret status side komponent, da det ikke er en del af produktionsinfrastrukturen, denne opdatering er givet for synlighed. Vores hold fortsætter med at implementere fixet. Vi vil dele en opdatering, så snart yderligere oplysninger er tilgængelige.

5. 27. juli 2026 kl. 09.20 UTCmonitoring

   Piano har implementeret et fix på tværs af alle berørte regioner og miljøer, herunder Sandbox. Login og registrering funktionalitet er blevet genoprettet og fungerer normalt. Vi vil fortsat overvåge situationen og give en yderligere opdatering, hvis der opstår problemer.

6. 27. juli 2026 kl. 14.50 UTCresolved

   Denne hændelse er blevet løst.

7. 3. august 2026 kl. 13.20 UTCpostmortem

   RCA for hændelsen kan findes på [* * dette link * *] (https: / / rca.piano.io / wp- content / uploads / 2026 / 07 / 2026- 07- 27- RCA- Identitets- Management- login- issues.pdf).

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 07.51 UTCinvestigating

   Efter nylig planlagt databasevedligeholdelse i AP-regionen, har vi identificeret et datagab, der påvirker Abonnementslog- og Abonnementsindsigelsesafdelingerne i Publisher Dashboard. Nogle kunder kan bemærke, at nylige køb endnu ikke afspejles i Abonnementslograpporten, og nogle målinger i Abonnementsindsigter kan forekomme midlertidigt inkonsekvente. Vores team regenererer de berørte data og forventer, at dette vil blive løst inden for de næste par dage. Vi vil dele en opdatering, så snart vi har flere oplysninger.

2. 27. juli 2026 kl. 08.04 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 27. juli 2026 kl. 08.39 UTCmonitoring

   Vi har genoprettet de berørte data for Abonnementsindsigelser, og målinger der bør nu vise korrekt. Abonnementslograpporten er endnu ikke fuldt ud genvundet, og nogle nylige køb mangler måske stadig fra dette synspunkt. Vores team fortsætter med at regenerere de resterende data. Vi vil dele en opdatering, så snart vi har flere oplysninger.

4. 28. juli 2026 kl. 00.22 UTCresolved

   Datagabet, der påvirker Abonnementsloggen, er nu blevet fuldstændig løst, og alle nylige køb i AP-regionen afspejles korrekt i rapporten. Kombineret med det tidligere fix til Abonnementsindsigelser, er begge berørte områder af Publisher Dashboard blevet genoprettet til normal. Denne hændelse er nu løst. Tak for din tålmodighed, mens vi afsluttede datafornyelsen.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 12.31 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et spørgsmål, der påvirker leveringen af betalingsvægge og erfaringer for forlag i Asien og Australien. Nogle anmodninger er ikke at fuldføre med succes. Vores ingeniørhold arbejder aktivt på at identificere årsagen og genoprette normal service. Vi vil dele en opdatering, så snart vi har flere oplysninger.

2. 23. juli 2026 kl. 13.00 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 23. juli 2026 kl. 13.07 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 23. juli 2026 kl. 15.50 UTCresolved

   Et internt infrastrukturproblem, der påvirker en back-end-systemafhængighed i vores Tokyo datacenter forårsagede autentificering fejl, der cascaded i anmodning fejl for Audience API. Fordi Composer trafik for Asien (AP) og Australien (AU) ruter gennem denne instans, begge regioner oplevede svigt af Composer anmodninger. Denne hændelse er blevet løst. Vores ingeniørhold identificerede årsagen og genoprettede det berørte system; service er vendt tilbage til normal i alle regioner. Vi undskylder for eventuelle ulemper.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. juli 2026 kl. 20.36 UTCidentified

   Vi observerer forsinkelser i databehandling på brugerprofilbackend forårsaget af data forbedring indsats for at styre cx præfiks og komponistprogram ID. Hvis du bruger cxense 's eksterne profil opdatering API (https: / / api.cxense.com / profil / user / external / update), vil du observere 1-2 timers forsinkelser, når du læser den samme profil ved hjælp af (https: / / api.cxense.com / profil / user / external / update). Vores team er nu ved at forene data tilbage i en enkelt, korrekt opfattelse, og denne forsoning er kilden til den igangværende forsinkelse. Ingen data er gået tabt, alle hændelser behandles, i øjeblikket med en omtrentlig forsinkelse på 1-2 timer. Vi undskylder for ulejligheden og vil dele en opdatering som backlog klar

2. 21. juli 2026 kl. 11.52 UTCidentified

   Databehandling forsinkelser fortsætte på brugerprofiler backend, med aktuelle forsinkelser på 1-2 timer. Vi har identificeret, at en nylig dataændring førte til en betydelig stigning i datamængden for en undergruppe af kunder, som er den primære driver af backlog. Vores team er omhyggeligt at øge processens gennemløb, samtidig med at vi nøje overvåger systemets generelle stabilitet for at undgå at indføre yderligere spørgsmål. Vi er optimistiske med hensyn til at stabilisere situationen hurtigt og vil dele en opdatering, så snart vi har flere oplysninger.

3. 22. juli 2026 kl. 06.30 UTCmonitoring

   Databehandling på Piano Audience User Profiles backend er vendt tilbage til nær real- tid og backlog er ryddet. Vi sætter denne hændelse til Overvågning, mens vores team fuldender residual oprydning fra de tidligere data ændring. Vi vil dele en yderligere opdatering, når hændelsen er helt løst.

4. 24. juli 2026 kl. 20.38 UTCresolved

   Hændelsen er blevet løst efter overvågning i mere end 24 timer. Vi ser behandlingen af data i real- tid

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. juli 2026 kl. 19.46 UTCidentified

   Vi observerer forsinkelser i databehandlingen på User profilbacken forårsaget af data forbedring indsats for at styre cx prefix og komponist applikation ID. Hvis du bruger cxense 's eksterne profil opdatering API (https: / / api.cxense.com / profil / user / external / update), vil du observere 1-2 timers forsinkelser, når du læser den samme profil ved hjælp af (https: / / api.cxense.com / profil / user / external / update). Vores team er nu ved at forene data tilbage i en enkelt, korrekt opfattelse, og denne forsoning er kilden til den igangværende forsinkelse. Ingen data er gået tabt, alle hændelser behandles, i øjeblikket med en omtrentlig forsinkelse på 1-2 timer. Vi undskylder for ulejligheden og vil dele en opdatering som backlog klar

2. 20. juli 2026 kl. 20.31 UTCidentified

   Vi fortsætter med at arbejde på en løsning på dette problem.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 14.59 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. 22. juni 2026 kl. 17.30 UTCmonitoring

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

3. 23. juni 2026 kl. 01.02 UTCresolved

   This incident has been resolved.

1. 9. juni 2026 kl. 09.52 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. 10. juni 2026 kl. 09.55 UTCresolved

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

3. 10. juni 2026 kl. 09.55 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. 29. maj 2026 kl. 02.31 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. 29. maj 2026 kl. 02.31 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. maj 2026 kl. 08.39 UTCidentified

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

4. 29. maj 2026 kl. 09.24 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. 29. maj 2026 kl. 14.03 UTCresolved

   This incident has been resolved.

6. 4. juni 2026 kl. 09.00 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. 28. maj 2026 kl. 16.27 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. 28. maj 2026 kl. 17.10 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. 29. maj 2026 kl. 03.53 UTCresolved

   This incident has been resolved.

4. 15. juni 2026 kl. 09.25 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. 20. maj 2026 kl. 10.19 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. 20. maj 2026 kl. 12.41 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. 15. maj 2026 kl. 08.03 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. 16. maj 2026 kl. 07.16 UTCresolved

   This incident has been resolved.

1. 13. maj 2026 kl. 13.48 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. 13. maj 2026 kl. 14.02 UTCmonitoring

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

3. 13. maj 2026 kl. 18.00 UTCresolved

   This incident has been resolved.

4. 15. maj 2026 kl. 09.39 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. 13. maj 2026 kl. 08.52 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. 8. maj 2026 kl. 22.21 UTCinvestigating

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

2. 8. maj 2026 kl. 22.21 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. 8. maj 2026 kl. 06.04 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. 8. maj 2026 kl. 09.26 UTCmonitoring

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

3. 8. maj 2026 kl. 17.36 UTCresolved

   The incident has been resolved.

1. 6. maj 2026 kl. 13.17 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. 6. maj 2026 kl. 13.43 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. 6. maj 2026 kl. 13.44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7. maj 2026 kl. 06.28 UTCresolved

   This incident has been resolved.

1. 5. maj 2026 kl. 08.21 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. 5. maj 2026 kl. 08.21 UTCresolved

   This incident has been resolved.

1. 27. april 2026 kl. 16.57 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. 27. april 2026 kl. 18.37 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. 27. april 2026 kl. 22.01 UTCmonitoring

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

4. 28. april 2026 kl. 09.20 UTCresolved

   This incident has been resolved.

5. 28. april 2026 kl. 14.04 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).