Personal Developer Instance dev382137 is Offline (502 Bad Gateway)

[23481A05N2]

Hello,

My Personal Developer Instance (PDI) dev382137 has been offline.

Details:
- Instance Name: dev382137
- Status: Offline
- Error: 502 Bad Gateway when opening the instance
- Refresh button does not bring the instance online.
- The issue has persisted for several hours.

Could you please help recover or restart my instance?

Thank you.

[Dr Atul G- LNG]

Hi @23481A05N2 

If your ServiceNow Personal Developer Instance (PDI) has been stuck in the Refreshing state for more than 24 hours and is returning an HTTP 502 error, it is likely that the underlying infrastructure or node hosting your instance has encountered an issue.

Option 1 – Try Refreshing the Instance

1. Sign in to the ServiceNow Developer Portal.

2. Go to Manage My Instance.

3. Click the Refresh button (if available).

4. Wait for the refresh process to complete.

In some cases, the PDI may recover after a manual refresh.

Option 2 – Release the Instance and Request a New PDI

If your PDI continues to return an HTTP 502 error or remains stuck for more than 24–48 hours, I generally recommend releasing the instance and requesting a new Personal Developer Instance (PDI) from the Developer Portal.

Based on community experience, instances that remain in this state for an extended period rarely recover automatically.

Please note the following before releasing your instance:

• Provisioning times for new PDIs have increased significantly in recent weeks.

• Many community members have reported waiting 2–3 weeks or longer to receive a new instance, regardless of the selected release version.

• There have been multiple reports of PDI failures, provisioning delays, and general Developer Portal availability issues.

Unfortunately, no one can provide an exact timeline for when these issues will be resolved or when a new PDI will be provisioned.

For now, the best approach is to monitor your request status in the Developer Portal and be patient while waiting for your new instance to become available.

[AndersBGS]

Hi @23481A05N2 

notice, there is no support for PDIs, so either wait or release your instance and request a fresh installation.

[glideFather]

ahoy @23481A05N2,

navigate to the https://developer.servicenow.com/dev.do#!/manage-instance and try to Refresh it once a while, sooner or later it shall be available. Or at least it always get available in my case...

Read [GF#5] PDI in Offline state: Resolving Error 502 for more details about states in PDI and how to resolve them.

[Tanushree Maiti]

Hi @23481A05N2 

Last week, I was getting a 502 Bad Gateway error for a few hours. After waiting for some time, the issue resolved itself automatically.

You can also try accessing it again after regular intervals.

If the issue still persists, even after refreshing it from the Developer Portal (after 4–5 days),

release the current instance and request a new one.