I've temporarily removed Testflume from our API Status page, marking the incident resolved though the component remains down. Since there's no way to filter out that component, as has been raised many times across the forum, this seems the most reasonable way to remove the ambiguity from the letsencrypt.status.io page.
We'll add Testflume back to the status page in the future, when it makes sense to do so.