Historial de interrupciones de Paperspace

1. August 26, 2026 at 10:46 AM UTCinvestigating

   Actualmente estamos investigando un problema que está impidiendo a los usuarios acceder o acceder a la Consola Paperspace. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y gracias por su paciencia y comprensión.

2. August 26, 2026 at 11:41 AM UTCmonitoring

   Nuestro equipo de Ingeniería ha resuelto el problema que impidió a los usuarios acceder o acceder a la Consola Paperspace, y actualmente estamos monitoreando los resultados. Nos disculpamos por cualquier inconveniente que esto pueda haber causado y gracias por su paciencia y comprensión.

3. August 26, 2026 at 11:50 AM UTCresolved

   Nuestro equipo de ingeniería ha confirmado que se ha resuelto la cuestión que impide a los usuarios acceder o acceder a la consola Paperspace, y el servicio ha sido totalmente restaurado. Gracias por su paciencia y comprensión durante todo este incidente. Si continúas experimentando cualquier problema, por favor contacta con nuestro equipo de soporte, y estaremos encantados de ayudarte más.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 26, 2026 at 3:11 AM UTCinvestigating

   We are currently investigating an issue preventing users from interacting with Core Virtual Machines in the CA1 Region.

2. May 26, 2026 at 3:25 AM UTCmonitoring

   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.

3. May 26, 2026 at 5:04 AM UTCresolved

   This incident has been resolved now.

1. May 8, 2026 at 6:08 PM UTCidentified

   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. May 8, 2026 at 6:09 PM UTCinvestigating

   We are currently investigating this issue.

3. May 8, 2026 at 7:55 PM UTCmonitoring

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

4. May 8, 2026 at 10:02 PM UTCresolved

   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.

1. April 20, 2026 at 3:32 PM UTCinvestigating

   We are currently investigating this issue.

2. April 20, 2026 at 5:30 PM UTCidentified

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

3. April 20, 2026 at 5:32 PM UTCresolved

   This incident has been resolved.

1. April 18, 2026 at 3:00 PM UTCinvestigating

   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. April 18, 2026 at 5:19 PM UTCresolved

   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.

1. January 16, 2026 at 10:27 AM UTCinvestigating

   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. January 16, 2026 at 12:20 PM UTCidentified

   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. January 16, 2026 at 4:20 PM UTCmonitoring

   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. January 16, 2026 at 4:21 PM UTCresolved

   This incident has been resolved.

1. January 16, 2026 at 10:09 AM UTCidentified

   We've identified an ongoing issue impacting Core Machines. 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. January 16, 2026 at 12:48 PM UTCresolved

   This incident has been resolved. The core VMs should be working as intended. Thanks for your cooperation.

1. December 26, 2025 at 2:55 PM UTCinvestigating

   We are currently investigating a network disruption that is preventing users from interacting with Gradient notebooks.

2. December 26, 2025 at 3:38 PM UTCidentified

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

3. December 26, 2025 at 7:55 PM UTCidentified

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

4. December 26, 2025 at 9:27 PM UTCmonitoring

   A fix has been deployed. Users should be able to create and interact with their notebooks normally. Awaiting confirmation before closure.

5. December 27, 2025 at 7:50 AM UTCinvestigating

   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.

6. December 27, 2025 at 4:12 PM UTCinvestigating

   We are continuing to investigate this issue.

7. December 27, 2025 at 8:46 PM UTCmonitoring

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

8. January 16, 2026 at 4:21 PM UTCresolved

   This incident has been resolved.

1. December 10, 2025 at 6:00 AM UTCidentified

   We have identified a service disruption affecting all resources in the CA1 region. Our team is working to restore services as quickly as possible. Users may be unable to access their Core VMs during this time. Further updates will be provided as recovery progresses.

2. December 10, 2025 at 7:06 AM UTCmonitoring

   Our teams have applied a fix and connectivity in the CA1 region is returning to normal. We are monitoring the environment to confirm full recovery.

3. December 10, 2025 at 8:05 AM UTCresolved

   This incident has been resolved. The core machines should be working as intended. Thank you for your patience and cooperation.

1. December 5, 2025 at 9:23 AM UTCinvestigating

   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. December 5, 2025 at 9:30 AM UTCidentified

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

3. December 5, 2025 at 9:31 AM UTCmonitoring

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

4. December 5, 2025 at 10:19 AM UTCresolved

   This incident has been resolved. Thank you everyone.

1. December 1, 2025 at 12:04 AM UTCinvestigating

   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. December 1, 2025 at 12:04 AM UTCidentified

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

3. December 1, 2025 at 3:44 AM UTCidentified

   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. December 1, 2025 at 6:50 AM UTCmonitoring

   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. December 1, 2025 at 12:07 PM UTCidentified

   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. December 1, 2025 at 2:56 PM UTCidentified

   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. December 1, 2025 at 7:53 PM UTCmonitoring

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

8. December 2, 2025 at 2:30 AM UTCresolved

   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.

1. October 24, 2025 at 2:06 AM UTCinvestigating

   We are currently investigating a network issue that is preventing users from interacting with Gradient notebooks.

2. October 24, 2025 at 2:57 AM UTCmonitoring

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

3. October 24, 2025 at 3:54 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. October 24, 2025 at 3:54 AM UTCresolved

   This incident has been resolved.

1. October 3, 2025 at 8:44 AM UTCinvestigating

   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. October 3, 2025 at 9:13 AM UTCidentified

   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. October 3, 2025 at 5:10 PM UTCidentified

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

4. October 3, 2025 at 9:31 PM UTCmonitoring

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

5. October 4, 2025 at 11:40 PM UTCresolved

   This incident has been resolved.

1. August 28, 2025 at 12:46 PM UTCinvestigating

   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. August 28, 2025 at 2:07 PM UTCinvestigating

   We are continuing to investigate this issue.

3. August 28, 2025 at 2:08 PM UTCidentified

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

4. August 28, 2025 at 2:33 PM UTCmonitoring

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

5. August 28, 2025 at 3:53 PM UTCresolved

   This incident has been resolved.

1. May 30, 2025 at 6:12 AM UTCinvestigating

   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. May 30, 2025 at 7:37 AM UTCresolved

   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.

1. February 24, 2025 at 7:24 AM UTCinvestigating

   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.

2. February 24, 2025 at 9:33 AM UTCidentified

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

3. February 24, 2025 at 9:39 AM UTCmonitoring

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

4. February 24, 2025 at 11:24 AM UTCresolved

   This incident has been resolved.

1. February 6, 2025 at 8:08 PM UTCinvestigating

   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.

2. February 6, 2025 at 8:33 PM UTCmonitoring

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

3. February 6, 2025 at 9:02 PM UTCresolved

   This incident has been resolved.

1. January 25, 2025 at 9:16 PM UTCidentified

   We've identified the issue and are working on a fix. Some users might still experience issues while we are implementing the fix.

2. January 25, 2025 at 10:27 PM UTCidentified

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

3. January 25, 2025 at 11:22 PM UTCmonitoring

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

4. January 26, 2025 at 4:01 AM UTCresolved

   This incident has been resolved.

1. January 24, 2025 at 9:36 PM UTCinvestigating

   We are currently investigating a network issue that is preventing users from interacting with Gradient notebooks and Core VMs.

2. January 24, 2025 at 9:37 PM UTCinvestigating

   We are continuing to investigate this issue.

3. January 24, 2025 at 9:37 PM UTCidentified

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

4. January 24, 2025 at 10:12 PM UTCmonitoring

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

5. January 24, 2025 at 11:33 PM UTCresolved

   This incident has been resolved.

1. December 21, 2024 at 2:40 AM UTCinvestigating

   We are currently investigating an issue that is preventing users from logging into their Paperspace account. We apologize for the inconvenience caused.

2. December 21, 2024 at 3:45 AM UTCinvestigating

   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.

3. December 21, 2024 at 4:13 AM UTCidentified

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

4. December 21, 2024 at 4:15 AM UTCmonitoring

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

5. December 21, 2024 at 4:55 AM UTCresolved

   This incident has been resolved. Thank you for your patience and cooperation.