Last checked
Container platform for accelerated application development and deployment.
Experiencing an issue?

Docker宕机了吗?
Degraded performance
Share your experience to help others stay informed.
Official status checked
Docker is experiencing issues
Official provider statusOfficial incident active
Maintenance: Scheduled database maintenance — Status: Complete Repos db is now in version 17.11 Affected components Docker Hub Automated Builds (Operational) Docker Hub Registry (Operational) Docker Hub Web Services (Operational) Docker Package Repositories (Operational)
Official provider statusOfficial maintenance active
Maintenance: Migrating to incident.io Status Pages — Status: Complete What's changing? On 8/25, we will migrate our status page to incident.io: http://incident.io Status Pages. This migration is part of our ongoing efforts to improve incident response, on-call management, and reliability communication. With incident.io: http://incident.io, we're bringing incident response, on-call management, and post-incident reviews into a single platform, so you get faster and more consistent updates during incidents. What you need to know • Our status page URL remains the same: you can still access it at : https://dockerstatus.com/https://dockerstatus.com. • Email subscribers will be automatically migrated to the new status page. No action needed. • A new RSS subscription option will be available to subscribers. • Slack subscriptions will need to be re-added after the migration to keep receiving updates. • Webhook subscription options will no longer be available. What you need to do • If you're subscribed via Email: • You'll be automatically migrated. No action required. • If you're subscribed via Slack: • Confirm the migration is complete by checking for "Powered by incident.io: http://incident.io" at the bottom of : https://dockerstatus.com/https://dockerstatus.com. • Re-subscribe your Slack workspace to keep receiving updates. • If you're subscribed via Webhook: • Wait until after the maintenance window is complete. • Choose an alternative subscription option: Email, Slack, or RSS. If you have questions or issues, reach out to our Support team: https://hub.docker.com/support/contact Thanks for your patience as we make this change. Affected components Docker Authentication (Operational)
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Unknown | ||
| 0m | Yes | Unknown | ||
| 668h 32mOngoing | Yes | Unknown | ||
| 0m | Yes | Minor | ||
| 0m | Yes | Major | ||
| 0m | Yes | Minor | ||
| 0m | Yes | Unknown | ||
| 0m | Yes | Minor |
Uptimus 通过官方状态源监控 Docker,并将事件、维护和组件健康状况统一为一致的服务状态。
此页面目前包含 21 个受监控组件、42 个事件、1 个维护窗口和 9 天已知历史。
Uptimus 是独立监控服务,与 Docker 无关联。健康状态并不保证每位用户、设备或地区都未受影响。
当 Docker 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。 可用历史包含 42 个事件,为提醒提供当前状态之外的背景。 最近收录的事件是“Degraded performance and intermittent availability on Docker Hub”。
接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Docker 的 21 个组件: Docker Authentication, Docker Hub Registry, Docker Hub Web Services, Docker Package Repositories。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。
Planned work published by the official provider.
Status: Complete What's changing? On 8/25, we will migrate our status page to incident.io: http://incident.io Status Pages. This migration is part of our ongoing efforts to improve incident response, on-call management, and reliability communication. With incident.io: http://incident.io, we're bringing incident response, on-call management, and post-incident reviews into a single platform, so you get faster and more consistent updates during incidents. What you need to know • Our status page URL remains the same: you can still access it at : https://dockerstatus.com/https://dockerstatus.com. • Email subscribers will be automatically migrated to the new status page. No action needed. • A new RSS subscription option will be available to subscribers. • Slack subscriptions will need to be re-added after the migration to keep receiving updates. • Webhook subscription options will no longer be available. What you need to do • If you're subscribed via Email: • You'll be automatically migrated. No action required. • If you're subscribed via Slack: • Confirm the migration is complete by checking for "Powered by incident.io: http://incident.io" at the bottom of : https://dockerstatus.com/https://dockerstatus.com. • Re-subscribe your Slack workspace to keep receiving updates. • If you're subscribed via Webhook: • Wait until after the maintenance window is complete. • Choose an alternative subscription option: Email, Slack, or RSS. If you have questions or issues, reach out to our Support team: https://hub.docker.com/support/contact Thanks for your patience as we make this change. Affected components Docker Authentication (Operational)
Started 2026年8月25日 UTC 20:31 · Ongoing
Downdetector 公共页面主要基于用户报告。Uptimus 还会在来源提供时结合官方事件、维护窗口和组件状态。
| 比较标准 | Uptimus | Downdetector |
|---|---|---|
| Docker 的社区中断报告 | 已包含 | 已包含 |
| 区分个别报告和大范围中断的自适应基线 | 已包含 | 已包含 |
| 24 小时报表活动和区域中断视图 | 已包含 | 已包含 |
| 在一个工作区管理网站、状态提供商、Steam 游戏及 Android 应用和游戏 | 已包含 | 独立产品 |
| 从同一工作区发送邮件、推送和 Webhook 告警 | 已包含 | 独立产品 |
| Docker 的官方事件更新和状态时间线 | 已包含 | 以用户报告为主 |
| 分别展示组件健康与维护窗口 | 已包含 | 公共页面功能有限 |
The official status page for Docker reports normal operation. An unresolved official incident is listed: “Maintenance: Scheduled database maintenance”. 0 reports were recorded for Docker in the last 24 hours. Last official check: .
分享您对 Docker 的看法
成为第一个评论的人!
发现其他流行服务及其当前状态
评价此服务
暂无评价