VRChat incident

Realtime Networking Connectivity Issues

Critical Resolved View vendor source →

VRChat experienced a critical incident on July 24, 2025 affecting USA, West (San José), lasting 18h 51m. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2025, 10:19 PM UTC
Resolved
Jul 25, 2025, 05:10 PM UTC
Duration
18h 51m
Detected by Pingoru
Jul 24, 2025, 10:19 PM UTC

Affected components

USA, West (San José)

Update timeline

  1. investigating Jul 24, 2025, 10:19 PM UTC

    We are currently investigating login issues with VRChat.

  2. investigating Jul 24, 2025, 10:22 PM UTC

    We're observing upstream provider network connectivity issues with our realtime servers which may result in timeouts and degraded performance across instances hosted in the US West region. Other regions appear to be unaffected by this issue, for the time being you may temporarily want to choose a different region during instance creation while we're investigating this incident with our provider.

  3. investigating Jul 24, 2025, 10:31 PM UTC

    We're observing upstream provider network connectivity issues with our realtime servers which may result in timeouts and degraded performance across instances hosted in the US West region. Other regions appear to be unaffected by this issue, for the time being you may temporarily want to choose a different region during instance creation while we're investigating this incident with our provider.

  4. investigating Jul 25, 2025, 02:08 AM UTC

    Our upstream provider is still working on analyzing the root cause and implementing a workaround for the network connectivity issues impacting our realtime servers in the US West region. Other regions are unaffected by this issue, for the time being you may temporarily want to choose a different region during instance creation while we're investigating this incident with our provider.

  5. investigating Jul 25, 2025, 03:58 AM UTC

    While our upstream provider is still investigating the network connectivity issues, you may be able use a VPN, such as Cloudflare WARP (https://one.one.one.one/) or other paid alternatives, as a temporary workaround.

  6. resolved Jul 25, 2025, 05:10 PM UTC

    This incident has been resolved.