Our setup has produced a missed block https://beaconcha.in/slot/5501765
We have been producing blocks correctly and after that incident it is still producing blocks correctly.
We have a 3-layer configuration with the validator client, the Beacon node and the execution client running separately.
We are using Mev-boost

This issue its RARE and not replicable at this moment and seems related to a reorg chain.

Validator: 326216
Slot: 5501765
Epoch: 171930
Proposed block should be: 16334246

These are our versions and fee recipent setup:

Validator set up and: version: Lighthouse/v3.3.0-bf533c8
lighthouse vc
--beacon-nodes http://ip1,http://ip2,http://ip3
--network mainnet
--metrics
--metrics-allow-origin *
--graffiti "Block by xxxxxxx"
--suggested-fee-recipient 0x388Cxxxxxxxxxxxx
--init-slashing-protection
--metrics-port xxx
--http
--builder-proposals

Beacon set up - teku/v22.12.0/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-17
command: ["--network=mainnet",
"--data-base-path=/opt/teku/data",
"--eth1-endpoints=http://localhost:8545",
"--p2p-port=9000",
"--rest-api-enabled=true",
"--rest-api-host-allowlist=*",
"--metrics-enabled=true",
"--p2p-subscribe-all-subnets-enabled=true",
"--ee-endpoint=http://127.0.0.1:aaaa",
"--ee-jwt-secret-file=xxxxxxxxxxxx",
"--validators-graffiti='Block by Stakely.io - btk01'",
"--validators-proposer-default-fee-recipient=0x718xxxxx",
"--validators-builder-registration-default-enabled=true",
"--validators-proposer-blinded-blocks-enabled=true",
"--builder-endpoint=http://localhost:18550",
"--log-destination=CONSOLE",
"--logging=INFO"

Execution Client - git_branch=heads/v2.32.0 git_tag=v2.32.0-dirty git_commit=021891a311430ffefde77fcceda567ba324e9abe
erigon
--prune htc
--prune.r.before=11184524
--maxpeers 100
--nat any
--http
--http.addr 0.0.0.0
--http.port 8545
--http.api=eth,debug,net,trace,web3,erigon,engine,txpool
--authrpc.port aaaa
--authrpc.addr xxxxx
--authrpc.jwtsecret xxxxx
--private.api.addr=localhost:9091
--chain mainnet
--metrics
--port 30303
--torrent.port 42070
--datadir=/home/erigon/.local/share/erigon
--authrpc.vhosts "xxxxxxxxxxxx"
--externalcl
--port 30302

I attached logs from the time the block produced.
teku_04012023.log
erigon_04012023.log
mev-04012023.log
LighthouseVC_04012023.log

We suspect that the problem is due to the fact that the block was generated during a chain reorganization.