PDI dev419537 showing 502 Bad Gateway – unable to access instance

[Gurrala]

Hi ServiceNow Community,

My Personal Developer Instance dev419537 suddenly became unavailable today around 11:00 AM IST.

When I try to access the instance, I get:

502 Bad Gateway – snow_adc

The Developer Portal also displays:
“We're having trouble opening your instance due to an internal error. We should have it fixed in a few minutes.”

I have already waited several hours, but the instance is still unavailable.

Could anyone please advise whether I should continue waiting or if there is another way to recover the PDI?

I have important development work in this instance, so I don't want to release it and lose the data.

I have attached screenshots of the error.

Thank you.

[Dr Atul G- LNG]

Hi @Gurrala 

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, the underlying infrastructure or node hosting the instance may have encountered an issue.

Option 1 – Try Refreshing the Instance (Recommended Approach)

1. Sign in to the ServiceNow Developer Portal.
2. Go to Manage My Instance.
3. Click Refresh, if the option is available.
4. Try refreshing the instance 4–5 times, as the PDI may recover after a manual refresh.

Hopefully, your PDI will become available again.

Option 2 – Release the Instance and Request a New PDI

If the PDI continues to return an HTTP 502 error or remains stuck for more than 24–48 hours, you may need to release the instance and request a new PDI from the Developer Portal.

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

 Please consider 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 for a new PDI.
• There have also been reports of PDI failures, provisioning delays, and general Developer Portal availability issues.
• Unfortunately, there is currently no guaranteed timeline for when these issues will be resolved or when a new PDI will be provisioned.

For now, the best approach is to try refreshing the instance several times first. If that does not work, monitor the request status in the Developer Portal and be patient while waiting for a new instance.