- Detected by Pingoru
- May 26, 2026, 01:30 AM UTC
- Resolved
- May 26, 2026, 05:04 AM UTC
- Duration
- 3h 34m
Affected: US (CA1)
Timeline · 3 updates
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- Detected by Pingoru
- Dec 26, 2025, 02:55 PM UTC
- Resolved
- Jan 16, 2026, 04:21 PM UTC
- Duration
- 21d 1h
Affected: US (NY2)Gradient
Timeline · 9 updates
Read the full incident report →
- 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
-
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.
Read the full incident report →
Critical December 1, 2025 - 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
-
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 →
- Detected by Pingoru
- Feb 24, 2025, 07:24 AM UTC
- Resolved
- Feb 24, 2025, 11:24 AM UTC
- Duration
- 3h 59m
Affected: US (NY2)
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2025, 08:08 PM UTC
- Resolved
- Feb 06, 2025, 09:02 PM UTC
- Duration
- 54m
Affected: APIConsole
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jan 24, 2025, 08:30 PM UTC
- Resolved
- Jan 24, 2025, 11:33 PM UTC
- Duration
- 3h 3m
Affected: US (NY2)Gradient
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Dec 21, 2024, 02:40 AM UTC
- Resolved
- Dec 21, 2024, 04:55 AM UTC
- Duration
- 2h 15m
Affected: Desktop App & StreamingConsole
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Nov 09, 2024, 07:26 PM UTC
- Resolved
- Nov 11, 2024, 04:53 AM UTC
- Duration
- 1d 9h
Affected: US (CA1)Desktop App & Streaming
Timeline · 8 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Sep 28, 2024, 08:00 AM UTC
- Resolved
- Sep 28, 2024, 09:23 AM UTC
- Duration
- 1h 22m
Affected: US (NY2)
Timeline · 5 updates
-
investigating Sep 28, 2024, 08:00 AM UTC
We are investigating a Network Issue that's affecting our Bare-Metal users in the NY Region. We apologize for the inconvenience.
-
identified Sep 28, 2024, 08:11 AM UTC
Our engineers have identified a networking issue affecting Paperspace Bare-Metal services caused by our upstream provided. Our network team is actively working with our upstream provider to mitigate the issue. Further updates will be provided as we implement corrective measures.
-
monitoring Sep 28, 2024, 08:31 AM UTC
A fix has been implemented and we're monitoring the results. Thank you for your patience and cooperation.
-
monitoring Sep 28, 2024, 08:32 AM UTC
Our engineers implemented a fix and we're monitoring the situation. If you're still experiencing issues, please contact our Support Team.
-
resolved Sep 28, 2024, 09:23 AM UTC
This issue has been resolved now. Thank you for your patience and cooperation.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2024, 04:16 AM UTC
- Resolved
- Sep 18, 2024, 06:38 AM UTC
- Duration
- 2h 21m
Affected: US (CA1)
Timeline · 3 updates
-
investigating Sep 18, 2024, 04:16 AM UTC
We are currently investigating an issue that is preventing CORE machines in CA1 from processing events. Our engineers are working on a fix. We apologize for any inconvenience caused.
-
monitoring Sep 18, 2024, 06:13 AM UTC
Our engineers have implemented a fix and events should start processing as usual. Customers that still experience issues, please wait a few minutes and try again or contact our Support Team.
-
resolved Sep 18, 2024, 06:38 AM UTC
Our engineers have resolved the issue. Please contact our Support Team if you encounter any problems with your CA1 CORE Virtual Machine.
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2024, 09:02 AM UTC
- Resolved
- Jul 13, 2024, 11:00 AM UTC
- Duration
- 1h 58m
Affected: GradientConsole
Timeline · 6 updates
-
investigating Jul 13, 2024, 07:29 AM UTC
We're investigating an issue where users aren't able to interact with the Paperspace Console and other Paperspace Services. We apologize for any inconvenience caused.
-
identified Jul 13, 2024, 08:05 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Jul 13, 2024, 08:06 AM UTC
Our engineers have identified the issue and are working on a fix for this issue. We apologize for the inconvenience caused.
-
monitoring Jul 13, 2024, 09:02 AM UTC
Our engineering team has implemented a fix and we are monitoring the results. We appreciate your patience and cooperation.
-
monitoring Jul 13, 2024, 10:44 AM UTC
We are continuing to monitor for any further issues. We appreciate your patience and cooperation.
-
resolved Jul 13, 2024, 11:00 AM UTC
This incident has been resolved. Thank you for your patience and cooperation.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2024, 09:14 PM UTC
- Resolved
- Jul 10, 2024, 12:40 AM UTC
- Duration
- 3h 25m
Affected: US (NY2)Gradient
Timeline · 3 updates
-
investigating Jul 09, 2024, 09:14 PM UTC
Several reports have been done regarding machines not being accessible on both Core and Gradient, we are investigating the root cause of this issue, and your patience is appreciated.
-
monitoring Jul 09, 2024, 11:17 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 10, 2024, 12:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2024, 02:02 PM UTC
- Resolved
- Jul 08, 2024, 03:28 PM UTC
- Duration
- 1h 26m
Affected: Console
Timeline · 4 updates
-
investigating Jul 08, 2024, 02:02 PM UTC
We are currently investigating an issue that is preventing news users and teams from accessing the billing page.
-
identified Jul 08, 2024, 02:14 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 08, 2024, 02:35 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 08, 2024, 03:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2024, 06:00 AM UTC
- Resolved
- Jul 08, 2024, 08:33 AM UTC
- Duration
- 2h 33m
Affected: US (NY2)
Timeline · 3 updates
-
investigating Jul 08, 2024, 06:00 AM UTC
Our engineers are investigating an issue that prevents NY2 Region users from interacting with their Virtual Machines. We apologize for the inconvenience.
-
monitoring Jul 08, 2024, 08:10 AM UTC
Our engineers implemented a fix and we're monitoring the situation. Users should be able to interact with their VMs as normal. If you experience any issues, please contact our Support Team.
-
resolved Jul 08, 2024, 08:33 AM UTC
The issue has been resolved. If you experience any problems, please contact our Support Team.
Read the full incident report →
- Detected by Pingoru
- Jul 05, 2024, 05:38 AM UTC
- Resolved
- Jul 05, 2024, 08:29 AM UTC
- Duration
- 2h 51m
Affected: US (NY2)Gradient
Timeline · 3 updates
-
investigating Jul 05, 2024, 05:38 AM UTC
We are currently investigating an issue that is preventing users from interacting with Gradient notebooks. We apologize for the inconvenience caused.
-
monitoring Jul 05, 2024, 08:07 AM UTC
Our engineers have implemented a fix. Users should be able to access Gradient assets as normal. If you experience any problems, please contact our Support Team.
-
resolved Jul 05, 2024, 08:29 AM UTC
The incident was resolved by our engineers. If you continue to experience issues, please contact our Support Team.
Read the full incident report →
- Detected by Pingoru
- Jul 04, 2024, 07:18 AM UTC
- Resolved
- Jul 04, 2024, 09:07 AM UTC
- Duration
- 1h 49m
Affected: US (NY2)Gradient
Timeline · 4 updates
-
investigating Jul 04, 2024, 07:18 AM UTC
We're investigating a possible network issue that's affecting CORE and Gradient services in the NY2 Region. We apologize for the inconvenience experienced.
-
identified Jul 04, 2024, 07:32 AM UTC
Our engineers are currently working on a fix. We appreciate your patience.
-
monitoring Jul 04, 2024, 08:23 AM UTC
Our engineers have implemented a fix and we're monitoring the situation. If you continue to experience issues, please let us know.
-
resolved Jul 04, 2024, 09:07 AM UTC
The issue affecting both CORE and Gradient users in the NY2 Region has been resolved. If you continue to experience problems, please contact our Support Team.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2024, 07:00 PM UTC
- Resolved
- Jun 27, 2024, 10:00 PM UTC
- Duration
- 3h
Affected: US (NY2)US (CA1)Gradient
Timeline · 5 updates
-
identified Jun 27, 2024, 07:55 PM UTC
Our engineers have identified generalized issues with the network connectivity, we are working on a solution to ensure connectivity to all our users. We appreciate your patience.
-
identified Jun 27, 2024, 08:14 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Jun 27, 2024, 08:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 27, 2024, 08:35 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 27, 2024, 10:00 PM UTC
This incident has been resolved.
Read the full incident report →