Skip to navigationSkip to loginSkip to main contentSkip to footer section

Service Level Agreement (“SLA”) VPC Peering

This Service Level Agreement defines the different service level objectives that Scaleway undertakes to comply with in the context of the Covered Service, as well as their scope of application.

Definitions

“Covered Services”: means the “VPC Peering” service provided by Scaleway.

“Maintenance Window": means a period of time during which Scaleway performs maintenance activities on the infrastructure (physical, network or software) upon which the Covered Service is based. This includes any updates of the VPC Peering capabilities and functionalities that may involve temporary unavailability of the VPC Peering service.

“Monthly Availability Rate” or “MAR”: means the availability rate of a Covered Service for a given calendar month (expressed in percentage), determined by the following formula:

public-gw-sla-formula-en

It being specified that:

  • Tt: Total number of minutes in the relevant month (in case the Client partially runs a Resource during the course of a month, it is assumed that such Resource is 100% available for the portion of the relevant month that it was not running);
  • Tpit: Number of minutes of unavailability recorded during every Unavailability Period that occurred in the relevant month.

“NACL”: means VPC NACL (Network Access Control List) service.

“Peering connection”: means a link between two Scaleway VPCs. It allows them to route traffic between their resources. A connection is established when managers of two VPCs each create a peering connector towards the other.

“Peering connector”: means one side of a peering connection. It represents an intent to peer with another VPC.

“Private Network”: means the connection of Scaleway resources in multiple Availability Zones (AZ) within the same region, so that they can communicate with each other in an isolated and secure Layer 2 network.

“Public Cloud Resource”: means a Scaleway resource that can be attached to a VPC’s Private Network and that can route network traffic through a VPC Peering connection, such as but not limited to:

  • An Instance;
  • An Elastic Metal or Apple Silicon server;
  • A Kapsule cluster;
  • A Load Balancer.

“Resource”: means a Scaleway peering connector, attached to a Virtual Private Cloud (VPC).

“Routing”: means VPC Routing service.

“Unavailability Period”: means one (1) Public Cloud Resource attached to one (1) Private Network of the Client’s VPC cannot communicate with one (1) Public Cloud Resource attached to one (1) Private Network of a second VPC through a peering connection between these two VPCs, and all attempts to communicate with this resource are unsuccessful during a continuous period of at least one (1) minute, under the condition that the Routing and ACL services (if enabled) applied to each of these VPCs would enable the communication between these two (2) resources under normal conditions.

Being specified that the following events shall in no circumstances be considered as an Unavailability Period:

  • Any unavailability that occurs during a Maintenance Window;
  • Any intermittent unavailability lasting less than one (1) complete minute;
  • Any problems (misconfiguration, failure or connectivity problem) related to the VPC the Client’s VPC is peering with.

“VPC Peering”: means a networking service that enables two Scaleway VPCs to establish a private peering connection and route traffic between their resources.

“VPC Resource” or “VPC”: means a Virtual Private Cloud resource.

Service Level Objectives “SLO”

Scaleway undertakes to comply with the following Service Level Objectives:

Covered ServiceMonthly Availability Rate
VPC Peering99.90%

The SLO described hereinabove shall in no circumstances apply to any components under Client's control, such as, but not limited to, any software and/or applications installed and used by the Client in connection with the Services.

Compensation

In the event Scaleway does not comply with the SLO described hereinabove during a given calendar month, the Client is entitled to request a compensation, it being specified that : (i) the Client shall have paid all invoices issued by and due to Scaleway in connection with the Services, (ii) the Client shall have notified Scaleway of the non-respect of the SLO within the specified time limit, and (iii) the Client shall cooperate in good faith with Scaleway to resolve the issue, in particular:

  • by remaining available during the entire period necessary for resolving the issue encountered;
  • by providing all the information reasonably available to the Client regarding the issue encountered;
  • by carrying out any verification that may reasonably be necessary to resolve the issue encountered.

It is expressly agreed that the compensation granted by Scaleway constitutes an all-inclusive payment for all damages resulting from Scaleway’s failure to comply with the SLO and that the Client expressly waives its right to any other claim, complaint or action.

The compensation shall take the form of a voucher which shall be applied by Scaleway on the invoice issued for the Public Cloud Resources impacted, following the month during which the Client’s request was issued.

The amount of the compensation granted by Scaleway is determined according to the following table and corresponds to a percentage of the monthly amount invoiced to the Client for the Resources that did not comply with the SLO during a given month. The Client acknowledges that this compensation cannot under any circumstances be reimbursed in cash.

Monthly Availability Rate (“MAR”) Compensation
in the form of a percentage (%) of the
monthly amount invoiced to the Client for the
Resources that did not comply with the SLO
99.0% < MAR < SLO 10%
95.0% < MAR < 99.0% 25%
MAR < 95.0% 50%

Request for compensation

Client’s request for compensation must be issued via support ticket no later than thirty (30) days following the month during which the applicable Resources did not comply with the SLO. Failing that, no compensation can be claimed by the Client with respect to such breach of the SLO.

In addition to its request, the Client must provide Scaleway with the server log files indicating the Unavailability Periods of the impacted Resources as well as the date and time at which they occurred. Client’s failure to comply with these requirements may result in the withdrawal of its right to compensation. In the event of a dispute regarding this SLA, Scaleway will take a decision in good faith based on the information provided by the Client as well as its own system logs, monitoring reports, configuration records and any other available information.

Maximum compensation

The total amount of compensation granted by Scaleway over the course of a given calendar month shall under no circumstances exceed fifty percent (50%) of the monthly amount invoiced to the Client for all the Public Cloud Resources impacted by the Covered Services that failed to comply with the SLO during the course of such month.

Exclusions

No compensation shall be granted to the Client if the failure to comply with the SLO is due to any of the following reasons:

  • Force Majeure events;
  • Act of a third party;
  • Client’s fault or wrongful acts;
  • Failure of the Client to fulfil its contractual obligations;
  • Unavailability of the Services occurring during a Maintenance Window;
  • Unavailability of the VPC Peering API used to create, list, update and delete VPC Peering connectors resources;
  • Misuse (or improper use) of the Services by the Client, such as but not limited to: misconfiguration of the Covered Service, misconfiguration of VPC, Routing or NACL services;
  • Any connectivity problems beyond the Client’s VPC Peering connector, such as but not limited to: a network misconfiguration, or failure, or connectivity problem on the VPC the Client’s VPC Peering connector is peering with.
  • Suspension of the Services pursuant to the General Terms of Services or the applicable Specific Conditions;
  • Failure of the Client to cooperate in good faith with Scaleway to restore the availability of the Resources;
  • Services or functionalities in Beta test phase or which have not been made available in a “General Availability” phase;
  • Services or functionalities for which there are no SLO explicitly described in the SLA.