Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Paperspace

    51 incidentes de Paperspace registrados desde marzo de 2024, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Disrupción de servicio: Consola de espacio papel

    Comenzó 26 de agosto de 2026 a las 10:46 UTC · 1h 4m

    OutageIncidente crítico
    Componentes afectados
    Console
    1. 26 de agosto de 2026 a las 10:46 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. 26 de agosto de 2026 a las 11:41 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. 26 de agosto de 2026 a las 11:50 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.

    Service Disruption Identified: CORE CA1

    Comenzó 26 de mayo de 2026 a las 1:30 UTC · 3h 34m

    OutageIncidente mayor
    Componentes afectados
    US (CA1)
    1. 26 de mayo de 2026 a las 3:11 UTCinvestigating

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

    2. 26 de mayo de 2026 a las 3:25 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. 26 de mayo de 2026 a las 5:04 UTCresolved

      This incident has been resolved now.

    Service Disruption Identified: CORE

    Comenzó 8 de mayo de 2026 a las 18:08 UTC · 3h 54m

    IssuesIncidente menor
    Componentes afectados
    US (NY2)
    1. 8 de mayo de 2026 a las 18:08 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. 8 de mayo de 2026 a las 18:09 UTCinvestigating

      We are currently investigating this issue.

    3. 8 de mayo de 2026 a las 19:55 UTCmonitoring

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

    4. 8 de mayo de 2026 a las 22:02 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.

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

    Comenzó 20 de abril de 2026 a las 15:32 UTC · 2h 1m

    OutageIncidente mayor
    Componentes afectados
    US (NY2)
    1. 20 de abril de 2026 a las 15:32 UTCinvestigating

      We are currently investigating this issue.

    2. 20 de abril de 2026 a las 17:30 UTCidentified

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

    3. 20 de abril de 2026 a las 17:32 UTCresolved

      This incident has been resolved.

    GPU Instance Power-On Issues (NYC Region)

    Comenzó 18 de abril de 2026 a las 15:00 UTC · 2h 18m

    OutageIncidente mayor
    Componentes afectados
    US (NY2)
    1. 18 de abril de 2026 a las 15:00 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. 18 de abril de 2026 a las 17:19 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.

    Service Disruption Identified: Gradient

    Comenzó 16 de enero de 2026 a las 10:27 UTC · 5h 54m

    OutageIncidente mayor
    Componentes afectados
    Gradient
    1. 16 de enero de 2026 a las 10:27 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. 16 de enero de 2026 a las 12:20 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. 16 de enero de 2026 a las 16:20 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. 16 de enero de 2026 a las 16:21 UTCresolved

      This incident has been resolved.

    Service Disruption Identified: CORE

    Comenzó 16 de enero de 2026 a las 10:09 UTC · 2h 39m

    OutageIncidente mayor
    Componentes afectados
    US (NY2)
    1. 16 de enero de 2026 a las 10:09 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. 16 de enero de 2026 a las 12:48 UTCresolved

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

    Service Disruption: Gradient

    Comenzó 26 de diciembre de 2025 a las 14:55 UTC · 21d 1h

    OutageIncidente mayor
    Componentes afectados
    GradientUS (NY2)
    1. 26 de diciembre de 2025 a las 14:55 UTCinvestigating

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

    2. 26 de diciembre de 2025 a las 15:38 UTCidentified

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

    3. 26 de diciembre de 2025 a las 19:55 UTCidentified

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

    4. 26 de diciembre de 2025 a las 21:27 UTCmonitoring

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

    5. 27 de diciembre de 2025 a las 7:50 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. 27 de diciembre de 2025 a las 16:12 UTCinvestigating

      We are continuing to investigate this issue.

    7. 27 de diciembre de 2025 a las 20:46 UTCmonitoring

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

    8. 16 de enero de 2026 a las 16:21 UTCresolved

      This incident has been resolved.

    Service Disruption Identified: CORE

    Comenzó 10 de diciembre de 2025 a las 6:00 UTC · 2h 5m

    OutageIncidente crítico
    Componentes afectados
    US (CA1)
    1. 10 de diciembre de 2025 a las 6:00 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. 10 de diciembre de 2025 a las 7:06 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. 10 de diciembre de 2025 a las 8:05 UTCresolved

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

    Ticketing tool for the Paperspace affected

    Comenzó 5 de diciembre de 2025 a las 9:23 UTC · 56m

    Pending
    Componentes afectados
    Console
    1. 5 de diciembre de 2025 a las 9:23 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. 5 de diciembre de 2025 a las 9:30 UTCidentified

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

    3. 5 de diciembre de 2025 a las 9:31 UTCmonitoring

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

    4. 5 de diciembre de 2025 a las 10:19 UTCresolved

      This incident has been resolved. Thank you everyone.

    Service Disruption Identified: CORE AMS

    Comenzó 1 de diciembre de 2025 a las 0:04 UTC · 1d 2h

    OutageIncidente crítico
    Componentes afectados
    Europe (AMS1)
    1. 1 de diciembre de 2025 a las 0:04 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. 1 de diciembre de 2025 a las 0:04 UTCidentified

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

    3. 1 de diciembre de 2025 a las 3:44 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. 1 de diciembre de 2025 a las 6:50 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. 1 de diciembre de 2025 a las 12:07 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. 1 de diciembre de 2025 a las 14:56 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. 1 de diciembre de 2025 a las 19:53 UTCmonitoring

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

    8. 2 de diciembre de 2025 a las 2:30 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.

    Service Disruption: Gradient

    Comenzó 24 de octubre de 2025 a las 2:06 UTC · 1h 48m

    OutageIncidente mayor
    Componentes afectados
    GradientUS (NY2)
    1. 24 de octubre de 2025 a las 2:06 UTCinvestigating

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

    2. 24 de octubre de 2025 a las 2:57 UTCmonitoring

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

    3. 24 de octubre de 2025 a las 3:54 UTCmonitoring

      We are continuing to monitor for any further issues.

    4. 24 de octubre de 2025 a las 3:54 UTCresolved

      This incident has been resolved.

    Core machine inaccesssible

    Comenzó 3 de octubre de 2025 a las 8:44 UTC · 1d 14h

    OutageIncidente mayor
    Componentes afectados
    US (NY2)
    1. 3 de octubre de 2025 a las 8:44 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. 3 de octubre de 2025 a las 9:13 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. 3 de octubre de 2025 a las 17:10 UTCidentified

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

    4. 3 de octubre de 2025 a las 21:31 UTCmonitoring

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

    5. 4 de octubre de 2025 a las 23:40 UTCresolved

      This incident has been resolved.

    Service Disruption: Single Sign-On (SSO)

    Comenzó 28 de agosto de 2025 a las 12:46 UTC · 3h 7m

    IssuesIncidente menor
    Componentes afectados
    Desktop App & StreamingConsole
    1. 28 de agosto de 2025 a las 12:46 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. 28 de agosto de 2025 a las 14:07 UTCinvestigating

      We are continuing to investigate this issue.

    3. 28 de agosto de 2025 a las 14:08 UTCidentified

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

    4. 28 de agosto de 2025 a las 14:33 UTCmonitoring

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

    5. 28 de agosto de 2025 a las 15:53 UTCresolved

      This incident has been resolved.

    Service Disruption: Paperspace Console

    Comenzó 30 de mayo de 2025 a las 6:12 UTC · 1h 25m

    OutageIncidente mayor
    Componentes afectados
    Console
    1. 30 de mayo de 2025 a las 6:12 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. 30 de mayo de 2025 a las 7:37 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.

    Service Disruption: CORE VMs in NY2

    Comenzó 24 de febrero de 2025 a las 7:24 UTC · 3h 59m

    IssuesIncidente menor
    Componentes afectados
    US (NY2)
    1. 24 de febrero de 2025 a las 7:24 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. 24 de febrero de 2025 a las 9:33 UTCidentified

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

    3. 24 de febrero de 2025 a las 9:39 UTCmonitoring

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

    4. 24 de febrero de 2025 a las 11:24 UTCresolved

      This incident has been resolved.

    API degraded performance and console access issues

    Comenzó 6 de febrero de 2025 a las 20:08 UTC · 54m

    IssuesIncidente menor
    Componentes afectados
    ConsoleAPI
    1. 6 de febrero de 2025 a las 20:08 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. 6 de febrero de 2025 a las 20:33 UTCmonitoring

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

    3. 6 de febrero de 2025 a las 21:02 UTCresolved

      This incident has been resolved.

    Service Disruption Identified: Gradient

    Comenzó 25 de enero de 2025 a las 21:16 UTC · 6h 45m

    IssuesIncidente menor
    Componentes afectados
    Gradient
    1. 25 de enero de 2025 a las 21:16 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. 25 de enero de 2025 a las 22:27 UTCidentified

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

    3. 25 de enero de 2025 a las 23:22 UTCmonitoring

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

    4. 26 de enero de 2025 a las 4:01 UTCresolved

      This incident has been resolved.

    Service Disruption: Gradient and Core

    Comenzó 24 de enero de 2025 a las 20:30 UTC · 3h 4m

    OutageIncidente mayor
    Componentes afectados
    GradientUS (NY2)
    1. 24 de enero de 2025 a las 21:36 UTCinvestigating

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

    2. 24 de enero de 2025 a las 21:37 UTCinvestigating

      We are continuing to investigate this issue.

    3. 24 de enero de 2025 a las 21:37 UTCidentified

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

    4. 24 de enero de 2025 a las 22:12 UTCmonitoring

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

    5. 24 de enero de 2025 a las 23:33 UTCresolved

      This incident has been resolved.

    Service Disruption: Console UI

    Comenzó 21 de diciembre de 2024 a las 2:40 UTC · 2h 15m

    OutageIncidente mayor
    Componentes afectados
    Desktop App & StreamingConsole
    1. 21 de diciembre de 2024 a las 2:40 UTCinvestigating

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

    2. 21 de diciembre de 2024 a las 3:45 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. 21 de diciembre de 2024 a las 4:13 UTCidentified

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

    4. 21 de diciembre de 2024 a las 4:15 UTCmonitoring

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

    5. 21 de diciembre de 2024 a las 4:55 UTCresolved

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