api.macromeasures.com / api-new.macromeasures.com
Last updated: Wednesday, November 2, 4:45PM EST
Some issues with our Redis cluster caused 503/504 errors
when accessing the API. The problem has since been fixed. we
apologise for the inconvenience.
An unexpected network error in our database cluster resulted in
500 servers for completed requests during the duration of the
There was intermittent downtime during this period due to
faulty load-balancing settings, resulting in higher latency and
server errors for a small percentage of requests. We apologise
for the inconvenience.
The Instagram API introduced some backwards-incompatible
changes, so we had some downtime while updating our systems
in accordance with the changes. The users.json endpoint
returned "complete: false" in the response for the duration of
We added some performance improvements to our API request
handler, which required a brief downtime to be deployed. The
users.json endpoint returned "complete: false" in the response
for the duration of the outage. Everything is back up and
The users endpoint was failing for unclassified users,
returning "complete: false" in the response for the duration of
the outage. This was caused by a partial network failure in our
Amazon EC2 cluster which has since been resolved.