Skip to content

Incident detail

[Containers/Functions] - [fr-par] - private endpoints might not be available

Resolved incidentMinor2 affected services

Timeline window

to

Get alerted the next time Scaleway breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    Since 14:00 UTC, on fr-par, clients might not be able to reach their container through their private endpoint. This affects only a subset of containers, and only those attached to a private network, of course.

    We are investigating. Sorry about the inconvenience.

  2. Investigating

    It seems that a few amounts of client workloads are also affected (containers that can connect to resources in the PN).

    We are still investigating.

  3. Resolved

    The incident is now resolved.

    Between approximately 14:00 UTC and 15:30 UTC in the fr-par region, a small subset of Functions and Containers connected to private networks may have been impacted.

    The following issues may have occurred:

    • Difficulty reaching the private endpoint (`<container_id>.<pn_id>.internal`) for containers only.
    • Errors when accessing resources within a private network from a Function or Container.

    We apologize for any inconvenience caused.

Keep exploring

More from Scaleway

Neighboring incidents on Scaleway's timeline and the rest of their record on OutageDeck.