PDI inaccessible (504 Gateway Timeout) and Developer Portal (/dev.do) stuck on Loading

[SharveshS]

Hi everyone,

I'm facing an issue with my Personal Developer Instance (PDI), and I'm unable to access either my instance or the Developer Portal.

Issue:

• My PDI URL returns a 504 Gateway Timeout error.
• The Developer Portal (https://developer.servicenow.com/dev.do) gets stuck indefinitely on the Loading screen.
• Because of this, I'm unable to manage, restart, or refresh my PDI.

Troubleshooting already performed:

• Tried multiple browsers (Edge/Chrome).
• Tried Incognito/Private mode.
• Cleared browser cache and cookies.
• Tried from a different browser profile.
• The issue persists.

Has anyone experienced this recently, or is there a known issue with the Developer Portal or PDI infrastructure? Any guidance would be appreciated.

Thank you.

[Dr Atul G- LNG]

Hi @SharveshS 

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.

[Aditya_hublikar]

Hello @SharveshS ,

Don't worry buddy . You are not alone , this  same issue is faced my multiple users . But now getting this message 

After some time screen is loaded but instance went to offline .

 I think , we should wait for some time , its servicenow internal error  🙂 . Instance will  back  after some time .

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

Regards,
Aditya

[Tanushree Maiti]

Hi @SharveshS 

Did you run any background script or without that you are getting 504 error.

If after running backgroung script , you are getting 504 error , then will suggest to wait to get the activity completed at internally.

A 504 Gateway Time-out during a Background Script typically indicates that the script execution exceeded the timeout limit enforced by the platform, browser, or proxy server. This often happens when processing large datasets or waiting for slow external integrations.

Recommended actions:

• Terminate the current job or transaction if it is still running.
• Clear the instance cache using cache.do.
• For scripts that process large volumes of data, avoid using the Background Scripts page. Instead, create a Fix Script (System Definition > Fix Scripts). Fix Scripts are trackable, can be monitored, and continue executing even if the browser session times out.
• Use setLimit() on GlideRecord queries whenever possible to reduce the number of records retrieved in a single execution.
• Process records in small, manageable batches (like 50–100 records per execution) to minimize execution time and reduce the risk of node lock-ups or timeouts.

If without running any script you are getting 504 error, will suggest 

Wait for hours or day , Try to refresh it from Developer portal ,, it would be up.

[Tejas Adhalrao]

hi @SharveshS ,

Yes, many users are currently experiencing the same issue, so it appears to be a platform-wide issue. Let's trust the ServiceNow team—they have always been quick to address Developer Portal and PDI-related issues. I'm confident the issue will be resolved soon, and our PDIs will be back up and running shortly.

If you found my solution helpful, please mark it as Helpful and Accept Solution.

thanks ,

tejas