Incidentsby GlyphService Disruption Identified: Users may experience issues with CORE Virtual Machines in the AMS Region.
May 30, 07:41 UTCMay 30, 14:18 UTC
Duration
6h 37m
Impact
Major
Root cause
Not disclosed
Paperspace, 90 days
2 incidents
Affected
Europe (AMS1)
Final update
The issue has been resolved by our engineers. We apologize for any inconvenience caused. If you continue to experience issues, please contact our Support Team.
Timeline
- Resolved · May 30, 14:18 UTC
The issue has been resolved by our engineers. We apologize for any inconvenience caused. If you continue to experience issues, please contact our Support Team.
- Monitoring · May 30, 13:47 UTC
Our engineers have addressed the issue. Most users should be able to use their CORE Virtual Machines in the AMS1 Region. If you continue to experience issues, please reach out to our Support Team.
- Monitoring · May 30, 10:58 UTC
Our engineers have addressed the issue. Most users should be able to use their CORE Virtual Machines in the AMS1 Region. If you continue to experience issues, please reach out to our Support Team.
- Identified · May 30, 07:41 UTC
Our engineers have identified a potential electrical issue that may be impacting users of the AMS Region CORE Virtual Machine and are currently in the process of rectifying it. We apologize for any inconvenience this has caused you.
More from Paperspace
Full historyGradient Notebooks Stuck in Pending State - Recovery Underwaylasted 1h 18mService Disruption: Paperspace Consolelasted 1h 4mService Disruption Identified: CORE CA1lasted 3h 34mService Disruption Identified: CORElasted 3h 54mDegraded Performance: Core VM Start/Stop Delays and Internal Connectivity Issueslasted 2h 1mGPU Instance Power-On Issues (NYC Region)lasted 2h 18m