VRChat experienced a critical incident on October 20, 2025 affecting Authentication / Login and Social / Friends List and 1 more component, lasting 12h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 09:59 AM UTC
We're aware of login issues caused by a large-scale event at an upstream provider. The scale of this outage unfortunately affected our ability to post an official status update til now.
- identified Oct 20, 2025, 10:32 AM UTC
The VRChat API is currently unavailable due to an internal service failure caused by the upstream provider outage. We're working on bringing our API services back online as quickly as possible.
- identified Oct 20, 2025, 11:33 AM UTC
We're still working on bringing our API services back online. Our recovery efforts are currently being delayed due to insufficient compute services capacity at our upstream provider.
- identified Oct 20, 2025, 04:26 PM UTC
We're continuing to work on bringing VRChat API services back online as soon as possible. At this time we were able to bring parts of our API services up in a limited capacity, while leaving heavier services, such as friends lists, offline for now.
- identified Oct 20, 2025, 07:31 PM UTC
We're continuing our work to bring VRChat API services back online and so far managed to manually add additional compute services capacity to our API cluster to reduce overall response latency and error rate. Once we manage to bring sufficient headroom capacity online, we'll work on re-enabling friends lists and avatar lists endpoints.
- identified Oct 20, 2025, 07:50 PM UTC
We're making progress in adding more compute capacity to bring our API services back online and thus re-enabled friends lists and avatar lists endpoints now. Your friends list may still show incorrect and outdated information until you restart VRChat.
- monitoring Oct 20, 2025, 08:36 PM UTC
VRChat services are now fully up and running again. We'll continue to monitor the situation for the next hours to ensure stable operation of our services and will make adjustments as necessary.
- resolved Oct 20, 2025, 10:02 PM UTC
This incident has been resolved.