# Ignition Failover **URL:** \ **Category:** General Discussion\ **Created:** [July 1, 2026, 9:21pm UTC](https://forum.inductiveautomation.com/t/ignition-failover/116240 "2026-07-01T21:21:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 1, 2026, 10:00pm UTC](https://forum.inductiveautomation.com/t/ignition-failover/116240/2 "2026-07-01T22:00:46Z")
Ignition has no special code for WSFC, whatever that actually means in practice. If that feature can act like a reverse proxy/load balancer, then the answer I just gave in this other thread basically applies: > [@Web Development Module and Redundancy](https://forum.inductiveautomation.com/t/web-development-module-and-redundancy/116238/2): > > A load balancer/reverse proxy is the generally accepted solution to this, but be aware they have no concept of Ignition's specific redundancy concept. You'll have to use a product smart enough to distinguish between HTTP availability (whether the given redundant node is up at all) and Ignition's specific redundancy role (i.e. don't try to fail requests over to a backup that is not active). You can do this by checking the /system/gwinfo route. --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-failover/116240)._