DCF77 users. Watch for incorrect leap second indicator

On the last day of a month I sometimes see the leap indicator set to 1. The primary cause seems to be incorrect decoding of the DCF77 time signal. As of 2020-01-31 20:30 UTC I see one NTP pool server sending leap=1.

If you use DCF77 as a time source, consider checking the leap status.