Network disruption in the Netherlands
-
@cees-meijer sorry for the inconvenience and thanks for the suggestion we will take this in consideration!
-
@Eric-Barten Since 04:30 this morning we have have not received any messages from our devices.
Is there a known network or server outage at T-Mobile? -
I have to confirm this. No messages since 2020-03-11T03:31:09.33449585Z
Same problem as last week?Derko
-
Same here, not receiving messages anymore, last message received 03:55.
Since last year we were very impressed with how the overal NB-iot network performed, but now with the missing messages this is putting NB-iot via T-mobile in a bad spotlight with our customers. -
This is unacceptable indeed and we are very sorry for the inconvenience. We are in touch with all involved engineers and suppliers and working on a structural solution.
-
The main unacceptability lies in the complete lack of communication.
I’ve given up, the high we all experienced last year is turned into a an all time low. I’m ready and able to pay for better service and so talking to Vodafone.
The head-in-the-sand attitude of the T-Mobile team (except for Eric) is unprecedented. I received the personal phone numbers of several team members but none of them are picking up or even returning calls. -
Is this affecting all price plans? Or only the community SIM cards?
-
I’m receiving messages again. Problem solved?
About lack of communication as @magnatron writes: I am not sure if I agree with that. Yes, it is hard to get in touch with T-Mobile. That needs to be improved. But once you have contacted them, they are very much willing and trying to solve your problem.
And, we have a ‘Community’-plan. I don’t know exactly what I can expect as support. -
Some of our devices are now back up, but not all of them.
Can T-Mobile let us know when we should expect full recovery? -
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.
