Innomesh · Cloud Control
Resilience
and connectivity-loss behaviour.
What happens to our rooms if the local AV network loses its uplink to the wide area network or the internet?
01. The question, stated plainly
If the local AV network loses its uplink to the wide area network or the internet, while the departmental network remains healthy, can the rooms keep functioning? This post gives the direct answer, the architectural context, and the operating evidence behind it, plus the additional resilience patterns available if you want to harden the deployment further.
02. What actually happens
In the room
Devices retain state
A presentation already running from a local laptop continues. Audio already routed continues. Displays already powered on stay on.
Touch panels
Frozen, not failed
Touch panels freeze until connectivity returns. The room is frozen in its current state rather than falling into an unsafe one.
On reconnection
Automatic reconciliation
The control plane reconciles state automatically. No manual recovery step is required from your AV team.
The failure mode is graceful loss of control, not loss of the room. When connectivity returns, room state and any in-progress activity continue uninterrupted.
03. The results speak for themselves
99.99%
Control-plane availability sustained across 30+ enterprise tenants in higher education, healthcare, government, and corporate sectors.
1,500+
In production at the University of Queensland, highly available AV control from the cloud for the past seven+ years.
04. How the architecture supports this
Four properties of the platform combine to deliver the behaviour described above. None of them are bolt-ons; all four are how Innomesh is built.
Redundancy in the connectivity layer
AWS Site-to-Site VPN and AWS Direct Connect include built-in redundancy, multiple endpoints, and redundant connectivity patterns.
Per-room container isolation across multiple data centres
Each room runs as its own containerised instance across multiple Availability Zones, so one room incident does not affect another.
Local media path, not through the Cloud
Innomesh sends control commands to AV devices; it does not carry the audio or video stream itself.
Active-active control plane
The control plane runs as an active-active deployment across multiple AWS Availability Zones.
Optional · Tier 3
Local controller redundancy.
Clustered cloud control, plus one local failover. The local controller and AV devices in the room continue independently of the cloud connection.
05. Resilience options if you want to go further
01
Dual site-to-site VPN tunnels
Suitable where you already operate redundant firewalls with HA failover.
02
Dual Direct Connect for HA
Two AWS Direct Connect circuits configured for high availability.
03
AV architecture at the control-plane edge
Customer-specific and typically more expensive than the dual-tunnel pattern.
06. Our availability promise
Response and resolution targets per severity, paired with a control-plane availability commitment measured over a rolling 12-month window.
99.99%
Control-plane availability target
Measured over a rolling 12-month window across 30+ enterprise tenants.
| Incident | First response | Resolution |
|---|---|---|
| Critical | 15 minutes | 1 hour |
| Severe | 30 minutes | 8 hours |
| Partial | 2 hours | 48 hours |
| General | 8 hours | 72 hours |
Walk through this with our team.
The Innomate team is happy to step through the connectivity pattern with your DevOps, Networks, Cloud and Cyber Security teams in detail.
team@innomate.io