正常

DigitalOcean 是不是挂了?

DigitalOcean 运行正常。 DigitalOcean 向开发者出租云服务器、数据库与 Kubernetes。

2026年10月18日的 DigitalOcean 状态:02:09 UTC 读取自官方状态页,最多每 5 分钟刷新一次。

近 90 天

97.25%
估算可用率
90 天前今天

根据 DigitalOcean 公布的事件推算,属于估算,不是实测值。

DigitalOcean 近 90 天稳定性

17报告事件数
0完全中断
4 h 2 min典型时长
25 h 50 min最长事件

最近一次事件:“DNS Resolution for Managed Kubernetes”,6 天前。

组件

API正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Global正常
Agent Runtime正常
ATL1正常
Amsterdam正常
AMS3正常
AMS3正常
AMS3正常
AMS3正常
AMS3正常
Billing正常
AMS2正常
AMS2正常
AMS2正常
AMS2正常
AMS2正常
AMS2正常
AMS2正常
AMS3正常
ATL1正常
Inference正常
MKC1正常
AMS3正常
AMS3正常
AMS3正常
BLR1正常
AMS3正常
AMS3正常
AMS3正常
AMS3正常
BLR1正常
ATL1正常
ATL1正常
ATL1正常
ATL1正常
Atlanta正常
BYOIP正常
ADK正常
MKC1正常
RIC1正常
Bangalore正常
FRA1正常
BLR1正常
FRA1正常
FRA1正常
BLR1正常
Cloud Control Panel正常
BLR1正常
NYC2正常
ATL1正常
ATL1正常
ATL1正常
ATL1正常
ATL1正常
ATL1正常
ATL1正常
Knowledge Bases正常
Frankfurt正常
BLR1正常
BLR1正常
NYC3正常
BLR1正常
FRA1正常
BLR1正常
FRA1正常
BLR1正常
LON1正常
FRA1正常
BLR1正常
BLR1正常
Cloud Firewall正常
LON1正常
Guardrails正常
RIC1正常
FRA1正常
FRA1正常
LON1正常
FRA1正常
FRA1正常
FRA1正常
FRA1正常
LON1正常
FRA1正常
Community正常
TOR1正常
SFO2正常
Model Services正常
MKC1正常
MKC1正常
Kansas正常
MKC1正常
LON1正常
London正常
SFO3正常
LON1正常
LON1正常
LON1正常
LON1正常
NYC3正常
LON1正常
LON1正常
NYC3正常
NYC1正常
DNS正常
MKC1正常
MKC1正常
SGP1正常
NYC1正常
SFO3正常
NYC1正常
Support Center正常
New York正常
RIC1正常
RIC1正常
MKC1正常
MKC1正常
MKC1正常
MKC1正常
MKC1正常
MKC1正常
MKC1正常
NYC1正常
NYC1正常
SYD1正常
NYC1正常
NYC3正常
NYC1正常
NYC1正常
NYC2正常
SGP1正常
SFO3正常
NYC1正常
NYC1正常
Reserved IP正常
SFO2正常
Richmond正常
San Francisco正常
NYC2正常
NYC2正常
NYC2正常
NYC2正常
NYC2正常
SFO3正常
NYC2正常
NYC2正常
NYC3正常
SGP1正常
SYD1正常
WWW正常
RIC1正常
Singapore正常
NYC3正常
NYC3正常
NYC3正常
NYC3正常
SGP1正常
NYC3正常
NYC3正常
TOR1正常
NYC3正常
SYD1正常
SFO2正常
SFO2正常
Sydney正常
SFO3正常
SYD1正常
SFO3正常
RIC1正常
RIC1正常
RIC1正常
RIC1正常
RIC1正常
RIC1正常
RIC1正常
Toronto正常
SGP1正常
SGP1正常
SGP1正常
SFO1正常
SFO1正常
SFO1正常
SFO1正常
SFO1正常
SFO1正常
LON1正常
SYD1正常
SYD1正常
SFO2正常
SFO2正常
SFO2正常
SFO2正常
SFO2正常
SFO2正常
SFO1正常
SFO3正常
SFO3正常
SFO3正常
TOR1正常
SFO3正常
TOR1正常
SFO3正常
SFO3正常
SFO2正常
SGP1正常
SGP1正常
SGP1正常
SGP1正常
SGP1正常
SGP1正常
SFO3正常
SYD1正常
SYD1正常
SYD1正常
SYD1正常
SYD1正常
SYD1正常
SYD1正常
TOR1正常
TOR1正常
TOR1正常
TOR1正常
TOR1正常
TOR1正常
TOR1正常
CSPM正常

近期事件

App Platform Deployments

Between 04:34 and 12:15 UTC, customers experienced service interruptions affecting App Platform deployment operations. During this window, customers may have been unable to deploy new applications or scale existing deployments. Applications already running prior to the incident were unaffected and continued to operate normally. The disruption was caused by a software update that prevented application containers from starting on newly provisioned infrastructure nodes. Our Engineering team rolled back the update and restored the affected nodes. App Platform deployment and scaling operations have recovered and are operating normally. We sincerely apologize for any inconvenience this caused. If you continue to experience any issues, please open a support ticket and our team will be happy to assist you.

DNS Resolution for Managed Kubernetes

降级

Our Engineering team has resolved the external DNS resolution failures affecting Managed Kubernetes across multiple regions. Applications running on Managed Kubernetes can now resolve external domain names. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience problems, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/

VPC Networking Availability

降级

Our Engineering team fully resolved the VPC Networking disruption as of 10:29 UTC. Customers can now create and delete VPC peering connections, subnets, and routes as expected. Following the recovery, we monitored the affected systems and confirmed that VPC Networking operations remain stable. We apologize for any inconvenience this disruption may have caused. If you continue to experience unexpected behavior, please open a ticket with our Support team for further assistance.

A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)

From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation. We apologize for the disruption and its impact on your work. If you continue to experience unexpected behavior, please open a support ticket so our team can investigate and assist you.

Support Portal Service Disruption

降级

From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. Our Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience.

常见问题

DigitalOcean 现在是不是挂了?

DigitalOcean 官方状态页显示:All Systems Operational。本页每次打开时会重新读取,最多每 5 分钟一次。

DigitalOcean 上一次故障是什么时候?

DigitalOcean 最近一次报告的事件是“DNS Resolution for Managed Kubernetes”,发生在6 天前(2026-10-11 22:01 UTC)。近 90 天的事件中没有完全中断。

这里跟踪了 DigitalOcean 的哪些部分?

DigitalOcean 的状态页列出 239 个组件,包括 API, Global, Global, Global, Global。每次页面刷新都会重新读取。

DigitalOcean 挂了我该怎么办?

暂停依赖它的部署,等恢复后重试或补跑失败的任务,并看看镜像或缓存能否临时顶上。

Droplet 还在跑,但没法新建或调整规格?

Cloud Control Panel 和 API 与 Droplet 本身是独立组件。控制面故障只会挡住新操作,不会影响已经在运行的机器。

状态页说只有 AMS3 受影响,我 NYC3 的 Droplet 没事吧?

没事——DigitalOcean 按数据中心报告。每个区域的 Droplet、卷和 Kubernetes 都是单独一行,AMS3 的事件不波及别的区域。

怎么判断 DigitalOcean 是所有人都打不开,还是只有我这边有问题?

如果上面显示运行正常但 DigitalOcean 对你仍然不可用,问题多半在你这边:换个网络、清除缓存,或检查自己的网络连接。如果显示降级或故障,说明其他人也受到影响。

我自己的网站挂了,怎么第一时间收到通知?

OpenUptime 每分钟检查一次你的网站,一旦无响应就通过 Slack、Telegram、邮件或 Webhook 告警。它是开源的,可以免费开始使用。