FRITZ!Box 7590 - automatic disabling "enables" ports, portforwording

Networking
1

I have a Fritz!box 7590 with a static ip on the internet side.

I configured a series of portforwording to the RED of the firewall.

Everything worked without problems for about 1 year, for about 10 days, the port authorizations set on the router have been automatically deactivated.

Firewall and router updated to the latest version.
I also tried replacing the router with an equal model, restoring the backup, but nothing came back.

To re-enable everything I have to enter an authorization, change the port number, apply and then re-edit the port.

This is what the 7590 system log reports:
01.09.2323:51:33 Removed enabling for port 444 on XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enabling for port 8000 on XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enabling for port 222 on XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enabling for port 8123 on XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enabling for port 180 on XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enabling for port 443 on XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enable on port range 1194-1200 for XXX.XXX.XXX.XXX (Firewall).
01.09.2323:51:33 Removed enable on port range 80-87 for XXX.XXX.XXX.XXX (Firewall)

Has this ever happened to you?
Could it be the rpovider disabling this?
I have TIM, I live in Italy, and the router is theirs.

2

this would be my guess.

Does TIM give you an internet IP or a CGNAT (Carrier Grade NAT) local IP address?

3

TIM provides me with a static public ip.
I also opened a report to tim they told me that they have disabled me upnp.
Router side it was already disabled by me. let’s see if that was it .

4

After the firmware update the problem no longer occurred, I think I ran into the port 443 bug

5