Network disruption in the Netherlands
-
The problem should be solved for now. It will take some minutes before all data will be received again. So it is possible that some devices are up again and some are still down.
Unfortunately this is only a workaround and we are still looking for a structural solution. I will keep you updated about this.
-
@Eric-Barten we still have some devices that did not come up again. My understanding is that this outage was due to message broker problems and that the devices were still attached to the network. If so, can you track the device by IMEI number (867723030010440)? And correct the problem from your side? Otherwise we have to go and visit a customer location to retrieve and reset/debug the device.
-
@Eric-Barten We also have a device that did not come back. IMEI 357518080554132, last message at 11 mrt. 2020 04:26.
-
Sorry! I had a direct chat with @Robin-Puthli today and didn’t update this topic on devices that did not come back.
@Bart-Abel yours should be fixed right now. I just needed to recover the subscription. Please have a double check.
-
@afzal_m Thanks. It works again!
-
This post is deleted! -
Pleasure to help you!
Anyone else who is still having problems:
Just register a fake IMEI in your project and remove it again. Use https://dyrk.org/tools/imei/ to get a dummy IMEI.
-
@afzal_m said in Network disruption in the Netherlands:
The problem should be solved for now. It will take some minutes before all data will be received again. So it is possible that some devices are up again and some are still down.
Unfortunately this is only a workaround and we are still looking for a structural solution. I will keep you updated about this.
I think a structural solution is to move away from a message broker at the T-Mobile side. It does not add any value for integrators over an (open) APN, and creates maintenance for T-Mobile. Apparently the network is still functioning, and has excellent coverage i must say so that is not the problem.
-
We do not have a message broker @Robin-Puthli. But we do use a SCS. The SCS is an essential component for NB-IoT (as also described by 3GPP). Without the SCS you will get in trouble with your battery.