Bad Networks
Bad Networks explains how Hyper behaves when the connection is no longer ideal. The design goal is to keep the meeting usable by protecting voice, reducing video load, and reconnecting quickly when the path blips.
Use this page when you support mobile workers, travel-heavy teams, or any environment where the meeting must keep moving even when the network does not cooperate.
Wireframes
Section titled “Wireframes”┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/call-health │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Network health │
│ │
│ Meeting: Launch readiness sync │
│ Connection: stable now, 1 short drop in last 10 min │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Latency 42 ms Packet loss 0.6% │ │
│ │ Jitter 6 ms Share quality Good │ │
│ │ Mic path Clean Speaker path Clean │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ Suggestions │
│ - Keep camera on current quality preset │
│ - Prefer wired audio before turning on live translation │
│ - Rejoin only if packet loss rises above 3% │
│ │
└──────────────────────────────────────────────────────────────────────┘
Hosts and participants can see whether the issue is loss, latency, or low bandwidth before deciding how to respond.
When to use this
- Coffee shops, hotel Wi-Fi, mobile hotspots, overloaded home networks, and public internet conditions.
- Teams that want fewer manual bandwidth settings and clearer automatic recovery behavior.
Before you start
- Set expectations that Hyper protects voice first when conditions degrade.
- Encourage users to test from the same class of connection they will use for real meetings.
Settings and options
Operational response
- Reduce non-essential video or stop optional screen sharing when the network panel shows sustained degradation.
- Use captions and chat when audio comprehension needs reinforcement under poor conditions.
- Treat reconnect events as a network symptom first, not a meeting-control problem.
What this feature helps with
Adaptive bandwidth
Hyper detects network conditions in real time and adjusts video quality automatically. When bandwidth drops, we preserve what matters most — your voice and the conversation.
Voice prioritization
Audio always comes first. When the network struggles, we reduce or pause video before compromising voice quality. You stay heard even when the connection is rough.
Quick reconnect
If your connection drops, Hyper reconnects in under a second. No long buffering, no "reconnecting…" spinner — you're back in the call before anyone notices.
How to work with it
Network conditions detected automatically
- Hyper continuously monitors latency, packet loss, and bandwidth
- No manual configuration — detection runs in the background
Bandwidth adapts in real time (prioritizes voice over video)
- When conditions degrade, video quality adjusts first
- Voice stays clear — we never sacrifice audio for video
Quick reconnect if connection drops
- Sub-second reconnect when your connection briefly drops
- Resume the call without rejoining or losing context
Where it fits well
Coffee shop calls
- Handle shared Wi-Fi and bandwidth contention
- Voice stays clear even when others are streaming
- Quick reconnect if the hotspot briefly drops
- No need to hunt for a quieter corner
Mobile hotspot meetings
- Work reliably on 4G/5G when Wi-Fi isn't available
- Adaptive bandwidth reduces data usage when needed
- Voice prioritization keeps calls productive on limited plans
- Sub-second reconnect handles cell handoffs
Travel/hotel Wi-Fi
- Survive slow, congested hotel networks
- Works on connections as low as 500kbps
- No manual quality settings — Hyper adapts automatically
- Stay in the call through flaky connections
What to expect
- Automatic bandwidth adaptation
- Voice always prioritized
- Sub-second reconnect
- Works on 500kbps connections
- No manual settings needed
- QUIC transport protocol
Questions that come up often
What's the minimum bandwidth required?
Hyper can maintain voice calls on connections as low as 500kbps. For video, we recommend at least 1Mbps for a stable experience, but we'll adapt down when needed — reducing or pausing video before compromising audio.
How much packet loss can Hyper tolerate?
Our QUIC-based transport and adaptive algorithms handle moderate packet loss (up to ~5%) without noticeable impact. At higher loss, we prioritize voice and may reduce video quality. Quick reconnect kicks in if the connection drops entirely.
What happens during reconnect?
When your connection drops, Hyper attempts to reconnect within a second. You typically rejoin the same call without leaving — no new link, no re-invite. Other participants may see a brief "reconnecting" indicator on your tile.
Can I manually override quality settings?
Hyper is designed to work automatically — we don't expose manual bandwidth or quality controls. This keeps the experience consistent and avoids user confusion. If you need to reduce data usage, we'll adapt when we detect constraints.
How much mobile data does a typical call use?
Voice-only uses roughly 1–2 MB per minute. With video, usage depends on quality — typically 5–15 MB per minute at default settings. When bandwidth is limited, we reduce video quality to lower data consumption.
Related tasks
Limitations and rollout notes
- Automatic adaptation protects voice and continuity, but no RTC system can fully overcome severe packet loss or total network outage.
- Screen-sharing readability still depends on available upstream bandwidth and the content being shared.
Troubleshooting
Video keeps degrading during the same type of meeting
- Check whether the issue correlates with a specific network, time of day, or device type.
- Compare voice quality to video quality to see whether adaptation is working as designed.
- Pause screen sharing briefly and watch whether metrics stabilize.