My team can't do any type of scripting in our SAND Instance

[John Johnson]

Hello,

We purchased a 'SAND' instance about 4 years ago.  It worked great for about a year. We used it as a secondary development instance, going between DEV and SAND for development.  3 years ago, we cloned down from production to all our sub instances with the same clone profile. We were able to script in all sub instances except for our SAND instance. I put in a support case but was told it was our network causing issues even though all other instances worked perfectly. I was told to do a 'zBoot' on the instance and did so. This caused me to have to redo everything on the instance.  It was actually like OOB, i.e., LDAP, SSO, etc, had to be reconfigured.  Finally getting that done, we had the same issue.  When i say we can't script on the instance, i mean we can't create and save a fix script, business rule, scheduled script, etc.  I can't even modify a script and save it.  I get this error.

"The webpage at https://<instance>.service-now.com/sysauto_script.do might be temporarily down or it may have moved permanently to a new web address".  I was told it was our network which makes no sense because all other instances work great with no issues.  Sure, I could think of it being a firewall on our side, cyber blocking it or something, but it worked for over a year.  I was then told to use the default OOB clone profile to clone over the SAND instance.  Same results.  Long story short, we finally had the support team to blow up the instance all together, then several weeks later, they stood up a new sand instance for us, sand2.  worked great for a week.  cloned down and then we had the same issue.  I think it is just a cooincident that the instance had issues after the clone.  This has been going on for over 3 years. For Real!.  Have any of you heard of this at all?  

Today, support did a change for 'Role Recalculation' thinking it was role related.  Same thing after the change.

Any suggestions would be greatly appreciated

[John Johnson]

Thanks for the help, everyone! It turned out to be an on-site firewall!