Skip to content

Add API Status Check to API Monitoring section - #136

Closed
shibley wants to merge 1 commit into
yosriady:masterfrom
shibley:add-asc-mar2026
Closed

Add API Status Check to API Monitoring section#136
shibley wants to merge 1 commit into
yosriady:masterfrom
shibley:add-asc-mar2026

Conversation

@shibley

@shibley shibley commented Mar 11, 2026

Copy link
Copy Markdown

Adds API Status Check to the API Monitoring section.

API Status Check is a free real-time status dashboard for 160+ third-party APIs including AI platforms (OpenAI, Anthropic, Google Gemini, Cohere), cloud providers (AWS, Azure, GCP, Cloudflare, Vercel), payment processors (Stripe, PayPal), and developer tools (GitHub, Slack, Twilio). It offers embeddable status badges that developers can add to their documentation and applications to show real-time API status.

This is a valuable addition for developers building applications that depend on third-party APIs, complementing the existing performance monitoring and privacy control tools in this section.

@guest20

guest20 commented Mar 11, 2026

Copy link
Copy Markdown

Dupe #125 #134

Whats the point of this?

@shibley

shibley commented Mar 11, 2026

Copy link
Copy Markdown
Author

Apologies for the duplicates — closed #125 and #134. This is the only active PR.

@shibley

shibley commented Mar 20, 2026

Copy link
Copy Markdown
Author

Hi! Just a friendly bump on this PR. API Status Check monitors the real-time status of 500+ APIs — a useful addition for developers building applications that depend on third-party services. Happy to adjust the description or placement if needed. Thanks for maintaining this great list!

@shibley

shibley commented Mar 24, 2026

Copy link
Copy Markdown
Author

Hi! Checking in again — API Status Check tracks real-time uptime for 500+ major APIs including Stripe, Twilio, OpenAI, and AWS. It'd be a useful addition to the monitoring section alongside existing tools. Happy to adjust anything!

@shibley

shibley commented Jul 28, 2026

Copy link
Copy Markdown
Author

@guest20 was right, and I'm sorry it took this long to answer. This is a duplicate — I have four PRs on this repo for the same one-line entry (#125 and #134, both closed, plus this one and #196). That's my mistake and it reads as spam from the maintainer's side.

Consolidating on #196, which is the newest and cleanest. Closing this one.

I also had two contradictory numbers live in this repo at the same time — #136 said "160+ APIs" and #196 said "114+". Neither is right; I've corrected #196 against the live endpoint. Sorry for the noise.

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.

2 participants