What caused disconnects at the Mikrotik + Megaphone access point?

Question

Mikrotik

A few months ago I bought a MikroTik RBLHGR & R11E-LTE access point, stuffed a megaphone SIM card into it, set it up according to one of the instructions on the network. Everything was working ok until yesterday. The internet started dropping out intermittently. It recovers itself in 3-4 minutes. I am attaching the log. Help to understand please.

spoiler

feb/01 04:29:42 dhcp,info defconf deassigned 192.168.88.252 from 50:FF:20:17:5A:B6
feb/01 04:29:43 interface,info ether1 link down
feb/01 04:29:59 interface,info ether1 link up (speed 100M, full duplex)
feb/01 04:30:07 interface,info ether1 link down
feb/01 04:30:16 interface,info ether1 link up (speed 100M, full duplex)
feb/01 04:30:27 dhcp,info defconf assigned 192.168.88.252 to 50:FF:20:17:5A:B6
feb/02 04:29:42 dhcp,info defconf deassigned 192.168.88.252 from 50:FF:20:17:5A:B6
feb/02 04:29:43 interface,info ether1 link down
feb/02 04:29:59 interface,info ether1 link up (speed 100M, full duplex)
feb/02 04:30:08 interface,info ether1 link down
feb/02 04:30:16 interface,info ether1 link up (speed 100M, full duplex)
feb/02 04:30:27 dhcp,info defconf assigned 192.168.88.252 to 50:FF:20:17:5A:B6
feb/03 04:29:41 dhcp,info defconf deassigned 192.168.88.252 from 50:FF:20:17:5A:B6
feb/03 04:29:43 interface,info ether1 link down
feb/03 04:29:58 interface,info ether1 link up (speed 100M, full duplex)
feb/03 04:30:07 interface,info ether1 link down
feb/03 04:30:15 interface,info ether1 link up (speed 100M, full duplex)
feb/03 04:30:26 dhcp,info defconf assigned 192.168.88.252 to 50:FF:20:17:5A:B6
feb/04 04:29:41 dhcp,info defconf deassigned 192.168.88.252 from 50:FF:20:17:5A:B6
feb/04 04:29:43 interface,info ether1 link down
feb/04 04:29:58 interface,info ether1 link up (speed 100M, full duplex)
feb/04 04:30:06 interface,info ether1 link down
feb/04 04:30:14 interface,info ether1 link up (speed 100M, full duplex)
feb/04 04:30:25 dhcp,info defconf assigned 192.168.88.252 to 50:FF:20:17:5A:B6
feb/04 12:40:28 lte,info lte1: not registred, state: 11
feb/04 12:40:28 interface,info lte1 link down
feb/04 12:41:28 lte,error failed to register on network
feb/04 12:42:51 lte,info lte1: registered home
feb/04 12:42:56 interface,info lte1 link up
feb/04 16:34:05 lte,info lte1: not registred, state: 11
feb/04 16:34:08 lte,info lte1: registered home
feb/04 16:34:10 lte,info lte1: not registred, state: 11
feb/04 16:34:10 interface,info lte1 link down
feb/04 16:34:12 lte,info lte1: registered home
feb/04 16:34:13 interface,info lte1 link up
feb/04 18:05:46 lte,info lte1: not registred, state: 11
feb/04 18:06:46 lte,error failed to register on network
feb/04 18:06:46 interface,info lte1 link down
feb/04 18:08:06 lte,info lte1: registered home
feb/04 18:08:10 interface,info lte1 link up
feb/04 18:25:46 lte,info lte1: not registred, state: 11
feb/04 18:26:34 lte,info lte1: registered home
feb/04 18:39:06 lte,info lte1: not registred, state: 0
feb/04 18:40:06 lte,error failed to register on network
feb/04 18:40:06 interface,info lte1 link down
feb/04 18:40:14 lte,info lte1: registered home
feb/04 18:40:15 interface,info lte1 link up
feb/04 19:24:59 lte,info lte1: not registred, state: 11
feb/04 19:24:59 interface,info lte1 link down
feb/04 19:25:59 lte,error failed to register on network
feb/04 19:27:17 lte,info lte1: registered home
feb/04 19:27:22 interface,info lte1 link up
feb/04 20:18:55 lte,info lte1: not registred, state: 11
feb/04 20:19:42 lte,info lte1: registered home
00:13:58 lte,info lte1: not registred, state: 0
00:14:58 lte,error failed to register on network
00:14:58 interface,info lte1 link down
00:15:57 lte,info lte1: registered home
00:16:02 interface,info lte1 link up
01:28:02 lte,info lte1: not registred, state: 0
01:28:06 lte,info lte1: registered home
01:28:32 lte,info lte1: not registred, state: 11
01:28:32 interface,info lte1 link down
01:29:32 lte,error failed to register on network
01:30:02 lte,info lte1: registered home
01:30:03 interface,info lte1 link up
01:35:53 lte,info lte1: not registred, state: 0
01:36:53 lte,error failed to register on network
01:36:53 interface,info lte1 link down
01:38:15 lte,info lte1: registered home
01:38:24 interface,info lte1 link up
04:29:41 dhcp,info defconf deassigned 192.168.88.252 from 50:FF:20:17:5A:B6
04:29:43 interface,info ether1 link down
04:29:59 interface,info ether1 link up (speed 100M, full duplex)
04:30:07 interface,info ether1 link down
04:30:15 interface,info ether1 link up (speed 100M, full duplex)
04:30:27 dhcp,info defconf assigned 192.168.88.252 to 50:FF:20:17:5A:B6
09:46:08 lte,info lte1: not registred, state: 11
09:46:56 lte,info lte1: registered home
09:47:42 interface,info ether1 link down
09:47:55 interface,info ether1 link up (speed 100M, full duplex)
09:48:00 dhcp,info defconf deassigned 192.168.88.252 from 50:FF:20:17:5A:B6
09:48:00 dhcp,info defconf assigned 192.168.88.252 to 50:FF:20:17:5A:B6
09:58:39 system,info,account user admin logged in from 192.168.88.252 via winbox
10:05:26 system,info,account user admin logged in from 192.168.88.252 via telnet

Answer 1

Is everything okay with the provider's tower? feeling like no...

Answer 2

My site is open now.
You should not edit files using the editor in the admin panel, in most cases it ends sadly.
Check hosting support for FTP access and modify files via FTP .

Answer 3

Look at the hosting access to ftp and see this file.
From the error, you are calling the T_FUNCTION constant which is not defined.
ps
1) It is good practice to deploy the project locally (or on a subdomain), make changes on it, if everything is OK - upload it to a live one, while it is better to use git or the like.
2) To customize the theme in the VI, it is better to create a child theme and make changes to it.
because for example, if you decide to update the theme, then all edits will be overwritten.