This incident has been resolved.
The issue was a result of a code push to our production environment that introduced error messages for users making valid API requests.
A very small percentage of Assistants API requests made during the relevant time period did not successfully post.