We've ruled out several potential causes internally and have confirmed that this appears to be an issue within the Meta API. We're continuing to monitor error rates and will update as more information becomes available.