Degraded / minor incident Scaleway status
scaleway.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Scaleway's status page shows “Degraded / minor incident” in fr-par-1 and Apple Silicon; the vendor is identified the cause. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: normal.
- Vendor status page Degraded / minor incident · 6 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS12876 prefixes seen by 100% of RIPE RIS peers
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: fr-par-1, Apple Silicon, Transactional Email
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 30 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 5 h 38 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: identified the cause on “[APPLE SILICON] - FR-PAR-1 - Macs cannot reach Scaleway public API”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- AS12876 prefixes seen by 100% of RIPE RIS peers. evidence confidence: medium
What we don't know: what is happening inside Scaleway's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “identified the cause”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: normal. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Scaleway. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Scaleway, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; routing visibility returning to normal; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Scaleway. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
[APPLE SILICON] - FR-PAR-1 - Macs cannot reach Scaleway public API
major identified · started
3 updates
- investigating
Apple Silicon on par1 cannot reach the public scaleway API. This impacts some workflows on the macs and customers should avoid triggering a reinstall or a reboot for the time being.
- identified
The problem has been identified. Problem is located on the network devices to which the MACs are connected. A fix has been found and tested yesterday evening. The fix will be pushed in fr-par-1 globally. However, a reboot (approx 10 to 15 minutes) of the network device is required. We are currently planning how we'll proceed to reduce your impact as much as possible.
- identified
3 maintenance operations are planned for the next week in order to solve the issue globally. - Monday the 23rd from 7am to 9am. - Tuesday the 24th from 7am to 9am. - Wednesday the 25th from 7am to 9am. During this planned maintenance, a loss of connectivity due to a reboot of the network equipment could be observed on the Mac Minis (it should not be more than 30 minutes, and each Mac should only be affected once)
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.