Paperspace Outage History

Paperspace is up right now

Paperspace had 10 outages in the last 2 years totaling 590h 23m of downtime — averaging 0.4 incidents per month.

There were 10 Paperspace outages since May 30, 2025 totaling 590h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.paperspace.com

Minor May 8, 2026

Service Disruption Identified: CORE

Detected by Pingoru
May 08, 2026, 06:08 PM UTC
Resolved
May 08, 2026, 10:02 PM UTC
Duration
3h 54m
Affected: US (NY2)
Timeline · 4 updates
  1. 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.

  2. investigating May 08, 2026, 06:09 PM UTC

    We are currently investigating this issue.

  3. monitoring May 08, 2026, 07:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. 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.

Read the full incident report →

Major April 20, 2026

Degraded Performance: Core VM Start/Stop Delays and Internal Connectivity Issues

Detected by Pingoru
Apr 20, 2026, 03:32 PM UTC
Resolved
Apr 20, 2026, 05:32 PM UTC
Duration
2h
Affected: US (NY2)
Timeline · 3 updates
  1. investigating Apr 20, 2026, 03:32 PM UTC

    We are currently investigating this issue.

  2. identified Apr 20, 2026, 05:30 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 20, 2026, 05:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 18, 2026

GPU Instance Power-On Issues (NYC Region)

Detected by Pingoru
Apr 18, 2026, 03:00 PM UTC
Resolved
Apr 18, 2026, 05:19 PM UTC
Duration
2h 18m
Affected: US (NY2)
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Major January 16, 2026

Service Disruption Identified: Gradient

Detected by Pingoru
Jan 16, 2026, 10:27 AM UTC
Resolved
Jan 16, 2026, 04:21 PM UTC
Duration
5h 54m
Affected: Gradient
Timeline · 4 updates
  1. 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.

  2. 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.

  3. 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.

  4. resolved Jan 16, 2026, 04:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 5, 2025

Ticketing tool for the Paperspace affected

Detected by Pingoru
Dec 05, 2025, 09:23 AM UTC
Resolved
Dec 05, 2025, 10:19 AM UTC
Duration
56m
Affected: Console
Timeline · 4 updates
  1. 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.

  2. identified Dec 05, 2025, 09:30 AM UTC

    The issue has been identified, a fix has been implemented and everything is operational now.

  3. monitoring Dec 05, 2025, 09:31 AM UTC

    A fix has been implemented and we're monitoring the results. Thanks for your patience.

  4. resolved Dec 05, 2025, 10:19 AM UTC

    This incident has been resolved. Thank you everyone.

Read the full incident report →

Critical December 1, 2025

Service Disruption Identified: CORE AMS

Detected by Pingoru
Dec 01, 2025, 12:04 AM UTC
Resolved
Dec 02, 2025, 02:30 AM UTC
Duration
1d 2h
Affected: Europe (AMS1)
Timeline · 8 updates
  1. 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.

  2. identified Dec 01, 2025, 12:04 AM UTC

    The issue has been identified and a fix is being implemented.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. monitoring Dec 01, 2025, 07:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. 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.

Read the full incident report →

Major October 3, 2025

Core machine inaccesssible

Detected by Pingoru
Oct 03, 2025, 08:44 AM UTC
Resolved
Oct 04, 2025, 11:40 PM UTC
Duration
1d 14h
Affected: US (NY2)
Timeline · 7 updates
  1. 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.

  2. 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.

  3. identified Oct 03, 2025, 12:18 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Oct 03, 2025, 02:35 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Oct 03, 2025, 05:10 PM UTC

    We are continuing to work on a fix for this issue.

  6. monitoring Oct 03, 2025, 09:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Oct 04, 2025, 11:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2025

Service Disruption: Single Sign-On (SSO)

Detected by Pingoru
Aug 28, 2025, 12:46 PM UTC
Resolved
Aug 28, 2025, 03:53 PM UTC
Duration
3h 6m
Affected: Desktop App & StreamingConsole
Timeline · 6 updates
  1. 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.

  2. investigating Aug 28, 2025, 12:47 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 28, 2025, 02:07 PM UTC

    We are continuing to investigate this issue.

  4. identified Aug 28, 2025, 02:08 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Aug 28, 2025, 02:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Aug 28, 2025, 03:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 30, 2025

Service Disruption: Paperspace Console

Detected by Pingoru
May 30, 2025, 06:12 AM UTC
Resolved
May 30, 2025, 07:37 AM UTC
Duration
1h 24m
Affected: Console
Timeline · 2 updates
  1. investigating May 30, 2025, 06:12 AM UTC

    We are currently investigating an issue that is preventing users from accessing the Paperspace console. Our team is working to resolve the issue as quickly as possible. We apologize for any inconvenience and will provide updates as we progress.

  2. resolved May 30, 2025, 07:37 AM UTC

    The issue was identified as affecting only a specific cohort of users. We have verified that all the systems including the Paperspace Console are operating as expected. Any remaining access concerns will be handled on case-by-case basis. We appreciate your patience and understanding.

Read the full incident report →