I mean NetSuite accidently push the TLS1.2

Last month NetSuite briefly pushed the change that is scheduled to go out this Friday. So for most of that day we found that anyone connecting to the webservice was getting these errors. The fix was to directly target one of the NS domains instead of using the call that determines which domain you should be using. They reverted the change and everything went back to normal

There was a planned testing window last month for a couple hours to help identify problem integrations, I don't think it was an accident.