API issue identified - 20160302 15:30 GMT

Resolved
{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}
After 31 minutes

This incident has been resolved.

{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}
After 17 minutes

Our engineers have determined the cause of the API latency. A server was in a degraded state leading to higher than normal latency. The issue has been correct and we will continue to monitor the situation.

{:closed=>"Closed", :complete=>"Complete", :false_alarm=>"False Alarm", :identified=>"Identified", :investigating=>"Investigating", :open=>"Open", :recovering=>"Recovering", :resolved=>"Resolved", :scheduled=>"Scheduled", :underway=>"Underway"}

Our monitoring systems have alerted our engineers that clients are experiencing latency and timeouts connecting to Vevo’s API. Engineers are investigating and will send an update in ten minutes.

Began at: