#March 24: GraphQL timeouts (21:04UTC)

We called an incident due to elevated errors through our GraphQL API, where requests were timing out when talking to our primary database. All errors were coming from a single machine in IAD, where the physical host for that machine seemed to be misbehaving and couldn’t hold a connection, so it earned itself a reboot. The host and its machines were behaving once it came back up, and everything seems fine, but this is a server we’re going to squint at with suspicion if it misbehaves in the future.