Noko incident

Increased API latency

Minor Resolved View vendor source →

Noko experienced a minor incident on March 24, 2016, lasting 3h 10m. The incident has been resolved; the full update timeline is below.

Started
Mar 24, 2016, 10:55 AM UTC
Resolved
Mar 24, 2016, 02:06 PM UTC
Duration
3h 10m
Detected by Pingoru
Mar 24, 2016, 10:55 AM UTC

Update timeline

  1. investigating Mar 24, 2016, 10:55 AM UTC

    We're seeing some slow-downs in processing API requests. The API is still functioning fully, but response times are slow for some types of API calls.

  2. resolved Mar 24, 2016, 02:06 PM UTC

    The underlying reason of API latency was an API client issuing too many requests for large sets of entries. As a temporary fix we've reached out to the affected customer and they've reduced the amount of requests issued. In the longer term, we're working on better caching for the more popular API methods; this will all but eliminate latency issues like this one.