rewindex

CompaniesScalewayIncidents

Scaleway: [AMS] There was no ipv6 connectivity for some instances in ams1

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.scaleway.com (opens in new tab)

Timeline of updates

  1. resolved

    For some Instances in ams1 didn't have ipv6 connectivity for about 24 hours. Impacted clusters: cl21, cl22, cl23, cl24, cl25, cl26 This has been resolved on our side.

From Scaleway’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.scaleway.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Scaleway, started 2023-01-30 14:00 UTC, resolved after 0 min, 1 update(s).

Title
[AMS] There was no ipv6 connectivity for some instances in ams1
Vendor
Scaleway
Date
URL
https://rewindex.com/company/scaleway/incidents/q556dqzc8j5g

Scaleway profileRecent Scaleway incidentsAll outages on January 30, 2023Scaleway in January 2023MarkdownJSON