GlobalOutageMap
← Live dashboard
Linode logoLinode

Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Jun 30, 2026, 06:54 PM · Resolved Jun 30, 2026, 11:22 PM

On June 30, 2026, between approximately 17:30 UTC and 21:45 UTC, users may have experienced connection timeouts and errors related to the Block Storage service in Singapore Expansion, SP \(sg-sin-2\). The issue began when one host in the cluster was taken down for maintenance while another host unexpectedly encountered network issues. A configuration issue also contributed to the impact. These factors led to a degraded state that affected performance and, to a limited extent, data availability. We mitigated the impact to customers at 21:45 UTC on June 30, 2026 by correcting the network,...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

SG-SIN-2 (Singapore 2) Block Storage

Updates (7)

  1. Jul 2, 2026, 04:29 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    On June 30, 2026, between approximately 17:30 UTC and 21:45 UTC, users may have experienced connection timeouts and errors related to the Block Storage service in Singapore Expansion, SP \(sg-sin-2\). The issue began when one host in the cluster was taken down for maintenance while another host unexpectedly encountered network issues. A configuration issue also contributed to the impact. These factors led to a degraded state that affected performance and, to a limited extent, data availability. We mitigated the impact to customers at 21:45 UTC on June 30, 2026 by correcting the network, confi

    Linode ↗
  2. Jun 30, 2026, 11:22 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    We haven’t observed any additional issues with the Block Storage service in Singapore Expansion, SP (sg-sin-2), and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

    Linode ↗
  3. Jun 30, 2026, 10:10 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

    Linode ↗
  4. Jun 30, 2026, 09:36 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    We are continuing to work on a fix for this issue.

    Linode ↗
  5. Jun 30, 2026, 08:36 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    Our team has identified the issue affecting the Block Storage service in our Singapore Expansion, SP (sg-sin-2) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    Linode ↗
  6. Jun 30, 2026, 07:55 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    We are continuing to investigate this issue.

    Linode ↗
  7. Jun 30, 2026, 06:54 PM
    Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)

    Our team is investigating an emerging issue affecting the Block Storage service in our Singapore Expansion, SP (sg-sin-2) data center. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.