PDI instance stuck Offline for 5+ hours with 502 Bad Gateway (snow_adc)

[srimeera612]

Hi Team,

My ServiceNow Personal Developer Instance (PDI) dev380747 has been Offline for more than 5 hours.

Issue details:
- Instance URL: https://dev380747.service-now.com
- Error shown: 502 Bad Gateway
- Message: snow_adc
- Developer portal says:
"We're having trouble opening your instance due to an internal error."

I already tried:
- Refreshing the instance
- Opening login.do/nav_to.do
- Different browser/network

The Actions menu only shows:
- Release instance
- View history

There is no reboot or repair option available.

I have important development work inside this instance including catalog items, flows, tasks, and configurations, and I do not want to lose the data by releasing the instance.

Could someone please help recover or restart the instance from the backend?

Thanks.

[Dr Atul G- LNG]

I've been using PDI without any issues since this morning, but I've noticed several posts in the community about PDI being offline. Here are some points to consider:

1. There is no support available for PDI.
2. If you can wait, let's wait a bit longer.
3. You can release this instance and start a new one, but you will lose your previous data. To avoid losing update sets in the future, make sure to take regular backups of your PDI.

There have been 3-4 posts in the community today about PDI failures or unavailability. Based on the responses, you might need to wait 1-2 days and hopefully, the PDI will be back online.

[Tanushree Maiti]

Hi @srimeera612 

Refer KB : KB1115956 ServiceNow instance responds with 502 (Bad Gateway) 

Unfortunately there is  no support available for PDIs. You should wait for 24-48 hours. If  PDI  is not restored, you should request for new instance.