Paperspace Outage History

18 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Paperspace status100.00% uptime history

Every Recorded Paperspace Incident

Paperspace incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Service Disruption: Paperspace ConsoleResolved We experienced a second occurrence of the issue affecting access to the Paperspace Console on November 4, 2026, between 15:30 UTC and 16:50 UTC. The issue has been mitigated, and users should now be able to…0 minResolved
Nov 4, 2026Service Disruption: Paperspace ConsoleThis incident has been resolved.3h 20mResolved
Oct 30, 2026Gradient Notebooks Stuck in Pending State - Recovery UnderwayResolved – Gradient Notebooks Stuck in Pending State Our Engineering team has resolved the disruption affecting Gradient Notebooks that began at approximately 02:23 UTC. As of approximately 05:33 UTC, operations have…1h 17mResolved
Sep 3, 2026Scheduled Paperspace Machine Storage MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Aug 26, 2026Service Disruption: Paperspace ConsoleOur 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…1h 3mResolved
Jun 9, 2026NY2 Network Overlay UpgradeThe scheduled maintenance has been completed.2h 0mScheduled
May 26, 2026Service Disruption Identified: CORE CA1This incident has been resolved now.3h 34mResolved
May 8, 2026Service Disruption Identified: COREOur 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…3h 54mResolved
Apr 20, 2026Degraded Performance: Core VM Start/Stop Delays and Internal Connectivity IssuesThis incident has been resolved.2h 0mResolved
Apr 18, 2026GPU Instance Power-On Issues (NYC Region)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…2h 18mResolved
Mar 10, 2026NY2 CORE Storage MaintenanceThe scheduled maintenance has been completed3h 0mScheduled
Feb 3, 2026NY2 CORE Storage MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Jan 16, 2026Service Disruption Identified: GradientThis incident has been resolved.5h 54mResolved
Jan 16, 2026Service Disruption Identified: COREThis incident has been resolved. The core VMs should be working as intended. Thanks for your cooperation.2h 39mResolved
Dec 26, 2025Service Disruption: GradientThis incident has been resolved.505h 25mResolved
Dec 10, 2025Service Disruption Identified: COREThis incident has been resolved. The core machines should be working as intended. Thank you for your patience and cooperation.2h 4mResolved
Dec 5, 2025Ticketing tool for the Paperspace affectedThis incident has been resolved. Thank you everyone.56 minResolved
Dec 1, 2025Service Disruption Identified: CORE AMSThe 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.26h 26mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Paperspace incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Paperspace Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Paperspace acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Paperspace outage in this window ran 21d 1h, against a mean recovery of 1d 7h. If you depend on Paperspace in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.