The problem should be only a network delay.
Block 811272 was mined by an unknow miner, this miner may have some slow network connection or simple mempool.space recive the data before from someone else node in the network.
Edit
curl -sSL "https://mempool.space/api/block/0000000000000000000129f389dc62ed91ad78866539ac77b0d9b9a3487b5b89"
{"id":"0000000000000000000129f389dc62ed91ad78866539ac77b0d9b9a3487b5b89","height":811272,"version":612671488,"timestamp":1696800518,"tx_count":1768,"size":1800947,"weight":3992906,"merkle_root":"c21c2a518141b7fb88280cd5f862fd74a746621827ff05835e2e839d68d34b0a","previousblockhash":"0000000000000000000115a254aefecb901263a802f2092ce81c5d642b24e927","mediantime":1696795285,"nonce":3370511648,"bits":386197775,"difficulty":57321508229258.04}
curl -sSL "https://mempool.space/api/block/0000000000000000000137eb33e954c41b692e73edad2f44885146a03ec60c8d"
{"id":"0000000000000000000137eb33e954c41b692e73edad2f44885146a03ec60c8d","height":811273,"version":549453824,"timestamp":1696800386,"tx_count":794,"size":2048344,"weight":3990001,"merkle_root":"c1aa0b3ffcb09a6df1ae067c857ecfcf573f8bb831654856216cf84545dff070","previousblockhash":"0000000000000000000129f389dc62ed91ad78866539ac77b0d9b9a3487b5b89","mediantime":1696796411,"nonce":2327133999,"bits":386197775,"difficulty":57321508229258.04}
I realize that what i said is incorrect.
Block 811272 - timestamp 1696800518
Block 811273 - timestamp 1696800386
Acording to the book, Mastering Bitcoin, Page 249 - Mining and the Hashing Race
However, this was easily resolved by updating the block timestamp to
account for the elapsed time. Because the timestamp is part of the header, the change
would allow miners to iterate through the values of the nonce again with different
results.
The minners can change the timestamp a little without affect the mining process