DigitalOcean Services Status

IPv6 Connectivity in Multiple Regions

Incident Report for DigitalOcean

Resolved

Our Engineering team has confirmed that the IPv6 connectivity issue has been fully resolved across all regions. Users should no longer face IPv6 connectivity issues. If you continue to experience problems, please open a ticket with our support team. Thank you for your patience and we apologize for any inconvenience.
Posted Oct 17, 2025 - 04:28 UTC

Monitoring

Our Engineering team has implemented the fix to resolve the IPv6 networking issues in multiple regions. Users should no longer have issues connecting to via IPv6 to their Droplets.

We will continue to monitor the situation, and we will post an update once we've confirmed complete resolution.
Posted Oct 17, 2025 - 03:56 UTC

Identified

Our Engineering team has identified the issue and are implementing a fix. Our team has resolved the IPv6 connectivity issue in FRA1 and are monitoring the situation.

In addition, it was discovered that the NYC1, and SFO2 regions were affected by this issue as well, and our team is currently working to resolve the issue in those regions. To summarize, users in the regions of AMS2, SGP1, NYC1, and SFO2 may still experience connection issues via IPv6.

We are rapidly working on a fix. We will share more information once available.
Posted Oct 17, 2025 - 02:52 UTC

Update

While investigating this issue, our Engineering team has noticed that the issue is occurring in SGP1 as well. Users in SGP1 may also experience IPv6 connectivity issues at this time.

We are working to resolve this issue as quickly as possible. We will post updates as soon as we have more information.
Posted Oct 17, 2025 - 00:44 UTC

Investigating

Our Engineering team is investigating an issue affecting IPv6 connectivity in FRA1, and a small subset of users in AMS2. At this time, users may experience issues connecting to IPv6-enabled resources.

We apologize for the inconvenience and will share an update once we have more information.
Posted Oct 17, 2025 - 00:19 UTC
This incident affected: Networking (AMS2, FRA1, NYC1, SFO2, SGP1).