547796e Add API Status Check to Monitoring section
📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝README.md (+1 -0)
📄 Description
This PR adds API Status Check to the Monitoring section.
What it does:
API Status Check aggregates status pages and incident reports from 1,130+ APIs and SaaS services, including:
Container registries (Docker Hub, GitHub Container Registry, Google Container Registry)
Orchestration platforms (Kubernetes, AWS ECS, Google Cloud Run)
Cloud providers (AWS, GCP, Azure, DigitalOcean)
CI/CD tools (GitHub Actions, CircleCI, GitLab)
Monitoring tools (Datadog, New Relic, Sentry)
Why it's useful for Docker users:
DevOps teams managing containerized apps need visibility into the entire infrastructure stack. When a deployment fails or monitoring goes down, API Status Check helps quickly determine if it's an external service issue (e.g., Docker Hub outage) vs. an internal problem.
Placement:
Added alphabetically between Autoheal and cAdvisor to maintain the existing sort order.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/1264
**Author:** [@shibley](https://github.com/shibley)
**Created:** 3/9/2026
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `add-apistatuscheck`
---
### 📝 Commits (1)
- [`547796e`](https://github.com/veggiemonk/awesome-docker/commit/547796e348df1d609fe680a0bb8b8aa04ec9720c) Add API Status Check to Monitoring section
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
This PR adds **API Status Check** to the Monitoring section.
## What it does:
API Status Check aggregates status pages and incident reports from 1,130+ APIs and SaaS services, including:
- Container registries (Docker Hub, GitHub Container Registry, Google Container Registry)
- Orchestration platforms (Kubernetes, AWS ECS, Google Cloud Run)
- Cloud providers (AWS, GCP, Azure, DigitalOcean)
- CI/CD tools (GitHub Actions, CircleCI, GitLab)
- Monitoring tools (Datadog, New Relic, Sentry)
## Why it's useful for Docker users:
DevOps teams managing containerized apps need visibility into the entire infrastructure stack. When a deployment fails or monitoring goes down, API Status Check helps quickly determine if it's an external service issue (e.g., Docker Hub outage) vs. an internal problem.
## Placement:
Added alphabetically between Autoheal and cAdvisor to maintain the existing sort order.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/1264
Author: @shibley
Created: 3/9/2026
Status: ❌ Closed
Base:
master← Head:add-apistatuscheck📝 Commits (1)
547796eAdd API Status Check to Monitoring section📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
This PR adds API Status Check to the Monitoring section.
What it does:
API Status Check aggregates status pages and incident reports from 1,130+ APIs and SaaS services, including:
Why it's useful for Docker users:
DevOps teams managing containerized apps need visibility into the entire infrastructure stack. When a deployment fails or monitoring goes down, API Status Check helps quickly determine if it's an external service issue (e.g., Docker Hub outage) vs. an internal problem.
Placement:
Added alphabetically between Autoheal and cAdvisor to maintain the existing sort order.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.