Public Status API

hgpot · March 5, 2025, 8:27pm

Does anyone know if Let's Encrypt has enabled the Public Status API feature of status.io?

The statuspage_id is easy to find, but that page does not document what URL is needed to check the public status page.

9peppe · March 5, 2025, 8:35pm

Is this useful?

generic.go

006733739


      
          var statusioSignificantStatuses = map[int]bool{
          	300: true, // Degraded Performance
          	400: true, // Partial Service Disruption
          	500: true, // Service Disruption
          	600: true, // Security Event
          }
          
          func (c statusioChecker) Check(ctx *scanContext, domain string, method ValidationMethod) ([]Problem, error) {
          	var probs []Problem
          
          	resp, err := http.Get("https://api.status.io/1.0/status/55957a99e800baa4470002da")
          	if err != nil {
          		// some connectivity errors with status.io is probably not worth reporting
          		return probs, nil
          	}
          	defer resp.Body.Close()
          
          	apiResp := struct {
          		Result struct {
          			StatusOverall struct {
          				Updated    time.Time `json:"updated"`

Osiris · March 5, 2025, 8:55pm

Wow, that API is poorly documented.. As in: nowhere?

hgpot · March 5, 2025, 9:04pm

That is perfect. I am able to pull from that link. Thank you!

We have dozens of cloud services that use various status page solutions that we pull into our own monitoring system (alongside our on-prem services). This will fit in nicely

jvanasco · March 5, 2025, 9:10pm

Many organizations hide this, because public usage can drive up their plan's cost.

Osiris · March 5, 2025, 9:28pm

But even status.io doesn't document it?

Nummer378 · March 5, 2025, 9:34pm

I should highlight that Let's Debug uses the very old status.io v1 API. It used to be documented here:

Documentation for the newer v2 API is here: Status.io API v2 · Apiary

(However, v2 is pretty different: It requires authentication for (all?) actions and uses different identifiers - I've no idea how to query letsencrypt.status.io with the v2 API)

mcpherrinm · March 5, 2025, 10:18pm

Status.io documents the following:

https://kb.status.io/developers/public-status-api/

for that above status URL.

I'm not sure how you're supposed to figure out the URL slug, except that it's the same as in the history page, Let's Encrypt Status, linked from https://letsencrypt.status.io/

9peppe · March 6, 2025, 12:28am

There's a Tom Scott video about the death of web 2.0 and its radically open APIs, it goes all the way back to Yahoo pipes.

hgpot · March 6, 2025, 5:38pm

Yep, I found that link so I knew it was possible but yes the URL slug was difficult to find, only seeing it in that GitHub link that @9peppe posted.

Assuming API v1 remains accurate and available, I don't see a need to move to an authenticated API v2.

Topic		Replies	Views
Current official status page for API? Client dev	15	6349	March 22, 2021
Status.io widget Site Feedback	5	2451	July 29, 2016
Permission for letsencrypt status page to be used in 3rd party components Feature Requests	13	1414	January 12, 2022
Let's Encrypt Undergoing Planned Maintenance Issuance Tech	4	1669	February 14, 2021
Today's outage - questions about status page update Help	7	3136	June 18, 2017

Public Status API

Related topics