Usage patterns pushed us to capacity and after some debugging the query pattern ended and durations settled to normal.
As this event calmed down we doubled the capacity of our query processing API and increased backend query workers by 33% in hopes of preventing further slowdowns. We're also continuing to work on an internal rate limiting problem to prevent this from occurring.
We apologize for the inconvenience and appreciate you bearing with us during these problems!