2019-10-17
An issue with a caching server caused some API responses to return error messages instead of cached responses.
Roughly one third of HTTP requests for certain API routes would have received an error instead of the expected response. This would have affected several distinct services and applications, mostly involving consumer facing equipment.
A hard disk on one of a set of servers in a caching layer in front of our API servers malfunctioned, which caused that server to respond to HTTP requests with errors instead of cached responses.
The server with the problematic hard disk was replaced with a server with a properly functioning hard disk.