Australia PDI Offline - 502 Bad Gateway (snow_adc)

VidyaR603675802
Tera Contributor

Hello ServiceNow Developer Community,

My Personal Developer Instance, running the Australia release, has been offline since 2 days.

The Developer Portal shows the instance status as Offline. When I click the refresh/wake button, it attempts to refresh but returns to Offline. When I access the instance directly, I receive: 502 Bad Gateway, snow_adc

I have already tried refreshing/waking the instance multiple times, but the issue persists.

Could the Developer Program team please confirm whether this PDI is affected by an ongoing Australia PDI infrastructure issue and whether it can be recovered?

Instance: dev313766
Release: Australia
Error: 502 Bad Gateway - snow_adc
Current status: Offline

Thank you.

1 ACCEPTED SOLUTION

Dr Atul - LNG
Tera Patron

Hi @VidyaR603675802 

 

Some PDIs may be temporarily unavailable due to scheduled maintenance.

 

If your PDI is currently offline, you can:

Wait for maintenance to complete and your instance to become available again. Release your current instance and request a new one. Please note that releasing your instance will permanently delete all data and work stored on it.

As a reminder, PDIs are unsupported development resources and do not have an availability, support, or uptime SLA. We strongly recommend regularly backing up any work you don’t want to lose.

 

@kh_safal  @Kh_Samyak 

****************************************************************************************
Regards
Dr Atul G. - Learn N Grow Together ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
******************************************************************************************

View solution in original post

4 REPLIES 4

Dr Atul - LNG
Tera Patron

Hi @VidyaR603675802 

 

Some PDIs may be temporarily unavailable due to scheduled maintenance.

 

If your PDI is currently offline, you can:

Wait for maintenance to complete and your instance to become available again. Release your current instance and request a new one. Please note that releasing your instance will permanently delete all data and work stored on it.

As a reminder, PDIs are unsupported development resources and do not have an availability, support, or uptime SLA. We strongly recommend regularly backing up any work you don’t want to lose.

 

@kh_safal  @Kh_Samyak 

****************************************************************************************
Regards
Dr Atul G. - Learn N Grow Together ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
******************************************************************************************

Thank you for your response. I've planned to wait for a day or so for the maintenance to get over. 

Aditya_hublikar
Giga Sage

 

Hello @VidyaR603675802 ,

Nowdays this is common issue faced by multiple users . My PDI also went to Offline since yesterday . But dont worry in rare situation pdi dont get back online . We can just keep some patience for while . Always keep in mind if you are doing any business requirement task on pdi then always takes its backup even if task is in progress or completed so it will help in such situations . Unfortunately  there is no any solution  for this .

 

You can also refer this servicenow admin ressponses 

 

 

Aditya_hublikar_0-1793705907495.png

 

 

 

 

 

 

 

Aditya_hublikar_1-1793705907496.png

 

 

 

 

 

 

 

 

 

https://www.servicenow.com/community/developer-forum/pdi-dev443121-offline-502-snow-adc-no-wake-opti...

https://www.servicenow.com/community/developer-forum/my-developer-instance-is-offline/m-p/3614836/hi...

 

If this helps you then mark it as helpful and accept as solution .

Regards,

Aditya

yashkamde
Giga Sage

Hello @VidyaR603675802 ,

 

It means that your instance is offline so it may take some time :

yashkamde_0-1793705907002.png

 

In the meantime, try refreshing the page and check again after a while. If it's urgent, you can release the current instance and request a new one, but I wouldn't recommend doing that as the first option.

yashkamde_1-1793705907077.png

 

If my response helped mark as helpful and accept the solution.