Live / Onshape / Incident
Onshape: Exports are delayed in all regions, interruptions when modeling.
Onshape · onshape.comMajor incidentResolved2026-10-20 15:45 UTC
Public — what happened
Summary
Onshape said that file exports were delayed in all regions and that some users were being interrupted while modeling, and it classed the incident as major. The company reported that it had identified the problem at 14:15 UTC on 2026-10-20 and was working on a fix, with updates at 14:35 and 14:40 saying that work was continuing. At 15:08 UTC Onshape said a fix was in place and it was watching the results, and the incident was marked resolved at 15:45.
Affected
North America, Western Europe, Southeast Asia, Australia, Northeast Asia
Timeline
- Started — 2026-10-20 14:15 UTC
- Identified — 2026-10-20 14:15 UTC (3 updates)
- Monitoring — 2026-10-20 15:08 UTC
- Resolved — 2026-10-20 15:45 UTC · 1h 31m 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 Onshape 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 Onshape: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Onshape report →
More from Onshape
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.