- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
My personal developer instance has been unreachable since 15 September, about 2 days and 12 hours.
Every request returns the same response from the load balancer, including the login page:
HTTP/1.1 400
Server: snow_adc
Bad Request
This combination of host and port requires TLS.
Reproduced on /, /login.do, /navpage.do, /stats.do and every REST API path. Plain HTTP on port 80 redirects to HTTPS correctly, so DNS and routing work.
This is not a TLS problem on my side: the handshake completes and the certificate presented is valid (CN=*.service-now.com, DigiCert, valid until 13 November 2026). I receive a well-formed HTTP response over that connection, so the message looks like a generic load-balancer error rather than a real TLS negotiation failure.
It is also not hibernation — a hibernating instance redirects to the wake-up page, while this returns 400 even on paths that need no authentication.
In the developer portal, Manage my instance shows Status: Offline, and the home page describes the same instance as "Refreshing Instance...". The instance record itself is intact
— the URL, the admin user, the version and 46 plugins are all still listed.
The instance holds configuration data I would rather not lose, so I would prefer not to reset or release it.
Two questions:
1. Can an instance in this state be restored, or is the data already gone?
2. What causes it — is it triggered by something on the user side, such as a usage pattern or an inactivity threshold, or is it a platform-side issue?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
57m ago
It looks like this is a known issue.
There is no official support for this issue, so it is difficult to say exactly what is causing it or when it will be resolved. At this stage, patience may be the best option while waiting for a fix.
Current status:
- Developer Site: Available
- New PDI provisioning: Paused
- PDI reclaim and wake actions: Paused
- Existing PDIs: Some remain offline
- User action required: None at this time
ServiceNow does not expect any data loss. Affected PDIs are currently hibernating, and the data stored on them is expected to remain available once the instances are restored.
If your PDI is offline, you will need to wait until it becomes available again before accessing your data. No action is currently required.
ServiceNow is continuing to monitor the situation and will provide further updates as more information becomes available.
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
******************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
57m ago
It looks like this is a known issue.
There is no official support for this issue, so it is difficult to say exactly what is causing it or when it will be resolved. At this stage, patience may be the best option while waiting for a fix.
Current status:
- Developer Site: Available
- New PDI provisioning: Paused
- PDI reclaim and wake actions: Paused
- Existing PDIs: Some remain offline
- User action required: None at this time
ServiceNow does not expect any data loss. Affected PDIs are currently hibernating, and the data stored on them is expected to remain available once the instances are restored.
If your PDI is offline, you will need to wait until it becomes available again before accessing your data. No action is currently required.
ServiceNow is continuing to monitor the situation and will provide further updates as more information becomes available.
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
******************************************************************************************
