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.

[peterholdsworth]

@ServiceNow  I've been working on mine (dev267725) all week, but went to try this morning and it's offline as well 😞
I was going to do a full backup today as well - it's like it knew..... !! 

==================================

Mine's back online now and.... implemented the GitHub source control as per Earl's guide on the right ----->

[surajsengar]

@ServiceNow  - Appreciate the proactive updates and the extension for impacted PDIs. This reinforces the importance of best practices like source control and update set backups. Thanks for supporting the developer community!

[RomanosN]

There are still issues with PDIs, mine is showing offline for the last couple of days without signs of coming back online. dev391045

[christafitz]

The new one I made when my previous was not coming online due to this issue, is now offline.  It says I have not used it in 7 days, when I used it on Friday 9/11/2027, which was 3 days ago. It was acting up a bit then, but now is completely offline. DEV441143. This is disappointing as I will probably need to release it and request a new one and start over again.

[RomanosN]

@christafitz Good luck. I had to delete mine and rebuilt it from scratch as I had no backups. Luckily I had very good documentation and was able to rebuild within a couple of hours. If you are in a hurry that's what I suggest.

[TodQ]

dev437902 is offline as well.  I didn't have any issues to speak of last month, but this week has been another story.

[AndrewG81765973]

Backup, backup, backup.  PDIs are a sandboxes with limited capabilities when considering what you can do with demo instances.   If you're working with Build Agent:  use source control.  If you aren't and you lose your PDI is really is your own fault.  Chalk it up to growing pains and a lesson learned and ** back your stuff up **.  Making changes in Global scope?  Export update sets.  I've found that the more going on in my PDI:  the more likely it could just go offline the next morning.  Custom components, custom apps that populate tables via scheduled jobs with records increasing into the hundreds of thousands (or millions) over a few days..if this is jamming things up then it would be a reasonable assumption they may be bumped offline temporarily, possibly permanently for performance reasons.  These are all assumptions as I don't work for ServiceNow but from experience I've found that instead of going the HI ticket route or simply waiting and hoping it comes back online:  Back your work up. Release the instance. Request a new one.  Restore any functionalities via update sets or pulling from source control. 

PDIs will have hiccups once in awhile that delays provisioning or keeps them offline for extended periods.  The ability to request and administer them always comes back, but your actual PDI might not for any number of reasons.  If you always assume its a 'house of cards' that could fall at any moment, it will reinforce the vigilance to backup your stuff. 

P.S I learned this the hard way

[kirsten_for]

@ServiceNow  are all PDI's offline today?  I am receiving 505 error message 

[Tim Woodruff]

My instance `dev187479` is also offline and has been for several days with no info or options on the dev site. Can anyone help sort this out? 

 (Also, haven't been able to activate plugins for at least several weeks.... -.-)

[Simon Hendery]

Hi @Tim Woodruff 

Short answer: no. No one can help. The PDI situation is a complete hot mess right now.

Aren't you pleased you left this ecosystem? 🤣🤣