Live / VRChat / Incident
VRChat: Realtime Networking Performance Issues (USE, USW)
VRChat · vrchat.comMinor incidentResolved2026-10-07 04:29 UTC
Public — what happened
Summary
VRChat reported a minor problem with its realtime servers in the US East and US West regions starting at 02:02 UTC on October 7, 2026, which could cause timeouts and sluggish performance in instances hosted there. The company said it was seeing connectivity trouble at an upstream network provider and suggested users pick another region when creating instances, noting other regions seemed unaffected. By 02:35 UTC VRChat said the issues had cleared and it was watching for stability, and the incident was marked resolved at 04:29.
Affected
USA, West (San José), USA, East (Washington D.C.)
Timeline
- Started — 2026-10-07 02:02 UTC
- Investigating — 2026-10-07 02:02 UTC
- Monitoring — 2026-10-07 02:35 UTC
- Resolved — 2026-10-07 04:29 UTC · 2h 27m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach VRChat against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for VRChat: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the VRChat report →
More from VRChat
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.