# Gateway Network Connected Tags

**URL:** <https://forum.inductiveautomation.com/t/gateway-network-connected-tags/113519>\
**Category:** Ignition\
**Created:** [January 23, 2026, 6:36pm UTC](https://forum.inductiveautomation.com/t/gateway-network-connected-tags/113519 "2026-01-23T18:36:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dustin\_Kwok](https://avatars.discourse-cdn.com/v4/letter/d/41988e/32.png) [@Dustin\_Kwok](https://forum.inductiveautomation.com/u/Dustin_Kwok)\
**Post date:** [January 23, 2026, 6:36pm UTC](https://forum.inductiveautomation.com/t/gateway-network-connected-tags/113519/1 "2026-01-23T18:36:02Z")

</div>

Hello all!

I’m using the system Gateway Network connected tags to monitor gateway connectivity in a redundant (Master/Backup) setup, and I see multiple variations of the same gateway name in the tag browser:

- `_0:0:{GatewayName}`

- `_0:1:{GatewayName}`

- `_0:2:{GatewayName}`

I wasn’t able to find documentation explaining these prefixes. My goal is to individually monitor the primary and backup gateways using two separate tags.

Can someone clarify which of these corresponds to the primary and which corresponds to the backup, and whether `_0:1` / `_0:2` are the correct tags to use for individual monitoring? Or if I should be using `_0:0`

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [January 23, 2026, 6:41pm UTC](https://forum.inductiveautomation.com/t/gateway-network-connected-tags/113519/2 "2026-01-23T18:41:43Z")

</div>

`_0:1` is the connection to the redundant master gateway. `_0:2` is the connection to the redundant backup gateway. `_0:0` is a “virtual” route in the sense that it can internally point to either the master gateway or the backup gateway, depending on which one is active. The idea is that you can use the `_0:0` address in the settings of something like a remote tag provider, and the tag provider will always point to the gateway that is actively executing tags. That way, you have built-in gateway network failover. But if you want to monitor the actual gateways, stick to monitoring the `_0:1` and `_0:2` tags.