55 incidentes de Xsolla registrados desde septiembre de 2021, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.
We are aware of critical security vulnerabilities in PHP, announced publicly on 20 October 2026. We are actively patching and mitigating affected systems, and added protections are in place at our web application firewall layer. No action is required from you . If any change could affect your services, we will post here before it begins.
Site Builder no estaba disponible temporalmente debido a un problema inesperado
Continuamos monitoreando cualquier otro problema.
Actualmente estamos investigando esta cuestión.
Seguimos investigando esta cuestión.
Se ha aplicado una solución y estamos monitoreando los resultados.
El 28 de septiembre de 2026, entre 07:17 y 09:15 UTC, el servicio del constructor del sitio no estaba disponible. Durante este tiempo, los usuarios no pudieron llegar a sitios web construidos con Site Builder. La cuestión se ha resuelto plenamente y el servicio funciona normalmente. Continuamos monitoreando el servicio y estamos investigando la causa raíz para evitar la recurrencia. Nos disculpamos por la molestia que esto causó.
Traducido automáticamente desde la actualización oficial del incidente.
Fecha: 3 de agosto de 2026, 20:45 – 21:25 UTC El 3 de agosto de 2026, entre 20:45 y 21:25 UTC, el servicio Store API experimentó un rendimiento degradado. Durante este período, los usuarios pueden haber observado tiempos o plazos elevados de respuesta al llamar a ciertos métodos de API de la tienda, lo que podría dar lugar a una carga más lenta de páginas relacionadas con la tienda y flujos de compra. La cuestión se ha resuelto plenamente y el servicio funciona normalmente. Continuamos monitoreando el servicio y estamos investigando la causa raíz para evitar la recurrencia. Nos disculpamos por cualquier inconveniente que esto pueda haber causado.
Traducido automáticamente desde la actualización oficial del incidente.
Estamos experimentando un outage parcial debido a problemas con el procesamiento de pagos.
Seguimos trabajando en una solución para esta cuestión.
Se ha aplicado una solución y estamos monitoreando los resultados.
El 24 de julio de 2026, de 2:15 AM a 2:40 AM PT, el servicio de creación de pago no estaba disponible. Durante esta ventana, los usuarios encontraron un error al intentar iniciar un pago. Sinceramente nos disculpamos por cualquier inconveniente que esto pueda haber causado.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando informes de latencia intermitente que afectan a las API de store.xsolla.com, lo que puede dar lugar a demoras de conexión temporales para algunos usuarios. Nuestro equipo de ingeniería está trabajando activamente para identificar y resolver la causa raíz. Proporcionaremos más actualizaciones a medida que continuemos nuestra investigación.
Hemos identificado y resuelto la fuente de los problemas de conectividad intermitente, que fueron aislados a una zona de red específica. Nuestro equipo de ingeniería migraron con éxito los servicios afectados a zonas estables, y hemos confirmado que la conectividad de servicio ha sido totalmente restaurada. Seguimos monitoreando el desempeño y estamos llevando a cabo un examen posterior al incidente para evitar la recurrencia.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
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.
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.
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.
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.
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.
We have applied a mitigation that has restored Store API availability. Our team continues to monitor the service to ensure stability.
All services are fully operational. We apologize for any inconvenience this may have caused and thank you for your patience.
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.
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.
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.
This issue is resolved. Xsolla Login Silent Authentication for Steam users remains stable and fully operational.
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.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
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.
We're experiencing technical issues with payment processing. The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
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.
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.
We're experiencing an issue with Store API. We're investigating this issue and will post an update shortly.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
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.
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.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We've fixed the issue. We'll monitor the services for the next 10 minutes to ensure stability and will post an update.
We are continuing to monitor for any further issues.
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.
This incident has been resolved.
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.
Increased latency and intermittent network disconnections observed in network traffic, causing delays in application responses. The network team is analyzing the issue.
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.
