Overview
Stream Machine continuously monitors your stream on both servers. If the primary server fails, DNS is automatically updated to redirect listeners to the backup server. When the primary recovers, listeners are moved back. The whole process is transparent — your audience stays on the same URL throughout.
What Triggers Failover?
Failover is triggered when:
- The primary server becomes unreachable (server or network failure), AND
- The backup server is online and healthy
If both servers are down, no failover occurs (there is nowhere to fail to). This is logged and our team is alerted.
What Happens During Failover?
- The monitoring system detects the primary server is down.
- DNS is updated to point your Stream Machine URL to the backup server's IP address.
- Listeners' players automatically reconnect to the same URL — now reaching the backup server.
- You receive an email notification about the failover event.
Most listeners experience only a brief buffering pause, similar to a momentary loss of mobile signal.
Automatic Failback
When the primary server comes back online:
- The system waits for the primary to remain stable for 2 minutes (to avoid switching back to a server that's flickering up and down).
- DNS is updated to point back to the primary server.
- Listeners are seamlessly moved back.
- You receive an email notification about the failback.
Flapping Protection
To prevent rapid back-and-forth switching, there is a 5-minute cooldown between failover events. This protects your listeners from being bounced between servers if a server is intermittently failing.
What Do My Listeners Need to Do?
Nothing. Listeners using your Stream Machine URL are automatically redirected. They do not need to change their URL, update their apps, or take any action. Most modern media players handle the brief DNS change seamlessly.
