I ran into a situation a few weeks back where I was unable to commit changes to the state. For me it was because my state had grown too large (it is limited in size... with enough size that in a typical game you should not bump up against it).
It does seem strange that it would affect multiple GMs across multiple games... but that could point to a change on the backend that lowered the allowed size of the state... or which made it easier/quicker to hit the limit.
Aaron shared some code with me that helped me pinpoint the problematic script that was bloating my storage. In your case, you might find some help from the same script -- either in the individual way each script reports its space from the state or the overall size of the state. In other words, if you and a few other GMs run this script and your overall size reports out to be the same, we might start to understand if the overall size limit has changed. Or, if you find a particular script causing bloat, we can look at why that's happening.
With Aaron's permission, I rolled his code into the ScriptInfo script (it's there in version 0.0.3). That script is currently in my repo and in the pipeline to be merged into the one-click next week. Once you have version 0.0.3 of the script, you can run:
!stateinfo
...and get a report of your state object:
At the bottom you will see a TOTAL output:
Share what you find and we might be able to zero-in on the cause.