- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello ServiceNow Developer Community,
Please help investigate my inaccessible Personal Developer Instance and restore access while preserving all existing work.
Instance: dev443121
URL: https://dev443121.service-now.com/
Release shown in the Developer Portal: Australia
Observation period: October 15, 2026, approximately 20:32-20:50 JST (11:32-11:50 UTC). The exact start of the outage is unknown.
Observed symptoms:
- The Developer Portal is accessible and shows the instance assigned to my account.
- The instance remains Offline, including after Refresh completes normally.
- Opening the instance root URL directly returns "502 Bad Gateway" with "snow_adc".
- Start building is disabled.
- No Wake Instance or Restart option is available. The only enabled Actions are Release instance and View history.
- The management page shows 0 alerts, with no visible waking-up progress, maintenance details, or estimated recovery time.
The instance history shows successful Event Management and ServiceNow IntegrationHub Installer activations dated October 14, following an earlier failed Event Management activation. This is background only; I have no evidence that the plugin activity caused this outage.
Could the appropriate team check the backend health and startup status, clarify whether maintenance is in progress, and advise on a non-destructive recovery and estimated recovery time? Please route this report to the appropriate Developer Program team if backend intervention is needed.
Preserving the existing instance is essential. Please retain all data, installed plugins, configurations, and customizations. This report does NOT authorize a reset, wipe, release, reclamation, reprovisioning, or replacement. Please obtain my explicit approval before any action that could remove or replace existing content. I have not reset or released the instance.
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @LiangYang3,
Thanks for reporting these issues. We have some clarification from the PDI team now. New software installations across the PDI server infrastructure have temporarily caused several instances to go offline. The affected PDIs will remain unavailable until the installations are complete. Thanks for your patience in the meantime!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I’ve been using my PDI without any issues since this morning, but I’ve noticed several posts in the ServiceNow Community today reporting PDI failures or unavailability. Based on the responses and recent experience, this appears to be a known issue affecting multiple users.
A few points to consider:
- There is currently no dedicated support available for PDI, so there isn’t much we can do from our side while the issue is ongoing.
- If you can wait, I would recommend waiting a little longer. Some users have reported their PDI coming back online after a few hours, although there is no guaranteed timeframe. Based on recent reports, it may take anywhere from a few hours to 1–2 days.
- You can release the current PDI and request a new one, but be aware that you will lose any data or configuration stored in the existing instance.
There have been around 3–4 community posts today about PDI failures or unavailability, so you’re not the only one experiencing this.
The issue might be related to ServiceNow's ongoing transition to a new release and the rebuilding/provisioning of PDIs, which could be contributing to instances being temporarily unavailable.
For now, patience is probably the best approach. If you have important data in the current PDI, I would avoid releasing it and give it some more time. If there is no important data and you need a working environment urgently, requesting a new PDI could be an option.
Backup and restore you PDI data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @LiangYang3
When I got 502 Bad Gateway error 4 months back for few hours ,after waiting for some time, the issue resolved itself automatically.
You can also try accessing it again after regular intervals. PDIs recover automatically when background tasks or refreshes finish.
If the error persists past 4-5 day, you can think of to release the broken instance from your developer portal and request a brand new PDI.
Note: Releasing an instance deletes all previous data stored on it
Please note , there is no support available for PDI.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
This is a user community, we can't investigate or fix your issue. All we can do is advise you that PDI problems are rampant at present. We're all having the same issues!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @LiangYang3 ,
Don’t worry, buddy. This has been happening with multiple users these days. My instance also went offline after some time, but it came back online on its own.
You just need to wait for some time and then try logging in again. In rare cases, the instance may not come back online. If it still doesn’t come back after waiting for a while, you can release the instance and request a new one. Always remember if you are working on business requirement in pdi then always take its backup even work is done or in progress , so if unfortunately pdi get offline it will not affect your work .
If this helps you then mark it as helpful and accept as solution.
Regards,
Aditya
