fshy

Home / OVHcloud

OVHcloud Public Cloud (paid)

us.ovhcloud.com/public-cloud/prices/Paid VM with included trafficegress/ovhcloud-public-cloudJSONcomparereport an errorprovider JSON

Free allowance
Incoming traffic Included.
Verdict
paidno free allowance; listed for its price
Cost
free tier
Identity
cardcard required, no phone
Binding limit
noneno named constraint binds
Evidence
documented2 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
Free tierIncoming traffic Included. Outgoing traffic Included.
unit unlimited; metered on downloaded-bytes
Pricepaid; traffic included
Limits
  • volume-quota outgoing traffic is Included rather than metered, with no stated cap source
Bindingnone no byte meter is published: outbound is included in the hourly instance price, so what a reader pays is the instance and not a quota
Identitycard an account with a payment method; every Start link on the price page carries a FREETRIAL voucher parameter whose value is not stated on the page
Egressincoming and outgoing traffic are both listed as Included, with no byte figure and no overage line on the price page; ingress: udp
free allowance: none published
Interfacecli, rest the OpenStack CLI and the OVHcloud API
Toolingwg-quick on the instance; the OpenStack CLI or the OVH API
Composes witha paid instance whose egress line is Included removes the credit question entirely; pair it with the FREETRIAL voucher to start at no cost
NotesThe strongest non-credit finding and the one that changes what the question is: if outgoing traffic is Included on a paid instance, then no credit arithmetic is needed at 1 TiB a month, and the cheapest OVH instance is the answer rather than any trial. Arithmetic is not applicable: with no per-GB rate there is nothing to divide. Left unstated because the page does not give it. Worth a paid-lane read of the fair-use clause, since Included on a 100 Mbit unmetered port and Included on a 2 Gbit port are different offers.
Evidence notedocumented the Included line is first-party and unambiguous; the FREETRIAL voucher amount was not readable, and the fair-use terms behind Included were not read. Those two reads would settle whether the trial is a credit and whether Included has a ceiling
Evidence 2
datesourcewhat it proved
2026-10-23us.ovhcloud.com/public-cloud/prices/the Private Network table reads '| Incoming traffic | Included |' and '| Outgoing traffic | Included |'
2026-10-23us.ovhcloud.com/public-cloud/prices/every Start link carries 'voucher%3DFREETRIAL', so a trial voucher exists even though its value is not on the page
More fields 7
{
 "wg_path": "native-conf",
 "wg_detail": "a Public Cloud instance with a public IP; wg-quick binds UDP directly",
 "ingress": "udp",
 "volume_tib_month": null,
 "volume_stated": "incoming and outgoing traffic are both listed as Included, with no byte figure and no overage line on the price page",
 "bytes_transit": "yes",
 "transit_note": "outbound bytes cross OVHcloud's network under the Included line rather than a meter"
}
Unknown values 2
  • $.per_object_cap.stated the field does not apply to this kind of offer
  • $.retention.stated the field does not apply to this kind of offer