# Ignition and PRP (Parallel Redundancy Protocol)

**URL:** <https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124>\
**Category:** Ignition\
**Created:** [April 16, 2026, 6:13pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124 "2026-04-16T18:13:37Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\
**Post date:** [April 16, 2026, 6:13pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/1 "2026-04-16T18:13:37Z")

</div>

Does v8.1.53 support PRP is the servers NIC hardware support PRP?

What about v8.3?

Thanks,

Ted.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 16, 2026, 6:16pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/2 "2026-04-16T18:16:41Z")

</div>

Ignition has no idea what this is. If it works, it's a concern at a level below Ignition.

---

<div class="post-metadata">

**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\
**Post date:** [April 16, 2026, 6:28pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/3 "2026-04-16T18:28:05Z")

</div>

> [@Kevin.Herron](#):
>
> Ignition has no idea what this is. If it works, it's a concern at a level below Ignition

Thanks @Kevin.Herron. If it did work, why is it a concern?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 16, 2026, 6:31pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/4 "2026-04-16T18:31:20Z")

</div>

I don't mean it's a concern that you should be worried about, I mean it's something that things "below" Ignition have to know about / implement. It's handled at a different layer of the stack, transparent to Ignition.

---

<div class="post-metadata">

**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\
**Post date:** [April 16, 2026, 6:37pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/5 "2026-04-16T18:37:12Z")

</div>

Gotcha, thanks again.

---

<div class="post-metadata">

**Author:** ![Greyship](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Greyship](https://forum.inductiveautomation.com/u/Greyship)\
**Post date:** [April 16, 2026, 10:30pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/6 "2026-04-16T22:30:28Z")

</div>

We use PRP with networking and Ignition, this is entirely transparent at the application level, and is all handled at the lower level (driver) before it even gets to the application.

---

<div class="post-metadata">

**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\
**Post date:** [April 17, 2026, 2:21pm UTC](https://forum.inductiveautomation.com/t/ignition-and-prp-parallel-redundancy-protocol/115124/7 "2026-04-17T14:21:23Z")

</div>

Thank you @Greyship
