PuppyIP Resource Center
Developer Tools & Networking 5 min read Published 2026-11-18

AWS Multipath Resilience 99.999% SLA: Eligible Paths, Measurement and Credits

AWS offers a 99.999% daily uptime commitment for eligible cross-Region paths with Multipath Resilience enabled. Check your connection, Regions and traffic thresholds before relying on the SLA.

AWS Multipath Resilience Cross-Region Networking SLA

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The SLA covers cross-Region VPC peering, Transit Gateway peering attachments and inter-Region Cloud WAN core network traffic. AWS named five Regions at launch.
  • AWS measures each direction and path separately by UTC day. A minute counts only if it carries at least 250,000 packets and no single flow exceeds 1 Gbps.
  • The daily uptime target is 99.999% and the daily packet delivery target is 99.9%. Both cover qualifying minutes on the protected AWS backbone segment.
  • Credits are based on the affected path’s daily Multipath Resilience charges. The request is due by the end of the second billing cycle after the incident.

Check your cross-Region connection first

AWS announced Multipath Resilience on November 17, 2026. When enabled, AWS makes copies of packets at the backbone entrance, sends them over diverse paths and removes duplicates before exit. The service level agreement (SLA) defines AWS’s commitments for that part of the trip under specified conditions.

Supported connections include cross-Region VPC peering, cross-Region Transit Gateway (TGW) peering attachments and inter-Region traffic on a Cloud WAN core network. The launch lists US East (N. Virginia and Ohio), US West (N. California and Oregon), and Europe (Ireland). Confirm the actual Region pair, connection type and enablement status.

Locate the protected backbone segment

The protected segment runs between the Multipath Resilience facilities adjacent to the source and destination Regions. It excludes the path inside either AWS Region. Monitor in-Region components and application request outcomes separately against your application’s own availability targets.

AWS measures each direction separately. For example, traffic from N. Virginia to Oregon has a separate measurement from the reverse direction. AWS defines the measurement day as 00:00:00 through 23:59:59 UTC. Keep the original time zone for incident records and convert timestamps to UTC.

Which minutes count toward 99.999%?

A qualifying minute meets both thresholds. The directional path must carry at least 250,000 packets during that minute, and no single flow may exceed 1 Gbps. A flow is identified by the source and destination IP addresses, source and destination ports, and protocol.

Suppose a path carries 300,000 packets in a minute but one flow exceeds 1 Gbps. The minute does not qualify. In a qualifying minute, AWS counts a second as unavailable when its monitoring detects more than 10% packet loss. Under the terms, a single unavailable second takes uptime below 99.999% even if every second of the day qualifies.

Packet delivery is a separate daily measure. AWS compares delivered packets with packets sent during qualifying minutes and commits to at least 99.9% delivery. For an incident, check for unavailable seconds and the total delivery rate across qualifying minutes.

How do sending direction and connection affect cost?

The VPC pricing page describes a per-GB Multipath Resilience fee for data sent across an enabled inter-Region VPC peering connection, in addition to standard inter-Region transfer charges. Received data does not incur this add-on fee.

Use the actual source and destination Regions and direction to look up the price. Confirm Multipath Resilience rates for TGW and Cloud WAN separately because the VPC peering price applies to that connection type.

What goes in a service credit request?

Record the affected dates, direction, Regions and connection or attachment IDs, and keep redacted packet loss records. AWS confirms claims with its own network monitoring. Exclusions include problems inside a Region, customer configuration errors, disabled connections and traffic outside qualifying minutes.

Open a case in the AWS Support Center by the end of the second billing cycle after the incident. Use the subject specified in the SLA and provide the affected UTC dates, service, Regions and resource IDs. If both daily commitments are missed on the same day, the larger credit applies. The daily credit must exceed USD 1 and is based only on Multipath Resilience charges for the affected path.

Sources

Frequently Asked Questions

Can occasional heartbeat packets be used to calculate the SLA?

Only qualifying minutes count. A minute with a handful of probes falls short of the 250,000-packet threshold. Heartbeat probes can still help detect application problems. Record the production traffic volume, per-flow rate and direction to compare with the terms.

Can I request a credit based on the connection’s monthly average?

AWS measures the commitments and credits by UTC day. List affected paths for each day in the case, and use the billing cycle to determine the submission deadline.