5G Not stable, frequent disconnection with 5-10 seconds disturbances
5G Not stable, frequent disconnection with 5-10 seconds disturbances

I do notice frequent disconnection/connection on 5G network, reconnect takes 5-15 seconds. Syslog shows below messages.
2024-12-11 18:18:22 [3] LTE: Exception:GetMobileStatus fail
2024-12-11 18:18:27 [3] LTE: Exception:item length too long(1034)
2024-12-11 18:18:27 [3] LTE: Exception:GetMobileStatus fail
2024-12-11 18:18:33 [5] LTE: SIM plugged.
2024-12-11 18:18:33 [5] LTE: Not registered, searching!
2024-12-11 18:18:36 [5] LTE: Registered with a network!
2024-12-11 18:18:36 [5] LTE: Network type is NR.
2024-12-11 18:18:36 [5] LTE: network changed: 0,0->420,1
2024-12-11 18:18:36 [5] LTE: Start connecting to the network!
2024-12-11 18:18:36 [5] LTE: Fail to connect to the network, start autoconnect!
2024-12-11 18:18:38 [5] LTE: Connected to the network!
Device used in KSA with STC network, Netowrk bands B1,B3,N40,N78. Normal operation device alternates between 5G/4G with no error (led white/green) but Exception conditions syslog as above messages.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, thanks for posting question here.
First, it is suggested to insert the same SIM into another LTE device or even a smartphone, then monitor for some time to confirm if the internet works fine and is stable.
Or if possible, you may insert another sim card to compare.
And you may refer to this guide to change DNS for try.
- Copy Link
- Report Inappropriate Content
1. The SIM is in use for 3 years on Android phone (Moto G 5G, Samsung M23) as USB/Ethernet Tethering to Mesh Router
2. Current Location also tried same phones and no issues , NX200 was swapped for missing band and CA on 5G
3. DNS is same for 5G and 4G+, device doesn't suffer "Exception" conditions on LTE-Plus
- Copy Link
- Report Inappropriate Content
Hi, to assist you efficiently, I've forwarded your case to the TP-Link support engineers who will contact you with your registered email address later. Please pay attention to your email box for follow-up.
Welcome to update solution here once the problem is resolved.
Thank you!
- Copy Link
- Report Inappropriate Content
Thanks @Marvin_S,
I shared multiple logs and waiting for feedback.
I reverted to old firmware "Firmware Version: 1.1.0 3.0.0 v60a2.0 Build 240519 Rel.754n" and could see different behavior with same 10 seconds delays.
2016-01-01 08:16:32 [5] LTE: SIM plugged.
2016-01-01 08:16:33 [3] LTE: Exception:archive length too short(0)
2016-01-01 08:16:33 [5] LTE: Not registered, searching!
2016-01-01 08:16:34 [5] LTE: Registered with a network!
2016-01-01 08:16:34 [5] LTE: Network type is LTE.
2016-01-01 08:16:34 [5] LTE: network changed: 0,0->420,1
2016-01-01 08:16:34 [5] LTE: Start connecting to the network!
2016-01-01 08:16:34 [5] LTE: Fail to connect to the network, start autoconnect!
2016-01-01 08:16:34 [5] LTE: Network type is NR.
2016-01-01 08:16:36 [5] LTE: Connected to the network!
2024-12-20 13:26:38 [5] LTE: Network type is LTE PLUS.
2024-12-20 13:26:48 [5] LTE: Network type is NR.
2024-12-20 16:57:22 [5] LTE: Network type is LTE PLUS.
2024-12-20 16:57:32 [5] LTE: Network type is NR.
2024-12-20 17:05:02 [5] LTE: Network type is LTE PLUS.
2024-12-20 17:05:12 [5] LTE: Network type is NR.
Restart of CPE SIM registration to 5G NR take 4 seconds, during normal operation LTE-PLUS to 5G NR takes 10 seconds on every switchover.
Changed Firmware Version: 1.2.0 3.0.0 v60a2.0 Build 240613 Rel.62450n and also 1.3.0 3.0.0 v60a2.0 Build 240627 Rel.48750n, the errors are back
2024-12-21 11:40:56 [3] LTE: Exception:SendAtCommand fail
2024-12-21 11:41:02 [5] LTE: SIM plugged.
2024-12-21 11:41:02 [5] LTE: Not registered, searching!
2024-12-21 11:41:03 [5] LTE: Registered with a network!
2024-12-21 11:41:03 [5] LTE: Network type is LTE.
2024-12-21 11:41:03 [5] LTE: network changed: 0,0->420,1
2024-12-21 11:41:03 [5] LTE: Start connecting to the network!
2024-12-21 11:41:03 [5] LTE: Network type is LTE PLUS.
2024-12-21 11:41:03 [5] LTE: Fail to connect to the network, start autoconnect!
2024-12-21 11:41:04 [5] LTE: Network type is NR.
2024-12-21 11:41:05 [5] LTE: Connected to the network!
2024-12-21 11:42:56 [5] LTE: Network type is LTE.
2024-12-21 11:42:56 [5] LTE: Network type is LTE PLUS.
2024-12-21 11:42:57 [5] LTE: Network type is NR.
2024-12-21 11:45:26 [5] LTE: Network type is LTE.
2024-12-21 11:45:26 [5] LTE: Network type is LTE PLUS.
2024-12-21 11:45:26 [5] LTE: Network type is NR.
2024-12-21 11:45:57 [5] LTE: Network type is LTE.
2024-12-21 11:45:57 [5] LTE: Network type is LTE PLUS.
2024-12-21 11:45:57 [5] LTE: Network type is NR.
- Copy Link
- Report Inappropriate Content
Hi, thanks for your update here.
I saw that you also share same log to the senior support, it is suggested to wait for their further research and response.
Thank you and best regards.
- Copy Link
- Report Inappropriate Content
same problem here, have you already found a solution? which provider do you have? use o2 telefonica.
- Copy Link
- Report Inappropriate Content
Still no. I am still tracing and sharing information with support.
If you are getting same exception error, I suggest to open support ticket.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Support fixed 1 conditions for disconnections for Band = Auto mode.
Update 3 weeks testing:
Forcing Band to N77 multiple problems pop up.
* Modem resets connection with 8 seconds disturbances recovers new IP from ISP
* Modem hangs (frequent) on routing / webconsole / tether / Internet for 16-17 minutes and recovers retaining old IP
* telnet/webconsole/tether services gives software disconnection (frequent) error but routing/internet works for 16-17 minutes and recovers
* network services disconnects all connected devices for 16-17 minutes and services returns back
- Copy Link
- Report Inappropriate Content
Update:
Band set to = N77
Band set to = Auto (NX200 active band during error N77)
Yellow highlights = no internet 16 minutes No Network (lan/wifi) & recovers
Green highlights = no internet 8 second modem resets
Red fonts = CPE reboot on own.
192.168.1.1 Mar 21 09:45:03 local0 notice Mesh Del Client : MAC : 58:11:22:20:16:E0
192.168.1.1 Mar 21 09:45:05 local0 notice Mesh Success Add Client : MAC : 58:11:22:20:16:E0
192.168.1.1 Mar 21 11:08:58 local0 notice LTE The network disconnected, start autoconnect!
192.168.1.1 Mar 21 11:09:04 local0 notice LTE Fail to connect to the network, start autoconnect!
192.168.1.1 Mar 21 11:09:06 local0 notice LTE Connected to the network!
192.168.1.1 Mar 21 14:55:08 local0 notice LTE Receive a long gw sms and save it successfully.
192.168.1.1 Mar 21 16:24:21 local0 notice Mesh Del Client : MAC : 58:11:22:20:16:E0
192.168.1.1 Mar 21 16:24:21 local0 notice Mesh Success Add Client : MAC : 58:11:22:20:16:E0
192.168.1.1 Mar 21 16:24:51 local0 err LTE Exception:GetMobileStatus fail
192.168.1.1 Mar 21 16:25:26 local0 err LTE Exception:GetMobileStatus fail
192.168.1.1 Mar 21 16:26:01 local0 err LTE Exception:GetMobileStatus fail
192.168.1.1 Mar 21 16:26:36 local0 err LTE Exception:GetMobileStatus fail
192.168.1.1 Mar 21 16:27:11 local0 err LTE Exception:GetMobileStatus fail
192.168.1.1 Mar 21 16:27:11 local0 info LTE execute save
192.168.1.1 Mar 21 16:27:11 local0 err LTE Exception:archive length too long(1110)
192.168.1.1 Mar 21 16:27:11 local0 info LTE new config flag=00000009, new status flag=00000009, index=0, token=2, archive(len=396)={"ver":300,"stast":3,"num":1,"tbl":[{"idx":0,"up":"327502","rule":"0,N,P;1,N,P;2,N,P;3,N,F;4,E,F;5,U,U;6,U,U;7,U,U;8,U,U;9,U,U;10,U,U;11,U,U;12,U,U;","m":{"s
192.168.1.1 Mar 21 16:27:11 local0 info LTE execute reboot
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 1372
Replies: 12
Voters 0
No one has voted for it yet.