How many people can stream your Eagle 3D Streaming app at once, where they connect from, and what happens when either limit is reached.
CCU is how many people are streaming at the same moment — not how many visit in a day.
If 100 people use your app across a day but never more than 6 are streaming at once, you are using 6 CCU. Capacity is about the peak, not the total.
A session ending releases its CCU immediately, and the next person waiting can use it. One exception: an application kept preallocated counts as one CCU the whole time it is held, even while nobody is streaming it. So the practical questions are how many people arrive together, and how long each one stays — which is why the idle timeout matters more than it sounds: a session nobody is using still occupies a slot somebody else wants.
When every slot is taken, the next viewer does not get a stream. The page shows CCU Limit Reached. Trying Again in 10 sec, counts down and tries again, so the viewer gets in as soon as a session ends. The account owner is also sent a CCU limit alert by email.
| Plan | Concurrent streams | Where your app can run |
|---|---|---|
| Trial | 1 | USA, Europe |
| Core | 10 | USA, Europe |
| Enterprise | Up to 1000 | Global — deployment in your preferred cloud region |
With the region left on Global, viewers are served from E3DS's own datacentres first, then from the nearest cloud region. When that region has no capacity, the session is routed to another one rather than refused — the stream works, and it works with more latency.
The Select Region dropdown in the developer options offers two values: Global, which is the automatic routing above, and United States. There is no Europe option. Pinning United States has no fallback: viewers wait for a machine in the United States and are never sent to another region.
To confirm which region actually served a session, open the System Info button inside the stream and read the Streamer Location line.
How quickly your build reaches E3DS's machines depends on where you are uploading from. It affects how long an upload takes and nothing about how the app streams afterwards — a slow upload from a distant office does not produce a slow stream.
Upload speeds observed in testing. They vary with load, network conditions and time of day, so treat them as a guide rather than a promise.
| Region | Location | Peak | Lowest recorded | Average |
|---|---|---|---|---|
| Europe | Frankfurt | 210 MBps | 76 MBps | 143 MBps |
| USA | N. Virginia | 110 MBps | 20 MBps | 65 MBps |
| Asia | Mumbai | 32.9 MBps | 13.49 MBps | 22.5 MBps |
| Asia | Sydney | 212 MBps | 185 MBps | 198.5 MBps |
The settings that free capacity by ending sessions nobody is using.
Last updated