Core machine inaccesssible
Oct 3, 08:44 UTCOct 4, 23:40 UTC
Duration
38h 57m
Impact
Major
Root cause
Not disclosed
Paperspace, 90 days
2 incidents
Affected
US (NY2)
Final update
This incident has been resolved.
Timeline
- Resolved · Oct 4, 23:40 UTC
This incident has been resolved.
- Monitoring · Oct 3, 21:31 UTC
A fix has been implemented and we are monitoring the results.
- Identified · Oct 3, 17:10 UTC
We are continuing to work on a fix for this issue.
- Identified · Oct 3, 14:35 UTC
We are continuing to work on a fix for this issue.
- Identified · Oct 3, 12:18 UTC
We are continuing to work on a fix for this issue.
- Identified · Oct 3, 09:13 UTC
We’re currently investigating an issue affecting Core Machines. Our engineers are actively looking into the root cause to restore full functionality as quickly as possible. Thank you for your patience while we work on this, and we’ll share updates as soon as we have more details.
- Investigating · Oct 3, 08:44 UTC
We've identified an ongoing issue impacting Core Machines in NY2. Our engineering team is actively investigating the root cause and working diligently toward a resolution. We understand how disruptive this may be and sincerely apologize for the inconvenience. Please rest assured that resolving this remains a top priority, and we’ll keep you updated with progress as soon as more information becomes available.
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