Hello,

I´m running CCR1036 with CAPSMAN based forwarding on RouterOS 6.44.3. Today I experienced problems while browsing a specific website, so I pinged with IPv6 and IPv4 the website, which failed. After nearly 1 minutes, everything was back to normal. All looging / monitoring shows nothing at this time frame. I downloaded supout.rif file and found the following right after the given timeframe:

2019.05.29-10:44:55.45@8: (83) flusing queue
2019.05.29-10:44:55.45@8: (83) entering state RUNNING
2019.05.29-10:44:55.45@8: (83)SETUP timeout to:1000
2019.05.29-10:44:55.45@8: checkForFreeMemory
2019.05.29-10:44:55.56@32: checkForFreeMemory
2019.05.29-10:44:55.56@32: (25) run! started, pid 3505
2019.05.29-10:44:55.56@32: (25) entering state WAITING
2019.05.29-10:44:55.57@32: (25) entering state READY
2019.05.29-10:44:55.57@32: (25) sending READY_CONFIRM message
2019.05.29-10:44:55.57@32: (25) flusing queue
2019.05.29-10:44:55.58@32: (25) entering state RUNNING
2019.05.29-10:44:55.58@32: (25)SETUP timeout to:1000
2019.05.29-10:44:55.58@32: checkForFreeMemory
2019.05.29-10:44:55.59@32: checkForFreeMemory
2019.05.29-10:44:55.59@32: (51) run! started, pid 3506
2019.05.29-10:44:55.59@32: (51) entering state WAITING
2019.05.29-10:44:55.60@32: (51) entering state READY
2019.05.29-10:44:55.60@32: (51) sending READY_CONFIRM message
2019.05.29-10:44:55.60@32: (51) flusing queue
2019.05.29-10:44:55.61@32: (51) entering state RUNNING
2019.05.29-10:44:55.61@32: (51)SETUP timeout to:1000
2019.05.29-10:44:55.61@32: checkForFreeMemory
2019.05.29-10:44:55.61@32: checkForFreeMemory
2019.05.29-10:44:55.61@32: (41) run! started, pid 3507
2019.05.29-10:44:55.61@32: (41) entering state WAITING
2019.05.29-10:44:55.62@32: (41) entering state READY
2019.05.29-10:44:55.62@32: (41) sending READY_CONFIRM message
2019.05.29-10:44:55.62@32: (41) flusing queue
2019.05.29-10:44:55.62@32: (41) entering state RUNNING
2019.05.29-10:44:55.62@32: (41)SETUP timeout to:1000
2019.05.29-10:44:55.62@32: checkForFreeMemory
2019.05.29-10:44:57.45@25: (72)SETUP timeout to:0
2019.05.29-10:44:57.45@25: checkForFreeMemory
2019.05.29-10:45:08.15@8: (8) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (8) entering state TRYTERM
2019.05.29-10:45:08.15@8: (8) sending TERM message
2019.05.29-10:45:08.15@8: (22) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (22) entering state TRYTERM
2019.05.29-10:45:08.15@8: (22) sending TERM message
2019.05.29-10:45:08.15@8: (25) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (25) entering state TRYTERM
2019.05.29-10:45:08.15@8: (25) sending TERM message
2019.05.29-10:45:08.15@8: (28) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (28) entering state TRYTERM
2019.05.29-10:45:08.15@8: (28) sending TERM message
2019.05.29-10:45:08.15@8: (30) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (30) entering state TRYTERM
2019.05.29-10:45:08.15@8: (30) sending TERM message
2019.05.29-10:45:08.15@8: (41) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (41) entering state TRYTERM
2019.05.29-10:45:08.15@8: (41) sending TERM message
2019.05.29-10:45:08.15@8: (42) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (42) entering state TRYTERM
2019.05.29-10:45:08.15@8: (42) sending TERM message
2019.05.29-10:45:08.15@8: (46) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (46) entering state TRYTERM
2019.05.29-10:45:08.15@8: (46) sending TERM message
2019.05.29-10:45:08.15@8: (50) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (50) entering state TRYTERM
2019.05.29-10:45:08.15@8: (50) sending TERM message
2019.05.29-10:45:08.15@8: (51) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (51) entering state TRYTERM
2019.05.29-10:45:08.15@8: (51) sending TERM message
2019.05.29-10:45:08.15@8: (64) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (64) entering state TRYTERM
2019.05.29-10:45:08.15@8: (64) sending TERM message
2019.05.29-10:45:08.15@8: (65) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (65) entering state TRYTERM
2019.05.29-10:45:08.15@8: (65) sending TERM message
2019.05.29-10:45:08.15@8: (83) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (83) entering state TRYTERM
2019.05.29-10:45:08.15@8: (83) sending TERM message
2019.05.29-10:45:08.15@8: (96) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (96) entering state TRYTERM
2019.05.29-10:45:08.15@8: (96) sending TERM message
2019.05.29-10:45:08.15@8: (97) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (97) entering state TRYTERM
2019.05.29-10:45:08.15@8: (97) sending TERM message
2019.05.29-10:45:08.15@8: (122) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (122) entering state TRYTERM
2019.05.29-10:45:08.15@8: (122) sending TERM message
2019.05.29-10:45:08.15@8: (132) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (132) entering state TRYTERM
2019.05.29-10:45:08.15@8: (132) sending TERM message
2019.05.29-10:45:08.15@8: (134) trying to terminate, entering TRYTERM
2019.05.29-10:45:08.15@8: (134) entering state TRYTERM
2019.05.29-10:45:08.15@8: (134) sending TERM message
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (51) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (97) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (134) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (65) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (41) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (50) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (25) entering state WAITSIG
2019.05.29-10:45:08.15@8: (132) TERMOK, terminating
2019.05.29-10:45:08.15@8: (132) entering state WAITSIG
2019.05.29-10:45:08.15@8: read failed (EOF)
2019.05.29-10:45:08.15@8: (22) entering state WAITSIG
2019.05.29-10:45:08.15@8: (132) finally got signal, status 0x0
2019.05.29-10:45:08.15@8: (132) entering state DEAD
2019.05.29-10:45:08.15@8: checkForFreeMemory
2019.05.29-10:45:08.15@8: (65) finally got signal, status 0x0
2019.05.29-10:45:08.15@8: (65) entering state DEAD
2019.05.29-10:45:08.15@8: checkForFreeMemory
2019.05.29-10:45:08.15@8: (134) finally got signal, status 0x0
2019.05.29-10:45:08.15@8: (134) entering state DEAD
2019.05.29-10:45:08.15@8: checkForFreeMemory
2019.05.29-10:45:08.15@8: (3

(No, there´s no single STP activated on any bridge/interface on the CCR1036, it´s routing traffic in/out)
What would you check if you´re in my situation?

Do you have historic voltage graphs? I had weird issues with same device until i found slow voltage drop from 24V to 18V during about one month. I replaced PSU capacitors, so now i have no more issues with that device, having 24V from PSU.

I have mtxr hl voltage values:

(multiplicator of 10...), so ~ 23,1V Would this be enough?