Are you Twitter folks aware that the API has been kicking up a huge
dust storm of 502s on all API calls, beginning somewhere on January
4th, and still continuing at time of writing (11:00 AM EST)?

Reply via email to