Monitoring - These 504s were the result of heavy traffic coming in from our api/v2 endpoints. We have identified and fixed an issue that should address this traffic and we will continue to monitor performance across the app.
Sep 13, 09:52 PDT

Monitoring - We've identified and fixed a configuration issue with our backend services. Some services would shut down if they were unable to connect to a node on our log aggregation cluster. Last night, one of our log nodes died and as traffic (and log volume) peaked this morning we began to see erratic behavior across our infrastructure. Users experienced intermittent periods of timeouts and degraded performance.

We'll continue to monitor performance and work to fill gaps in our metrics and alerting to mitigate issues like these in the future. We'll follow up with a public postmortem later this week.
Sep 12, 13:09 PDT

Monitoring - We've mitigated the impact of some abnormal API traffic. We're continuing to monitor our system and investigate the root cause.
Sep 11, 17:29 PDT

Monitoring - Today we experienced intermittent issues with API v2. This would have impacted customers using V2 of our API, and those loading the suggestions grid in the admin console. End users would not have been affected.

We do have a fix in place, and are monitoring it closely. We will post a post mortem with more details once this is resolved.

We are sorry for the delay in getting our status page updated with the issue, and for how this impacted using our product!
Sep 11, 14:13 PDT