Abnormally high gateway backhaul traffic for a single gateway after ChirpStack v4 migration

Viewed 1

Hello ChirpStack team,

We are observing an abnormal backhaul data usage issue with one specific gateway after migrating from ChirpStack v3 to v4.

Scenario:

Network: ChirpStack v4 (Docker-based deployment)

Gateway transport: MQTT over cellular

All gateways are configured similarly and have the same number/type of sensors

Sensors transmit standard uplinks (very low LoRaWAN payload size)

Issue:
One gateway (647fdafffe01358e) is showing extremely high cellular usage:

~600 MB downlink

~300 MB uplink

Whereas other gateways in the same setup show normal usage:

~30 MB down / ~15 MB up

~10 MB down / ~10 MB up

Observations:

LoRaWAN uplink/downlink frame sizes are very small (verified from Frames tab)

No unusual sensor traffic compared to other gateways

Gateway is operational and forwarding data correctly

Issue is isolated to a single gateway

Suspicions / questions:

Can repeated MQTT/TLS reconnects or unstable backhaul cause excessive downlink traffic?

Does ChirpStack re-send configuration, stats acknowledgements, or state sync repeatedly on reconnect?

Are there known cases where region mismatch or ADR instability leads to excessive gateway traffic?

Are there recommended ways within ChirpStack to:

Detect frequent gateway reconnects?

Reduce control / stats traffic?

Tune gateway stats or keepalive behavior?

We would appreciate any guidance on:

Known causes for such asymmetric high backhaul usage

Logs or metrics we should specifically inspect on the ChirpStack side

Best practices to avoid this scenario

Thank you in advance for your help.

0 Answers