DigitalOcean incident: Network Connectivity from India to NYC

Affected components

• NYC1

1. resolvedJul 24, 2026, 12:42 UTC

   Between 07:46  UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP. Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources. We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.

2. monitoringJul 24, 2026, 11:45 UTC

   We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.

3. identifiedJul 24, 2026, 10:36 UTC

   We have noticed ​​​​​​​network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in DigitalOcean's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Render: Service Disruption in OregonCritical · Jul 24, 2026, 11:16 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage S3 Standard Incident NotificationMajor · Jul 23, 2026, 19:14 UTC
• Grafana Cloud: Errors creating new Slack integration for Grafana IRMMajor · Jul 24, 2026, 09:17 UTC
• npm: Publish and Install failuresMajor · Jul 24, 2026, 11:08 UTC
• Notion: Notion is downMajor · Jul 24, 2026, 11:24 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• dbt Cloud: Scheduled jobs are intermittently affected by job failures caused by 403 errorMinor · Jul 24, 2026, 07:58 UTC
• Akamai: Edge Delivery IssuesMinor · Jul 24, 2026, 12:21 UTC
• ReadMe: Degraded performance due to third-party infrastructure issuesMinor · Jul 24, 2026, 12:22 UTC
• Mailgun: Route delays in EU RegionMinor · Jul 24, 2026, 12:27 UTC

How often does DigitalOcean have incidents?

DigitalOcean reported 20 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 5h 35m. See DigitalOcean's uptime and incident history