Developer instance stuck on "internal error" + can't reach support to escalate

[RanjithaC]

Issue 1 - Instance won't open
When I try to open my Developer instance from the Now Support landing page, I get this banner:

"We're having trouble opening your instance due to an internal error. We should have it fixed in a few minutes."

It's been showing this for a while and hasn't resolved on its own.

Issue 2 - Can't log a support ticket about it
When I try to go through Now Support to report the instance issue, I hit a "Sorry, you can't login with this ServiceNow ID" page. It looks like my ServiceNow ID's email isn't recognized as an authorized Now Support user under my organization's account, so I can't even open a case for Issue 1.

[Tanushree Maiti]

Hi @RanjithaC 

Several community members have faced the same instance offline issue ( with different error) this week. 

I faced the same Instance offline issue post multiple refresh ( waited for 5-6 hours) on Monday with the following error:

“Bad Request
This combination of host and port requires TLS.”

Since I needed the instance urgently, I released the existing instance through the Developer Portal and requested a new one. I received the new instance within about 2 minutes.

If you’re okay with waiting, you can wait another 1–2 days or possibly longer   and keep refreshing/checking the Developer Portal. Hopefully, your instance will come back online.

Alternatively, if you don’t have any important work or data in your offline PDI, you can follow the same process I did and release the existing instance and request a new one.

Unfortunately, there doesn’t appear to be any support available for PDI.