Shapr3D Outage History
7 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Shapr3D Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 1, 2026 | Temporary elevated errors in user, team and subscription managementThe system is recovering automatically without any side effects. | 0 min | Resolved |
| Aug 8, 2026 | App to web redirects may fail to log in usersThis incident has been resolved. | 3h 24m | Resolved |
| Jul 26, 2026 | Apple App Store Outage Impacting SubscriptionsApple has resolved the outage affecting their App Store transaction and receipt validation services. All purchasing and subscription synchronization systems are back up and operating normally. | 1h 27m | Resolved |
| Jul 16, 2026 | Elevated SSO login errorsThe upstream third-party service provider has resolved their outage, and SSO login functionality is now fully restored. | 3h 13m | Resolved |
| Jun 24, 2026 | Sync IssuesThe system is recovering as planned with the rollout of the fix. As no further related issued have been identified we consider the current incident affecting our sync service solved. | 165h 55m | Resolved |
| May 18, 2026 | Partial outage in the Checkout flowThe 3rd party provider has successfully restored their service and now checkout works again. | 9 min | Resolved |
| Feb 23, 2026 | Planned database maintenanceThe scheduled database maintenance is now complete and all Cloud services are fully operational. Thank you for your patience! | 30 min | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Shapr3D incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Shapr3D Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Shapr3D acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Shapr3D outage in this window ran 6d 21h, against a mean recovery of 1d. If you depend on Shapr3D in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.