There have been a lot of conversations of late about Gateway’s appearing offline and comments about stability issues with the NOC API. I’ve noticed a lot more of this happening in recent weeks here in Australia, though it’s not limited to “here”
I have seen similar behavior, gateways have been very unstable in the last few weeks. majority of the gateways that have been unstable are running through the meshed router. @Maj is there anything strange going on with TTN in australia? I don’t think I’m the only one that’s seeing the same thing. I’m not blaming anyone I would just like how to fix it.
@htdvisser is there something we are missing in the gateway config eg some reconnect flag we should set.
Are the gateways just appearing offline in the console or have they stopped routing packets as well? I know there have been some NOC issues at the global level recently, which affects the “last seen” time in the console.
We (Meshed) monitor all the gateways we’ve deployed and we know within minutes is there’s a widespread outage, either real or perceived (ie Console/NOC issue). There has been some occasional outages that affect multiple gateways, but they typically last less than 30 mins. The last one that ran for several hours was about a month ago.
The first place to look is the gateway packet forwarder log. Is the gateway still online and forwarding packets? Post output here if unsure. Then we can work out if it’s related to a particular gateway, or more widespread.
At Digital Catapult in the UK we have 2 or 3 times in the last year seen “not connected” status for large numbers of gateways on the console, yet on checking/testing the gateways are functioning correctly and passing traffic through. It is the status on the console that is wrong, not the gateways themselves.
I think this supports your view that it is not a Meshed issue at all but a more global one.