Xsolla driftsforstyrrelser

1. 3. august 2026 kl. 21.59 UTCresolved

   Dato: 3. august 2026, 20: 45 - 21: 25 UTC Den 3. august 2026, mellem 20: 45 og 21: 25 UTC, Store API service oplevet forringet ydeevne. I denne periode, kan brugerne have observeret forhøjede svartider eller timeouts, når de kalder visse Store API metoder, som kunne resultere i langsommere lastning af lagerrelaterede sider og indkøbsstrømme. Problemet er løst fuldt ud, og tjenesten fungerer normalt. Vi fortsætter med at overvåge tjenesten og er ved at undersøge den grundlæggende årsag til at forhindre gentagelse. Vi undskylder for eventuelle ulemper.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 09.32 UTCidentified

   Vi oplever en delvis afbrydelse på grund af problemer med betalingsbehandling.

2. 24. juli 2026 kl. 09.40 UTCidentified

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

3. 24. juli 2026 kl. 09.41 UTCmonitoring

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

4. 24. juli 2026 kl. 09.48 UTCresolved

   Den 24. juli 2026, fra 2: 15 AM til 2: 40 AM PT, var betalingsoprettelsestjenesten ikke tilgængelig. I dette vindue, brugerne stødte på en fejl, når de forsøger at indlede en betaling. Vi undskylder oprigtigt for de ulemper, det måtte have forårsaget.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 18.18 UTCinvestigating

   Vi er i øjeblikket ved at undersøge rapporter om intermitterende latency påvirker store.xsolla.com API 'er, som kan resultere i midlertidig forbindelse forsinkelser for nogle brugere. Vores ingeniørhold arbejder aktivt på at identificere og løse årsagen. Vi vil give yderligere opdateringer, når vi fortsætter vores undersøgelse.

2. 14. juli 2026 kl. 18.57 UTCmonitoring

   Vi har identificeret og løst kilden til de intermitterende forbindelsesproblemer, som var isoleret til en specifik netværkszone. Vores engineering team med held migreret berørte tjenester til stabile zoner, og vi har bekræftet, at service forbindelse er blevet fuldt restaureret. Vi fortsætter med at overvåge ydeevne og udfører en post-hændelse gennemgang for at forhindre gentagelse.

3. 14. juli 2026 kl. 20.56 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. maj 2026 kl. 20.08 UTCinvestigating

   We are aware of an ongoing incident impacting Xsolla Launcher availability. End users may experience failed or slow downloads of launcher assets. The issue has been traced to a major outage at one of our upstream CDN providers, which is currently affecting their global content delivery network and API. Their engineering team has acknowledged the incident and is actively investigating the root cause. Our team is monitoring the situation closely and evaluating mitigation options on our side. We will post the next update as soon as we receive new information from the upstream provider or have additional details to share. We sincerely apologize for the inconvenience and appreciate your patience.

2. 13. maj 2026 kl. 20.28 UTCmonitoring

   Xsolla Launcher CDN traffic has recovered across affected endpoints. Per our upstream CDN provider, the CDN has mostly recovered but may still be partially unavailable for some users while remediation continues on their side We are continuing to monitor the situation.

3. 13. maj 2026 kl. 20.52 UTCresolved

   Our upstream CDN provider has confirmed that the incident on their side has been resolved. We sincerely apologize for the disruption and thank you for your patience throughout the incident.

1. 5. maj 2026 kl. 19.24 UTCinvestigating

   We are currently investigating reports of degraded performance affecting the Store API. Users may experience slow load times or errors when accessing Webshop-related pages. Our team is actively looking into the issue and will provide an update as soon as possible.

2. 5. maj 2026 kl. 19.46 UTCinvestigating

   We are currently investigating a service outage affecting the Store API and our Webshop product in general. Our team is actively working to identify the root cause and will provide an update as soon as possible.

3. 5. maj 2026 kl. 20.24 UTCmonitoring

   We have applied a mitigation that has restored Store API availability. Our team continues to monitor the service to ensure stability.

4. 5. maj 2026 kl. 21.03 UTCresolved

   All services are fully operational. We apologize for any inconvenience this may have caused and thank you for your patience.

1. 13. januar 2026 kl. 15.49 UTCresolved

   On January 13, 2025, between 5:45 AM and 6:35 AM PST, users and partners may have experienced limited access to Site Builder features: - Inability to access the Site Builder editor or view site listings in Partner Account - Login failures via User ID on partner-hosted sites Certain login requests were temporarily blocked after an upstream provider's security system flagged them as anomalous. The issue was quickly identified and resolved in coordination with the provider. All Site Builder functionality has been fully restored. We apologize for any inconvenience this may have caused.

1. 24. december 2025 kl. 21.30 UTCmonitoring

   We are currently experiencing degraded functionality in Xsolla Login Silent Authentication for Steam users due to an ongoing outage on the Steam platform. As a result, users attempting to authenticate via Xsolla Login using Steam may encounter login failures or timeouts. Other Xsolla Login authentication methods remain operational. We are actively monitoring the situation and will provide updates as Steam restores full service.

2. 25. december 2025 kl. 02.53 UTCmonitoring

   Steam has restored service and Xsolla Login Silent Authentication for Steam users is operating normally again. We are monitoring closely for the next 30 minutes to ensure stability.

3. 25. december 2025 kl. 03.21 UTCresolved

   This issue is resolved. Xsolla Login Silent Authentication for Steam users remains stable and fully operational.

1. 5. december 2025 kl. 23.59 UTCresolved

   On December 5th at 2:56 PM PST, our systems detected a DDoS attack targeting our platform. The attack was automatically identified and mitigated by our anti-DDoS protection. During the brief period before full mitigation was completed (approximately 3 minutes, from 2:56 PM to 2:59 PM PST), some users may have experienced increased latency or intermittent timeouts. The attack was fully mitigated, and all systems have been operating normally since 3:00 PM PST. No ongoing impact to stability or performance has been observed. We sincerely apologize for any disruption this may have caused and greatly appreciate your patience and understanding.

1. 1. december 2025 kl. 02.26 UTCinvestigating

   We are currently investigating this issue.

2. 1. december 2025 kl. 02.27 UTCinvestigating

   We are continuing to investigate this issue.

3. 1. december 2025 kl. 02.35 UTCmonitoring

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

4. 1. december 2025 kl. 04.21 UTCresolved

   At 6:15 PM PST on November 30, our monitoring systems detected abnormal traffic patterns that showed temporary network degradation and partial unavailability across our services. We traced the issue to a temporary network disruption affecting upstream internet service providers (external to our platform). The impact lasted approximately 14 minutes, with full service restored at 6:29 PM PST. All systems are operating normally since connectivity was reestablished. We sincerely apologize for the impact and truly appreciate your patience and understanding.

1. 16. oktober 2025 kl. 13.17 UTCidentified

   We're experiencing technical issues with payment processing. The issue has been identified and a fix is being implemented.

2. 16. oktober 2025 kl. 13.22 UTCmonitoring

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

3. 16. oktober 2025 kl. 13.26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 16. oktober 2025 kl. 13.54 UTCresolved

   On October 16, 2025, from 5:42 AM PT to 6:19 AM PT, payments were authorized but did not progress to completion. Affected customers saw pending charges without order confirmations, and no payment webhook notifications were sent. After the issue was resolved, all pending payments were successfully completed, and the corresponding webhook notifications were delivered. We sincerely apologize for any inconvenience this may have caused.

1. 23. september 2025 kl. 08.02 UTCresolved

   At 11:42 PM PST on September 22, our monitoring systems detected abnormal traffic patterns that caused temporary network degradation. As a result, users experienced slower response times and, in some cases, intermittent connectivity issues. The root cause was identified as a sudden surge of inbound requests that exceeded normal operating levels (DDoS attack), which temporarily impacted service availability. The incident was fully resolved by 12:01 AM PST on September 23, and services have been operating normally since then. We sincerely apologize for the impact and truly appreciate your patience and understanding.

1. 4. september 2025 kl. 18.27 UTCinvestigating

   We're experiencing an issue with Store API. We're investigating this issue and will post an update shortly.

2. 4. september 2025 kl. 21.05 UTCmonitoring

   We've implemented the fix for the issue. We'll monitor the services for the next 2 hours to ensure stability and will post an update.

3. 4. september 2025 kl. 23.07 UTCresolved

   We have confirmed that the issue has been fully resolved. The incident was triggered by unforeseen behavior in the purchasing flow, which placed excessive load on the underlying infrastructure and resulted in locks that caused, first, performance degradation and then downtime in request processing. From 11:05 AM PST to 1:29 PM PST Sept 4rd 2025, some users may have experienced delays or errors when purchasing digital goods. All systems are now operating normally. However, some users might have experienced delays with the delivery of purchased items - the process may have taken longer than expected. At the moment, all items have been delivered. We sincerely apologize for the inconvenience this incident may have caused and appreciate your patience while we worked to resolve it.

1. 25. juli 2025 kl. 13.23 UTCresolved

   Between 07:42 and 08:08 AM EST, some partner websites built with Site Builder were temporarily unavailable due to an unexpected issue affecting the service's infrastructure. The issue was identified and mitigated. Measures have been taken to reduce the risk of recurrence. We appreciate your understanding and patience.

1. 24. juni 2025 kl. 07.28 UTCmonitoring

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

2. 24. juni 2025 kl. 07.32 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 24. juni 2025 kl. 08.20 UTCresolved

   On June 24, 2025, from 12:18 AM to 12:26 AM PT, our users may have encountered errors accessing Xsolla services due to temporary network issues with upstream providers. We sincerely apologize for any inconvenience this may have caused.

1. 3. juni 2025 kl. 15.42 UTCresolved

   On June 3, 2025, from 8:03 AM PT to 8:24 AM PT, our users have encountered errors in credit card payment processing due to the unavailability of the Credit Cards service. We sincerely apologize for any inconvenience this may have caused.

1. 28. maj 2025 kl. 08.59 UTCidentified

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

2. 28. maj 2025 kl. 09.00 UTCidentified

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

3. 28. maj 2025 kl. 09.18 UTCmonitoring

   We've fixed the issue. We'll monitor the services for the next 10 minutes to ensure stability and will post an update.

4. 28. maj 2025 kl. 10.17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 28. maj 2025 kl. 10.50 UTCmonitoring

   On May 28, 2025, from 01:11 AM to 02:12 AM PT, our users and partners may have encountered errors in the authentication process due to partial unavailability of the authorization API. Approximately 35% of users were affected during this period. We sincerely apologize for any inconvenience this may have caused.

6. 28. maj 2025 kl. 10.52 UTCresolved

   This incident has been resolved.

1. 22. maj 2025 kl. 10.24 UTCresolved

   On May 21, 2025, from 9:51 PM PT to 10:25 PM PT, our users and partners may have encountered errors in authentication process due to partial unavailability of the authorization API. It affected about 30% of users. We sincerely apologize for any inconvenience this may have caused.

1. 3. marts 2025 kl. 00.21 UTCinvestigating

   Increased latency and intermittent network disconnections observed in network traffic, causing delays in application responses. The network team is analyzing the issue.

2. 3. marts 2025 kl. 00.44 UTCresolved

   From 2025-03-02 16:02 PST to 2025-03-02 16:21 PST, users may have experienced increased latency, causing delays in application responses. Network latency has now returned to normal levels, and we are not observing any issues within our infrastructure. We requested information from our backbone providers regarding any potential external incidents.

1. 20. februar 2025 kl. 13.09 UTCresolved

   Between February 20, 12:50 AM PST and February 20, 02:45 AM PST, we experienced an issue affecting websites using the default .xsolla.site domain. Users encountered errors or were unable to access sites built with Xsolla Sitebuilder relying on .xsolla.site. Our team identified the cause and implemented a solution. We apologize for any inconvenience this incident may have caused.

1. 30. januar 2025 kl. 07.00 UTCidentified

   There is degradation in the store.xsolla.com high response time, and unavailability of some methods.

2. 30. januar 2025 kl. 07.29 UTCmonitoring

   We have been working to resolve the issue and are currently monitoring the system's performance.

3. 30. januar 2025 kl. 08.04 UTCmonitoring

   There are issues with processing and delivering orders

4. 30. januar 2025 kl. 08.50 UTCmonitoring

   All the functionality is operational since 0:04 PST. We'll monitor the services for the next 30 minutes to ensure stability and will post another update.

5. 30. januar 2025 kl. 09.42 UTCresolved

   We can confirm that the issue is fully resolved. We apologize for the impact and thank you for your patience.