api.macromeasures.com / api-new.macromeasures.com
OK

Last updated: Wednesday, November 2, 4:45PM EST

Recent outages

Wednesday, November 2, 2:45AM EST — 4:45PM EST (two hours)
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.
Monday, September 5, 6:35AM EST — 10:40AM EST (four hours)
An unexpected network error in our database cluster resulted in 500 servers for completed requests during the duration of the outage.
Tuesday, August 30, 2:00PM EST — 4:00PM EST (two hours)
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.
Wednesday, June 1, 1:16PM EST — 2:16PM EST (one hour)
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 the outage.
Wednesday, May 18, 2:53PM EST — 2:54PM EST (one minute)
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 running now.
Saturday, April 30, 1:25PM EST — 2:25PM EST (one hour)
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.