Vendor reports: partial outageOpen · vendor status “ongoing”Official status API

Singapore Network Outage

Reported by Vultr · Cloud & Infrastructure · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Sep 24, 2026, 14:31 UTC
Vendor's clock
Resolved
Not yet
Still open
First seen by Statuswall
Nov 11, 2026, 02:42 UTC
Statuswall's clock
Duration
Not available
Needs both vendor times

Affected scope

sgp

From the vendor's structured data.

Potential relevance

Vultr is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

What to check on your side

Verification steps only. Statuswall cannot see your systems.

  • Check resource health in the regions named by the vendor, and in your other regions for comparison.
  • Separate control-plane actions (deploys, scaling, console) from data-plane traffic: they often fail differently.
  • If you run multi-region or failover, confirm what your own health checks report before acting.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on Vultr.
  • Look at synthetic checks and alerts that exercise Vultr.
  • Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
  • Follow the vendor's official incident page for scope changes and resolution.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Sep 24, 2026, 14:31 UTCVendor-reported startVendor time
  2. Nov 11, 2026, 02:42 UTCFirst seen by Statuswall (vendor status: ongoing)Seen by Statuswall