No components marked as affected
Resolved
This incident has been resolved. We observed the first incident of repeated responses occur on March 27th around 2pm PST, and we rolled out a fix on March 28th around 12:55pm PST.
Monitoring
We've identified the issue and have rolled out a fix. We are now monitoring the issue.