Live / Expo / Incident
Expo: Degraded performance on the NPM registry
Expo · expo.devMinor incidentResolved2026-09-04 02:00 UTC
Public — what happened
Summary
Expo reported slower-than-normal performance on the NPM registry beginning at 22:45 UTC on September 3, 2026, and rated the issue as minor. The company said this could make package installations stall until they time out and could cause EAS Builds that rely on NPM to fail. Expo indicated the problem was on NPM's side and said it would share updates from NPM as they came in. The incident's status was still listed as investigating, although a resolution time of 17:21 on September 4 was recorded.
Timeline
- Started — 2026-09-03 22:45 UTC
- Resolved — 2026-09-04 17:21 UTC · 18h 36m 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 Expo 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 Expo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Expo report →
More from Expo
Covered in The Squid’s Ink, Week 37, 2026, our weekly internet health report.