Contabo’s current Help Center says its servers have no default bandwidth limit, but fair-use terms apply and exceptionally high or disruptive use may be throttled. That is not an unconditional promise that any VPS can carry any continuous stream: check the current terms for your exact plan, then assess both its port speed and the traffic your stream will generate.
These are separate questions. Port speed concerns how quickly data can travel at a given moment; monthly traffic is the total amount transferred over time. A stream can fit comfortably within an advertised port rate while still generating a large monthly data total.
What Contabo’s current bandwidth wording means
Contabo’s Help Center guidance on bandwidth and traffic limits says there is no default bandwidth limit for its VPS, VDS and dedicated server products, while also describing a fair-use policy. The policy wording reserves the possibility of throttling exceptionally high or disruptive usage. This is the current general answer, not a guarantee of a particular speed or approval for a specific 24/7 workload.
The distinction matters if you run an always-on channel. A VPS that sends a steady stream to YouTube is doing sustained outbound work, not the short burst of traffic typical of a website visit. The support wording does not say that every continuous stream will be throttled, nor does it promise that no continuous stream will be reviewed. The practical answer is to read the terms attached to the plan you intend to buy and ask Contabo support about your planned sustained use if the policy wording leaves doubt.
Contabo’s VPS product documentation lists product-specific port speeds and presents traffic terms with fair-use qualifications. The listed plans and their terms can change, so do not infer that a plan in an old comparison or forum post has the same conditions now. Check the chosen region, product, and order terms rather than applying a general statement to every VPS.
There is also older official material that needs careful handling. A Contabo traffic post, last updated 10 April 2025, describes a schedule involving traffic packages and a period of ten consecutive days above a package before port-speed reduction. Current Help Center wording does not repeat that schedule; it instead states that there is no default limit and that fair-use throttling is discretionary. Treat the older post as historical or potentially product-specific context, not as a universal current threshold for all VPS plans. For an account-specific answer, the current order terms and written confirmation from support are more useful than assuming either policy text covers every case.
Fair use and a persistent stream
Fair use is a qualification on the way a provider presents traffic, not a numeric allowance you can safely guess. In this case, the current help wording identifies exceptionally high or disruptive use as grounds for possible throttling without setting a universal traffic figure or a fixed number of days. This article therefore cannot tell you that a particular monthly volume is automatically allowed or automatically prohibited.
A continuous broadcast can matter even if the bitrate is modest. The traffic repeats hour after hour, so the accumulated outbound volume can be much larger than a short live event. The sensible question is not only “Does my stream fit the port?” but also “Do my plan’s current terms cover this pattern of sustained outbound traffic, and what would happen if the provider considers it exceptional?”
Keep a record of the exact product name, location, advertised port speed, traffic wording, and date you checked the terms. If you contact support, describe the service plainly: YouTube live output, the approximate bitrate, expected hours per day, and whether the VPS encodes the video or only relays it. A clear workload description gives support the context needed to answer; it does not itself guarantee approval or a particular network outcome.
If your channel depends on an overnight playlist, also plan for failures beyond bandwidth policy. A route can degrade, an encoder can stop, or a process can exit. The practical guidance in this guide to keeping a prerecorded livestream running after a server reboot covers the separate recovery problem. Recovery planning does not remove a traffic-policy risk, but it helps you distinguish a crashed process from a provider-side network issue.
Port speed is not monthly data
A port speed, usually expressed in megabits per second (Mbps), describes a rate at which a network interface can carry data. Your video bitrate is also a rate, but it is the rate of the encoded stream. Monthly traffic, often expressed in gigabytes (GB) or terabytes (TB), is the accumulated volume transferred over a period. The units are different because one describes speed and the other describes quantity.
Contabo’s documentation shows VPS port rates ranging from 200 Mbps to 1 Gbps in the plan table consulted for this article. Those are listed port speeds, not measured throughput from your particular VPS to YouTube. They do not establish that the route will sustain the full rate, and they do not tell you how much monthly traffic the provider will regard as exceptional under its current fair-use terms.
YouTube’s recommended H.264 video bitrate is 14 Mbps for 1080p at 30 frames per second and 17 Mbps for 1080p at 60 frames per second. Its recommendation for 4K at 60 frames per second is 50 Mbps. These are encoding targets from YouTube’s live encoder settings guidance, not evidence that a particular VPS-to-YouTube route can sustain them continuously.
On paper, those example bitrates are lower than the port rates shown in Contabo’s plan table. That comparison is a first check, not a stability test. Network routes, packet loss, contention, protocol overhead, and the way your application sends data can all affect the stream. If the VPS encodes the programme, CPU capacity and encoder load also matter; a network port with headroom cannot compensate for an encoder that cannot produce frames reliably.
Make sure you know which direction the VPS traffic takes. If it encodes and sends a live feed to YouTube, the relevant stream traffic is outbound from the VPS. If it relays a feed encoded elsewhere, the VPS may receive an input and send an output, so traffic can cross the VPS in more than one direction. Viewer playback traffic is generally served by YouTube rather than by your VPS, unless your setup has a separate distribution role. Do not count all viewer watch time as VPS egress without checking the architecture.
Estimate traffic from bitrate and runtime
You can make a useful planning estimate from the video bitrate and the hours you expect to stream. For decimal GB, use:
traffic in GB ≈ bitrate in Mbps × seconds streamed ÷ 8 ÷ 1,000
The division by eight converts bits to bytes; division by 1,000 expresses the result in decimal gigabytes. This is arithmetic based on a constant bitrate, not a Contabo allowance or a measurement of actual billing or network usage.
| Example H.264 video bitrate | Approximate data per hour | Approximate data per day | Approximate data over 30 days |
|---|---|---|---|
| 14 Mbps, 1080p30 | 6.3 GB | 151 GB | 4.5 TB |
| 17 Mbps, 1080p60 | 7.65 GB | 184 GB | 5.5 TB |
The table uses the YouTube video bitrate examples above and assumes the rate stays constant. For a calculation of your own, multiply the bitrate by the total number of seconds you will stream, then apply the formula. If you stream only part of each day, use those hours rather than a full day; if you plan an unbroken month, use the total runtime for that month. Do not treat the rounded totals as exact metering figures.
Actual traffic may differ. Audio adds data, and protocol overhead, reconnects, retries, and other VPS services can increase the total. A variable-bitrate encoder may average below or above a setting at different moments. If you have a measured average outgoing bitrate from a test, using that value may make the estimate more useful than relying only on the configured target. YouTube recommends testing upload bitrate and checking stream health; its live streaming troubleshooting guidance can help interpret problems during a test.
For a simple planning margin, note the assumptions rather than adding an arbitrary percentage: video bitrate, audio setting, daily hours, number of days, and any other outbound services on the VPS. Update the estimate if you change resolution or frame rate. A devotional playlist at a stable 1080p30 setting and a 4K60 channel do not create the same traffic, even if both run for the same number of hours.
Compare your estimate with the exact plan terms
Once you have a monthly estimate, compare it with the current terms for the exact product and location you intend to order. Check whether the product documentation or order page describes traffic as unlimited subject to fair use, provides a specific traffic package, or sets another condition. Preserve the wording and date you checked it. Where documents appear to conflict, ask support which terms govern your plan rather than choosing whichever page sounds more permissive.
Use a comparison such as this before paying:
| What to check | Why it matters | What to record |
|---|---|---|
| Product and location | Plans and listed conditions may differ | Exact plan name and selected region |
| Port speed | Affects the rate the interface is listed to support | Published rate, not assumed real-world throughput |
| Traffic and fair-use wording | Defines the provider’s stated conditions | Exact current wording and source page |
| Stream settings and runtime | Determines the approximate volume sent | Codec, resolution, frame rate, bitrate, hours |
| Workload type | Encoding and relaying use resources differently | Whether the VPS encodes, relays, or does both |
| Test results | Shows how your route behaves at the time of testing | Upload bitrate, dropped frames, and YouTube health |
If you see the word “unlimited”, read the qualification around it. It should not be interpreted as an unconditional promise of unlimited sustained throughput, nor does it eliminate the need to comply with fair-use terms. Equally, the fair-use qualification alone does not tell you that ordinary continuous streaming will be throttled. You need the current wording for your selected plan and, where it remains unclear, a response from Contabo about the described workload.
The older traffic post may appear in search results with tier figures and a ten-day period. Since current general support language does not repeat that schedule, do not calculate your current plan’s safe limit from those older figures. They may describe an earlier or narrower policy context. Ask support to confirm whether that post applies to the plan and location you are considering, and keep the answer with your purchasing notes.
If policy uncertainty is unacceptable for your channel, that may influence whether you choose a self-managed VPS at all. A VPS is more suitable when you want control over the operating system, encoder, and stream workflow and are prepared to maintain them. If you mainly want to upload a file and avoid leaving your own computer running, a managed approach may remove that operational burden. StreamNeo addresses the specific problem of keeping a file-based broadcast running without maintaining a local computer; it does not change YouTube’s requirements or replace checking the provider terms for any VPS you operate.
Test the route and watch for network problems
A plan-page comparison cannot show how your specific stream will behave. YouTube recommends testing upload bitrate, checking that the total stream bitrate fits the available upload bandwidth, and monitoring stream health during the event. A test from the VPS to YouTube is more relevant than a generic speed test from your home connection, because it exercises the source network and the stream path you intend to use.
Run a test using the intended resolution, frame rate, codec, and approximate bitrate. Watch YouTube’s stream health indicators and the encoder’s logs for dropped frames or connection interruptions. Where possible, test for long enough to expose recurring problems rather than treating a brief successful connection as proof of long-term stability. A successful test demonstrates how the setup behaved during that test window; it cannot promise uninterrupted operation overnight or establish a long-term traffic-policy decision.
If the stream degrades, separate likely causes before changing the plan. An encoder reporting skipped or overloaded frames points towards processing capacity or configuration. Dropped frames caused by network congestion, repeated disconnections, or unstable upload bitrate point towards the path or sending process. A stream that stops after sustained operation may require checking process logs, VPS monitoring, provider notices, and YouTube’s stream status. Capture timestamps and relevant messages so a support request can identify what happened.
A practical preflight is to confirm that the channel can go live, check the YouTube stream key and ingest configuration, run a private or otherwise appropriate test, and review stream health before relying on the broadcast. If you are still preparing the channel, this checklist for confirming YouTube Live is enabled addresses an account-side prerequisite. For production details such as audio, overlays, and scene preparation, use these YouTube live-stream production tips alongside the network test.
Document the outcome: the plan and region, test settings, observed bitrate, any drops, and the date. Repeat after a material change, such as moving regions, raising resolution, changing the encoder, or altering the playlist workflow. This gives you a baseline for diagnosis, not a guarantee that the same route or policy conditions will persist.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does Contabo throttle VPS bandwidth?
Contabo’s current Help Center says there is no default bandwidth limit for VPS, VDS, or dedicated server products, but fair-use terms apply and exceptionally high or disruptive use may be throttled. That wording leaves room for discretionary action; it is not a promise of unrestricted continuous throughput. Check the terms for your exact plan and ask support about your expected workload if needed.
Can I stream to YouTube continuously from a Contabo VPS?
A plan’s listed port speed can be compared with your stream bitrate, but that comparison does not establish stable end-to-end performance or confirm that a continuous workload meets the applicable fair-use terms. Test the actual VPS-to-YouTube route and monitor stream health, while also checking the current product and order terms. No reviewed official source guarantees a specific continuous-stream outcome.
How much monthly traffic does a 1080p stream use?
It depends on the actual bitrate and runtime, not resolution alone. As a calculation from YouTube’s H.264 recommendation of 14 Mbps for 1080p30, a constant stream is about 6.3 GB per hour and about 4.5 TB over 30 days, before differences such as audio and overhead. Treat that as an estimate, not a provider allowance or exact meter reading.
Does “unlimited traffic” mean there is no fair-use risk?
No. Read “unlimited” alongside the current fair-use wording and the terms applying to the selected plan; it is not an unconditional promise about sustained use. Contabo’s older traffic post includes a threshold schedule that current general Help Center wording does not repeat, so confirm with Contabo which terms apply rather than treating old figures as universal.