Paperspace Outage History
Paperspace is up right nowPingoru has recorded 50 incidents for Paperspace: 12 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 4 of 720 (1%) |
| May 2026 | 2 | 8 of 744 (1%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 527 (0%) |
Incidents, newest first
Critical August 26, 2026 Service Disruption: Paperspace Console 1h 3m Console
Started Aug 26, 2026, 10:46 AM UTC· resolved Aug 26, 2026, 11:50 AM UTC
- investigating Aug 26, 2026, 10:46 AM UTC
We are currently investigating an issue that is preventing users from accessing or logging in to the Paperspace Console. We apologize for any inconvenience this may have caused and thank you for your patience and understanding.
- monitoring Aug 26, 2026, 11:41 AM UTC
Our Engineering team has resolved the issue that was preventing users from accessing or logging in to the Paperspace Console, and we are currently monitoring the results. We apologize for any inconvenience this may have caused and thank you for your patience and understanding.
- resolved Aug 26, 2026, 11:50 AM UTC
Our Engineering team has confirmed that the issue preventing users from accessing or logging in to the Paperspace Console has been resolved, and the service has been fully restored. Thank you for your patience and understanding throughout this incident. If you continue to experience any issues, please reach out to our Support team, and we will be happy to assist you further.
Major May 26, 2026 Service Disruption Identified: CORE CA1 3h 34m US (CA1)
Started May 26, 2026, 01:30 AM UTC· resolved May 26, 2026, 05:04 AM UTC
- investigating May 26, 2026, 03:11 AM UTC
We are currently investigating an issue preventing users from interacting with Core Virtual Machines in the CA1 Region.
- monitoring May 26, 2026, 03:25 AM UTC
We've identified and implemented a fix for the issue and are monitoring the results. Some users might still experience issues as we continue working on this.
- resolved May 26, 2026, 05:04 AM UTC
This incident has been resolved now.
Minor May 8, 2026 Service Disruption Identified: CORE 3h 54m US (NY2)
Started May 08, 2026, 06:08 PM UTC· resolved May 08, 2026, 10:02 PM UTC
- identified May 08, 2026, 06:08 PM UTC
As of 14:30 UTC, our Engineering team is investigating reports of network connectivity issues impacting a small subset of customer VMs in NY2 region. Users may experience intermittent connectivity issues. We apologize for the inconvenience and will share an update once we have more information.
- investigating May 08, 2026, 06:09 PM UTC
We are currently investigating this issue.
- monitoring May 08, 2026, 07:55 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2026, 10:02 PM UTC
Our Engineering team has resolved the incident with intermittent connectivity issues affecting a few Core VMs in the NY2 data center. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.
Major April 20, 2026 Degraded Performance: Core VM Start/Stop Delays and Internal Connectivity Issues 2h US (NY2)
Started Apr 20, 2026, 03:32 PM UTC· resolved Apr 20, 2026, 05:32 PM UTC
- investigating Apr 20, 2026, 03:32 PM UTC
We are currently investigating this issue.
- identified Apr 20, 2026, 05:30 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 20, 2026, 05:32 PM UTC
This incident has been resolved.
Major April 18, 2026 GPU Instance Power-On Issues (NYC Region) 2h 18m US (NY2)
Started Apr 18, 2026, 03:00 PM UTC· resolved Apr 18, 2026, 05:19 PM UTC
- investigating Apr 18, 2026, 03:00 PM UTC
We are currently investigating an issue affecting a subset of GPU instances in the NYC region. Customers using P5000, P6000, and RTX5000 instances may experience difficulties when attempting to power on these resources. Our engineering team is actively working to identify the root cause and implement a resolution. In the meantime, impacted customers may encounter delays or failures when starting affected instances. We will continue to provide updates as more information becomes available. Thank you for your patience and understanding.
- resolved Apr 18, 2026, 05:19 PM UTC
The issue affecting a subset of GPU instances in the NYC region has been resolved. Customers using P5000, P6000, and RTX5000 instances may have previously experienced difficulties when attempting to power on these resources. Importantly, this issue had no impact on running instances, only power-on actions were affected. Our engineering team has implemented a fix and is continuing to monitor the environment to ensure stability.
Major January 16, 2026 Service Disruption Identified: Gradient 5h 54m Gradient
Started Jan 16, 2026, 10:27 AM UTC· resolved Jan 16, 2026, 04:21 PM UTC
- investigating Jan 16, 2026, 10:27 AM UTC
Our engineering team is investigating reports of service disruption impacting Gradient notebooks. At this point, users may experience intermittent issues with their notebooks. We apologize for the inconvenience and appreciate your patience and cooperation as we work to resolve the issue. Our engineers are actively investigating the cause and working towards a solution. We will share an update once we have further details.
- identified Jan 16, 2026, 12:20 PM UTC
Our Engineering team has identified the cause of the service disruption impacting Gradient notebooks and is actively working on a fix. At this time, users may continue to experience intermittent issues with their notebooks. Our team is implementing a solution to resolve the issue as soon as possible. We will provide another update once the fix is deployed and the service is restored.
- monitoring Jan 16, 2026, 04:20 PM UTC
A fix has been implemented and the service has been fully restored. Our engineering team has resolved the issue, and we are actively monitoring the system to ensure continued stability.
- resolved Jan 16, 2026, 04:21 PM UTC
This incident has been resolved.
Major December 26, 2025 Service Disruption: Gradient 21d 1h US (NY2), Gradient
Started Dec 26, 2025, 02:55 PM UTC· resolved Jan 16, 2026, 04:21 PM UTC
- investigating Dec 26, 2025, 02:55 PM UTC
We are currently investigating a network disruption that is preventing users from interacting with Gradient notebooks.
- identified Dec 26, 2025, 03:38 PM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 26, 2025, 05:10 PM UTC
We are continuing to work on a fix for this issue.
- identified Dec 26, 2025, 07:55 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Dec 26, 2025, 09:27 PM UTC
A fix has been deployed. Users should be able to create and interact with their notebooks normally. Awaiting confirmation before closure.
- investigating Dec 27, 2025, 07:50 AM UTC
We are currently investigating a network disruption that is preventing users from interacting with Gradient notebooks. Our engineers are working on resolution of the Gradient notebooks' unavailability.
- investigating Dec 27, 2025, 04:12 PM UTC
We are continuing to investigate this issue.
- monitoring Dec 27, 2025, 08:46 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 16, 2026, 04:21 PM UTC
This incident has been resolved.
Notice December 5, 2025 Ticketing tool for the Paperspace affected 56m Console
Started Dec 05, 2025, 09:23 AM UTC· resolved Dec 05, 2025, 10:19 AM UTC
- investigating Dec 05, 2025, 09:23 AM UTC
We are currently experiencing an outage affecting the Paperspace main website (paperspace.com). At this time, the Paperspace Console remains fully operational and can be accessed directly at: https://console.paperspace.com In addition, our ticketing system is encountering delays, which may impact our ability to respond as quickly as usual. Our Support team is actively monitoring the situation and will reply as soon as the system stabilizes. We will continue to provide updates as we work to restore full functionality. Thank you for your patience and understanding.
- identified Dec 05, 2025, 09:30 AM UTC
The issue has been identified, a fix has been implemented and everything is operational now.
- monitoring Dec 05, 2025, 09:31 AM UTC
A fix has been implemented and we're monitoring the results. Thanks for your patience.
- resolved Dec 05, 2025, 10:19 AM UTC
This incident has been resolved. Thank you everyone.
Critical December 1, 2025 Service Disruption Identified: CORE AMS 1d 2h Europe (AMS1)
Started Dec 01, 2025, 12:04 AM UTC· resolved Dec 02, 2025, 02:30 AM UTC
- investigating Dec 01, 2025, 12:04 AM UTC
We have identified a service disruption affecting our AMS region due to a power issue. Our team is working diligently to resolve this matter as quickly as possible. In the meantime, users may experience issues with their Core Products.
- identified Dec 01, 2025, 12:04 AM UTC
The issue has been identified and a fix is being implemented.
- identified Dec 01, 2025, 03:44 AM UTC
Update on Paperspace AMS Region Outage Our teams continue to work on recovering Paperspace services in the AMS region. Some customers may see improvements in bringing up their instances. We'll provide further updates as progress is made.
- monitoring Dec 01, 2025, 06:50 AM UTC
The AMS region is now operational, but some users may experience slow performance as systems stabilize. Our team is monitoring the recovery and working to restore full functionality.
- identified Dec 01, 2025, 12:07 PM UTC
The AMS region is operating in a partially degraded state. While some services are accessible, others remain unavailable for certain customers. We have identified the issue and our engineers are actively working on recovery. We’ll provide further updates as progress continues.
- identified Dec 01, 2025, 02:56 PM UTC
Our engineers are continuing to work on restoring full functionality in the AMS region. While some services remain partially unavailable for certain customers, recovery efforts are actively ongoing. We will provide further updates as progress continues.
- monitoring Dec 01, 2025, 07:53 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 02, 2025, 02:30 AM UTC
The incident in the AMS region has been fully resolved, and all services are now available. If you experience any further issues, please don't hesitate to contact our support team for assistance.
Major October 3, 2025 Core machine inaccesssible 1d 14h US (NY2)
Started Oct 03, 2025, 08:44 AM UTC· resolved Oct 04, 2025, 11:40 PM UTC
- investigating Oct 03, 2025, 08:44 AM 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.
- identified Oct 03, 2025, 09:13 AM 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.
- identified Oct 03, 2025, 12:18 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 03, 2025, 02:35 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 03, 2025, 05:10 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 03, 2025, 09:31 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 04, 2025, 11:40 PM UTC
This incident has been resolved.
Minor August 28, 2025 Service Disruption: Single Sign-On (SSO) 3h 6m Desktop App & Streaming, Console
Started Aug 28, 2025, 12:46 PM UTC· resolved Aug 28, 2025, 03:53 PM UTC
- investigating Aug 28, 2025, 12:46 PM UTC
We are currently investigating customers being unable to log in using Single Sign-On (SSO). Standard login methods remain available. Our engineering team is actively working to restore full functionality, and we will share updates as they become available.
- investigating Aug 28, 2025, 12:47 PM UTC
We are continuing to investigate this issue.
- investigating Aug 28, 2025, 02:07 PM UTC
We are continuing to investigate this issue.
- identified Aug 28, 2025, 02:08 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 28, 2025, 02:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 28, 2025, 03:53 PM UTC
This incident has been resolved.
Minor February 24, 2025 Service Disruption: CORE VMs in NY2 3h 59m US (NY2)
Started Feb 24, 2025, 07:24 AM UTC· resolved Feb 24, 2025, 11:24 AM UTC
- investigating Feb 24, 2025, 07:24 AM UTC
We are investigating an issue affecting Core VMs in the NY2 region, which may cause accessibility issues. Our team is working to resolve the issue as quickly as possible. We apologize for any inconvenience and will provide updates as we progress.
- identified Feb 24, 2025, 09:33 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Feb 24, 2025, 09:39 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 24, 2025, 11:24 AM UTC
This incident has been resolved.
Minor February 6, 2025 API degraded performance and console access issues 54m API, Console
Started Feb 06, 2025, 08:08 PM UTC· resolved Feb 06, 2025, 09:02 PM UTC
- investigating Feb 06, 2025, 08:08 PM UTC
We are seeing that our API is having degraded performance, also, access to the Paperspace Console might be intermittent. Our engineers are investigating the root cause. We appreciate your patience.
- monitoring Feb 06, 2025, 08:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 06, 2025, 09:02 PM UTC
This incident has been resolved.
Major January 24, 2025 Service Disruption: Gradient and Core 3h 3m US (NY2), Gradient
Started Jan 24, 2025, 08:30 PM UTC· resolved Jan 24, 2025, 11:33 PM UTC
- investigating Jan 24, 2025, 09:36 PM UTC
We are currently investigating a network issue that is preventing users from interacting with Gradient notebooks and Core VMs.
- investigating Jan 24, 2025, 09:37 PM UTC
We are continuing to investigate this issue.
- identified Jan 24, 2025, 09:37 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 24, 2025, 10:12 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 24, 2025, 11:33 PM UTC
This incident has been resolved.
Major December 21, 2024 Service Disruption: Console UI 2h 15m Desktop App & Streaming, Console
Started Dec 21, 2024, 02:40 AM UTC· resolved Dec 21, 2024, 04:55 AM UTC
- investigating Dec 21, 2024, 02:40 AM UTC
We are currently investigating an issue that is preventing users from logging into their Paperspace account. We apologize for the inconvenience caused.
- investigating Dec 21, 2024, 03:45 AM UTC
We are continuing to investigate the issue preventing users from logging into their Paperspace accounts. We sincerely apologize for the inconvenience this has caused and appreciate your patience as we work toward a resolution.
- identified Dec 21, 2024, 04:13 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Dec 21, 2024, 04:15 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 21, 2024, 04:55 AM UTC
This incident has been resolved. Thank you for your patience and cooperation.
Major November 9, 2024 Service Disruption: CORE 1d 9h US (CA1), Desktop App & Streaming
Started Nov 09, 2024, 07:26 PM UTC· resolved Nov 11, 2024, 04:53 AM UTC
- investigating Nov 09, 2024, 07:26 PM UTC
We are currently investigating an issue that is preventing users from interacting with their CORE machines in CA1. Our engineers are working on a fix. We apologize for any inconvenience caused.
- identified Nov 09, 2024, 08:03 PM UTC
The issue has been identified and a fix is being implemented.
- identified Nov 09, 2024, 08:45 PM UTC
We are continuing to work on a fix for the issue. We apologize for any inconvenience caused.
- identified Nov 10, 2024, 02:04 AM UTC
We are continuing to work on a fix for this issue.
- identified Nov 10, 2024, 09:13 AM UTC
Our engineers have identified the issue and are actively working on implementing a fix. We appreciate your patience as we work to resolve this issue.
- monitoring Nov 10, 2024, 10:07 PM UTC
Our engineers have implemented a solution and we are currently monitoring the results.
- monitoring Nov 11, 2024, 12:13 AM UTC
We are continuing to monitor for any further issues.
- resolved Nov 11, 2024, 04:53 AM UTC
Our engineers have applied a fix and the issue is considered resolved. If you continue to experience problems, please contact our Support Team. We apologize for the inconvenience experienced.