Incident: Developer Site Restored and PDI Availability Issues

[ServiceNow]

Update: July 27, 2026 

The infrastructure issue has been resolved, and all PDIs are back online. New PDI provisioning has also resumed, with PDIs currently available and little to no wait. 

All developers have been given additional time to access their PDIs and back up their work. If you previously received a reclamation notice, the date in that notice no longer applies. You will receive a new email with an updated date before your PDI can be reclaimed. 

We appreciate your patience while we worked to restore full PDI availability. 

Starting the evening of July 22, an infrastructure-related issue caused the Developer Site to become unavailable and some personal developer instances (PDIs) to appear offline. The Developer Site is now back online. We are continuing to investigate the impact to PDI availability and actions.

CURRENT STATUS

Developer Site: Available
New PDI provisioning: Available
Existing PDIs: Available
Developer action:  Log in to wake your PDI as needed and back up any work you want to preserve

 

WHAT HAPPENED?

On July 22, an infrastructure-related issue affected the Developer Site and some PDIs. The Developer Site was temporarily unavailable but has since been restored.

While we address the remaining issue, new PDIs cannot be created, and provisioning, reclaiming, and waking actions remain paused. Some affected PDIs are currently hibernating and cannot be accessed. If your PDI is affected, you will see a banner on the Developer Site.

WILL I LOSE THE DATA STORED ON MY PDI?

We do not expect any data loss as a result of this incident. Affected PDIs are currently hibernating, and the data stored on them is expected to remain available when they come back online. No action is required at this time.

I HAVE IMPORTANT DATA ON MY PDI THAT I NEED TO ACCESS. WHAT SHOULD I DO?

If your PDI remains offline, you will need to wait until it is back online to be able to access the data stored on it. No action is required at this time.

We recognize this interruption may affect ongoing development work, and we appreciate your patience as we work to resolve the issue.

As a reminder, PDIs are intended for learning, experimentation, and development scenarios and do not provide the same performance or reliability as customer instances. Because lost PDI data cannot be recovered, production and demo code should be stored outside of a PDI. We also recommend regularly backing up your PDI work using source control or update sets so it can be transferred or restored if needed.

[MIchael Shannon]

Activating a plugin did not work for me - my instance is still offline.

[Martin_e]

Activating the plugin did not work either. But after it failed, I was able to release my offline PDI. So I could request a new PDI which was setup within a minute

[christafitz]

I was unable to activate any Plugins for my previous offline PDI as well, but as the user above stated, I could then Release my offline instance. I was then able to request a new PDI and set that PDI up to work.

[Brian Trivison]

My PDI remains offline.  dev399588

[stefanstefc]

my PDI is also still offline  , dev216490 cant wake the instance , release it nor refresh it.

[mugi-san]

The PDI that was temporarily running is now offline again. Please let me know if you have any updates on this.

[NehaG8791370651]

Hi everyone,

It is a huge relief to see most of the PDIs back online! While outages are frustrating, this incident serves as a harsh but necessary reminder of why we shouldn't treat PDIs as primary storage for our hard work.

If you haven't already, take a few minutes today to connect your active projects to an external Git repository. Leveraging Source Control for scoped applications in ServiceNow is incredibly straightforward and can be linked directly to a free GitHub or GitLab account. Committing your work at the end of every development session completely removes this single point of failure.

For those still waiting on the remaining instances to come online, hang in there! Glad to see the platform team actively working to resolve the lingering offline PDIs.

[VJ_Srivastava]

Incidents like this underscore a critical principle in enterprise architecture: the strict division between experimental sandboxes (PDIs) and formal sub-production environments.

While PDIs are invaluable tools for prototyping, independent research, and upskilling, they are intentionally excluded from the high-availability architecture and SLAs that protect actual customer instances. Relying on a PDI for mission-critical development introduces an unnecessary point of failure into your delivery pipeline.

This infrastructure interruption should serve as a catalyst for technical leaders to audit their team's development lifecycles. It is a timely reminder to ensure that all production-bound code is authored, tracked, and maintained within dedicated, formally supported sub-production instances that are integrated with a resilient CI/CD pipeline and automated source control.

[FakhreA]

Hi Community,
Please look into this and get it resolved at the earliast its been more than 13 days.
Thanks!

[Kristina Ledden]

Any updates here? I am still unable to access my PDI, keep getting this message on the developer site: 

Alert level: warning. We're having trouble opening your instance due to an internal error. We should have it fixed in a few minutes.

When I do try to access my PDI, I receive this message: 

Bad Request
This combination of host and port requires TLS.