rewindex

CompaniesScalewayUptime

Scaleway uptime

From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.

92.11%free of major or critical incidents, last 30 days
96.82%free of major or critical incidents, last 90 days
12.24%free of any incident, last 90 days
107incidents started, last 90 days

Last 90 days, by UTC day

Aug 7 (UTC day): 0 min with a major or critical incident open, 12 h 49 min with any incident openAug 8 (UTC day): no vendor-reported incident openAug 9 (UTC day): no vendor-reported incident openAug 10 (UTC day): no vendor-reported incident openAug 11 (UTC day): 0 min with a major or critical incident open, 11 h 18 min with any incident open, 1 incident startedAug 12 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 13 (UTC day): 2 h 37 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedAug 14 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 15 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 16 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 17 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 18 (UTC day): 0 min with a major or critical incident open, 15 h 41 min with any incident openAug 19 (UTC day): 0 min with a major or critical incident open, 24 min with any incident open, 1 incident startedAug 20 (UTC day): 0 min with a major or critical incident open, 7 h 53 min with any incident open, 1 incident startedAug 21 (UTC day): 33 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedAug 22 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 23 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 24 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 25 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedAug 26 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 27 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 5 incidents startedAug 28 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 29 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 30 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 31 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 1 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 2 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedSep 3 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 5 (UTC day): 3 h 18 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedSep 6 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 7 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedSep 8 (UTC day): 8 min with a major or critical incident open, 24 h with any incident open, 4 incidents startedSep 9 (UTC day): 0 min with a major or critical incident open, 15 h 14 min with any incident open, 1 incident startedSep 10 (UTC day): 0 min with a major or critical incident open, 13 h 53 min with any incident open, 1 incident startedSep 11 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 12 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 13 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 14 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedSep 15 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedSep 16 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 17 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 18 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedSep 19 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 20 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 21 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 22 (UTC day): 0 min with a major or critical incident open, 7 h 22 min with any incident openSep 23 (UTC day): 0 min with a major or critical incident open, 4 h 9 min with any incident open, 1 incident startedSep 24 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 25 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 26 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 27 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 28 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedSep 29 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedSep 30 (UTC day): 5 h 13 min with a major or critical incident open, 24 h with any incident open, 3 incidents startedOct 1 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 2 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 3 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 5 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 6 (UTC day): 1 min with a major or critical incident open, 23 h 9 min with any incident open, 5 incidents startedOct 7 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 8 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 5 incidents startedOct 9 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 10 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 11 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 12 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 13 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 14 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 15 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 16 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 17 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 18 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 19 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 4 incidents startedOct 20 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 6 incidents startedOct 21 (UTC day): 9 h 54 min with a major or critical incident open, 24 h with any incident open, 5 incidents startedOct 22 (UTC day): 9 h with a major or critical incident open, 16 h 32 min with any incident open, 1 incident startedOct 23 (UTC day): 0 min with a major or critical incident open, 9 h 31 min with any incident open, 1 incident startedOct 24 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 25 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 26 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 4 incidents startedOct 27 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 28 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 29 (UTC day): 15 h with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 30 (UTC day): 9 h 54 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 31 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openNov 1 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openNov 2 (UTC day): 0 min with a major or critical incident open, 13 h 59 min with any incident open, 1 incident startedNov 3 (UTC day): 12 h 51 min with a major or critical incident open, 15 h 25 min with any incident open, 4 incidents startedNov 4 (UTC day): 6 min with a major or critical incident open, 6 min with any incident open

Aug 7today

no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive

Last 7 days, by hour

now

Numbers

WindowFree of major/criticalFree of any incidentOutage timeIncident timeIncidents
Last 30 days92.11%5.73%2.4 days28.3 days52
Last 90 days96.82%12.24%2.9 days79.0 days107

This is what Scaleway itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .

See the incidents: Scaleway status history · last 90 days · Scaleway status page (opens in new tab) · Markdown