Unable to login to developer.servicenow.com (LOADING SCREEN)

[Christian Dave2]

Hi everyone,

I’ve been unable to access developer.servicenow.com since yesterday evening.

Here is what I’m experiencing and what I’ve tried so far:

Issue:

My Personal Developer Instance (PDI) went offline, and when trying to access the Developer Site, I get stuck on an endless spinning loading screen.

Troubleshooting done:

Cleared browser cache, cookies, and history.

Created a new account to test, but encountered the exact same issue.

Is anyone else experiencing this, or is there a known issue with the developer portal right now? Any advice on how to resolve this would be appreciated!

[adamberger]

Ok, I have the same problem. Nothing is working. 
https://developer.servicenow.com/dev.do#!/manage-instance is spinning forever. It's not working either in chrome, or anonymous window neither in Safari. Nowhere.  Link to my personal instance returns 504. 

And It's even better. When I'm logged In with my account, Support pages keeps redirecting me to SSO, like 4 times and then I received error saying Sorry, you can't login with this ServiceNow ID. So I can't even raise a Support Ticket for it.  

It's in this state for 6 hours now. 

[Dr Atul G- LNG]

Now Support  not applied here, this is a PDI, and PDIs do not have official support. You will need to wait and be patient, mate.

[EwaldM]

I have the same issue! Tried different browsers. Cleared browser cache, cookies and history too...

[masonreed11]

It sounds like a platform-side issue, especially since a new account has the same problem. Try a different browser or incognito mode, and if it still spins, report it to ServiceNow support and check for any ongoing outage.

[yashkamde]

Hello @Christian Dave2 ,

I started seeing the same behavior today. As soon as I open my PDI, it stays on the Loading screen (like in your screenshot)

I'd recommend waiting 30–60 minutes and trying again. If it's still stuck after 2–3 hours, raise an issue through the Developer Portal Support, as the instance may require intervention from the ServiceNow team.

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