PDI Offline for Several Days – Need Recovery Help

[23a3sa42d2]

Hello ServiceNow Community,

My Personal Developer Instance (PDI), dev295422, has been showing Offline for several days.

The portal displays the message that my PDI is temporarily unavailable due to infrastructure maintenance.

I have tried refreshing the instance multiple times, but it remains Offline. Opening the instance URL also gives me a 502 Bad Gateway error.

I have an important learning project called Hostel360 - Smart Hostel Asset Management System in this instance. I created custom tables, Flow Designer automations, and issue classification logic, and I was preparing to build the dashboard.

Could someone please advise me on how to recover access to this PDI and whether my existing project data can be preserved?

I have not released or reset the instance.

Thank you for your help.

[Dr Atul - LNG]

No mate, until you get your PDI back , you can't do anything, even not able to take back up. Hard but truth.

[Simon Hendery]

Hi @23a3sa42d2 

Sorry, but this is a user community, not a help desk / tech support. We have no ability to access the PDI infrastructure, so can't help you. 

ServiceNow offers absolutely no support for PDIs.

[Tanushree Maiti]

Hi @23a3sa42d2 

Check  the response from Admin Team  : https://www.servicenow.com/community/app-engine-forum/pdi-offline/td-p/3611953

Please wait until the backend work is completed and your instance is up and running.

[Simon Hendery]

Yep, better @Tanushree Maiti - see, doesn't it feel more satisfying to post something relevant than your usual AI slop?

[VJ_Srivastava]

Hello @23a3sa42d2,

From an architectural and disaster recovery perspective, this is a painful but essential lesson in how to treat ephemeral infrastructure.

Personal Developer Instances operate on the absolute lowest tier of ServiceNow's infrastructure grid. They carry zero uptime guarantees, zero SLA, and zero dedicated technical support. Building a comprehensive application like your Smart Hostel Asset Management System solely on a local PDI without an external version control strategy is a major architectural risk.

In the ServiceNow enterprise ecosystem, development relies heavily on Source Control and CI/CD pipelines. By linking your scoped application to a remote Git repository, your data becomes decoupled from the volatile hardware. If a node fails or an instance is wiped, the architecture allows you to simply spin up a new environment, apply your credentials, and pull your entire application branch down in minutes.

If this instance does not recover natively, you must treat this as a forced disaster recovery drill. When you provision your next instance, make establishing a Source Control link your absolute first architectural step before building any new tables or flows.