https://letsencrypt.status.io/ has oak.ct.letsencrypt.org and sapling.ct.letsencrypt.org which are no more.
portal.letsencrypt.org and portal-staging.letsencrypt.org is also no more.
More curiously these 4 systems are still showing green on the status page even when they have been taken down. so I wonder what is the status page monitoring?
The portal still exists as far as I know - it's used for account unpause URLs. You need a special link from your ACME client (with a JWS) to use it, otherwise the page won't have anything to show to you.
The Let's Encrypt Oak CT log is also still running: Oak 2025h2 and 2026h2 are still serving read-only requests. You can't write to them any more, but they're still happily serving requests. I haven't looked at sapling specifically, but I presume it's the same thing there. So given that the endpoint exists and responds to requests, having it in the status page is fine IMHO.
And for why it shows no exsit things as operational see this
Thanks for the heads up. We'll look at this today and come up with a plan.
Thanks for the info about the portal.
https://oak.ct.letsencrypt.org/2025h2/ and https://oak.ct.letsencrypt.org/2025h1/ were returning 404 so I assumed they were taken down.
Sorry to give you more work. But maybe its time to add the new logs to the status.io page.
Yeah you need to query one of the RFC6962 endpoints for the logs to return anything non-404.
We are in the process of deleting remaining Sapling infrastructure today, and have deleted the Status.io component as part of that process.
Oak and Portal both still exist and are up, so they'll remain.
We'll follow up making sure our new logs are added to the public status page as well.