Live / Scaleway / Incident
Scaleway: [BILLING] - Billing consumptions in November are not up-to-date
Scaleway · scaleway.comResolved2026-11-03 07:54 UTC
Public — what happened
Summary
Scaleway said that usage figures for November were not current in its billing console and billing APIs. The company posted about the problem at 14:42 UTC on 2026-11-02 and said it was working on a fix. It did not state a cause. On 2026-11-03 at 07:54 UTC Scaleway reported the situation was resolved, saying things returned to normal around 7:30 Paris time.
Affected
Billing
Timeline
- Started — 2026-11-02 14:42 UTC
- Investigating — 2026-11-02 14:42 UTC
- Resolved — 2026-11-03 07:54 UTC · 17h 12m after it started
What SquidGrid measured
SquidGrid measured 277 internet paths into Scaleway’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Scaleway against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Scaleway: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Scaleway report →
More from Scaleway
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.