Xsolla Outage History
16 incidents recorded over the last 365 days, 10 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Xsolla Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Infrastructure Scheduled MaintenanceThe connectivity issues have been resolved and we are just completing some final checks/verification. | 30 min | Scheduled |
| Oct 21, 2026 | Proactive notice: PHP security vulnerabilitiesWe 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… | — | Investigating |
| Sep 28, 2026 | Site Builder Partner Sites UnavailableOn September 28, 2026, between 07:17 and 09:15 UTC, the Site Builder service was unavailable. During this time, users could not reach websites built with Site Builder. The issue has been fully resolved, and the service… | 2h 5m | Resolved |
| Aug 3, 2026 | Store API - Partial Service DegradationDate: August 3, 2026, 20:45 – 21:25 UTC On August 3, 2026, between 20:45 and 21:25 UTC, the Store API service experienced degraded performance. During this period, users may have observed elevated response times or… | 0 min | Resolved |
| Jul 24, 2026 | Payment Processing IssueOn July 24, 2026, from 2:15 AM to 2:40 AM PT, the payment creation service was unavailable. During this window, users encountered an error when attempting to initiate a payment. We sincerely apologize for any… | 16 min | Resolved |
| Jul 14, 2026 | Intermittent latency affecting store.xsolla.com APIsThis incident has been resolved. | 2h 37m | Resolved |
| Jul 9, 2026 | Infrastructure Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| May 13, 2026 | Xsolla Launcher - degraded availability due to upstream CDN incidentOur 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. | 43 min | Resolved |
| May 5, 2026 | Store API degraded performanceAll services are fully operational. We apologize for any inconvenience this may have caused and thank you for your patience. | 1h 38m | Resolved |
| Apr 28, 2026 | Infrastructure maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Mar 19, 2026 | Infrastructure maintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jan 13, 2026 | Site Builder - Partial Service DisruptionOn 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… | -124 min | Resolved |
| Dec 24, 2025 | Issue with Steam Silent AuthenticationThis issue is resolved. Xsolla Login Silent Authentication for Steam users remains stable and fully operational. | 5h 51m | Resolved |
| Dec 5, 2025 | DDoS Mitigation EventOn 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… | -63 min | Resolved |
| Dec 1, 2025 | Network issuesAt 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… | 1h 54m | Resolved |
| Nov 13, 2025 | Scheduled Maintenance – November 12–13, 2025The scheduled maintenance has been completed. | 4h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Xsolla incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Xsolla Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Xsolla acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Xsolla outage in this window ran 5h 51m, against a mean recovery of 2h. If you depend on Xsolla in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.