No components marked as affected
Resolved
The issue was caused by a bad deploy to our graph database. We have rolled back and response times have recovered.
Investigating
We are experiencing an increase in errors on our API. We are currently investigating the issue