Skip to content

Add API Status Check to API Monitoring - #196

Open
shibley wants to merge 2 commits into
yosriady:masterfrom
shibley:add-apistatuscheck
Open

Add API Status Check to API Monitoring#196
shibley wants to merge 2 commits into
yosriady:masterfrom
shibley:add-apistatuscheck

Conversation

@shibley

@shibley shibley commented Jun 22, 2026

Copy link
Copy Markdown

Adds API Status Check to the API Monitoring section.

A live dashboard tracking the real-time operational status of 114+ cloud services and APIs — AWS, GitHub, Stripe, OpenAI, Vercel, Cloudflare, Twilio, and more — useful for developers diagnosing whether an outage is on their side or an upstream provider's.

@shibley

shibley commented Jul 23, 2026

Copy link
Copy Markdown
Author

Friendly bump on this one — API Status Check is a free real-time uptime dashboard for OpenAI/Anthropic/major API providers, which fits well alongside the other monitoring tools in this section. Happy to make any changes needed to help it merge. Thanks for maintaining this list!

@shibley

shibley commented Jul 28, 2026

Copy link
Copy Markdown
Author

Housekeeping + a correction on my own entry.

Housekeeping: I had four PRs open/closed on this repo for this same one-line addition (#125, #134, #136, and this one). @guest20 flagged that on #136 back in March and I never answered — my fault. I've now closed #136 with an apology and consolidated everything here. This is the only one.

Correction: the description said "114+ cloud services." That was wrong. Verified unauthenticated against the live endpoint just now:

$ curl -s https://apistatuscheck.com/api/status | jq '{count, categories: (.categories|length), lastUpdated}'
{
  "count": 285,
  "categories": 29,
  "lastUpdated": "2026-07-28T15:06:39.891Z"
}

Updated to 285 APIs across 29 categories, and I mention the public /api/status JSON endpoint since that's the part likely to be useful to readers of an API-devtools list.

One thing I'd rather state than have you discover: of those 285, 61 are resolving a live status right now (55 up, 6 degraded) and 224 return unknown — coverage is uneven by category, and the dashboard shows that honestly rather than defaulting everything to green. If you'd prefer the entry to say "285 tracked, live status for a subset," I'll reword it that way.

I maintain the site; disclosing that. If API Monitoring isn't the right section, or you'd rather not carry it at all, say the word and I'll close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant