Platform · Resilience

What happens when the network drops.

Plants lose links: a fibre is cut, a firewall rule changes, a cloud region has a bad hour, a database is restarted for maintenance. This is exactly what a Proxus gateway does then, in order, with the limits that apply.

Book a demo Try the outage

Try it

Cut the link, then watch the history fill.

Fast time: a second here is four hours at the plant. Leave the link down for more than twelve seconds and the 48-hour retention starts dropping the oldest values.

Online: every value reaches the history as it is read.

Step by step

From the moment the link fails to the moment it is caught up.

The link fails Nothing on the floor stops The hub, a database or a cloud service is out of reach
Collection carries on Drivers, rules and alarms keep running On the gateway, at their configured rates
Data waits In the gateway’s buffer, with its own times Each target has its own queue too
Status says so Disconnected, with what is queued In the hub, per gateway and per target
The link returns The backlog arrives in order The history has no gap; then live data again

The limits

What to expect, stated plainly.

48 h
How long data waits: By default. Set per gateway from 1 to 720 hours, as long as its disk holds that many hours at its data rate.; Oldest first
Past the retention: Values older than the retention are dropped first, so the newest data is never the data lost.; In order
Delivery: At least once: in rare cases a value written just before the link failed is written twice. Within these limits values wait instead of being skipped.; 5 tries
A record a target refuses: If a target answers but never accepts one record, that record is skipped after five attempts and named in the target’s status, so the rest is not held up.; 10,000
Alarms while offline: Alarms are kept on the gateway until the hub confirms it has them, sent in the order they were raised; the queue holds up to 10,000 of them.; Waits
A restart without the hub: A running gateway rides out the outage. A gateway that starts while the hub is unreachable waits for the hub before it collects.; Licensed rate
Above the rate: Data above a gateway’s licensed rate is not delivered and not buffered, online or offline.

Details: gateway buffer retention · outbound targets · store-and-forward explained

Proven in production

Running at the edge, including where bandwidth is scarce.

All deployments

Plan for your outages

How long are your outages?

Tell us how many sites you run and how long a link is usually down. An engineer sizes the gateway buffer with you and replies within one working day.

Plan outages Live demo