So one guy had server and suddenly the redstone just stopped transferring redstone signal into repeater at two places, so I download the map and loaded in singleplayer, the problem persisted, I tried breaking the repeaters, changing direction of them, changing ticks on the repeaters a lot a lot more things but they just don't work, you can't transfer redstone signal thru them, redstone powder on that coords works.
I also tried to create a new map with the same seed and went to the same coords and the repeaters worked, also in the original world I tried to move them one block up, one down, just anywhere and it works, it really doesn't work just on the two spots, it's really a super odd bug.
Here is a download link for the map from the server, coords are XYZ: 1766 / 130 / 297
https://mega.nz/#!gFplBCbL!OLzdTb0sMM2KA9_PS_hrHhE7D9I06bOYuM7m7B8EP1M
Related issues
Attachments
Comments

The issue is the following repeaters not receiving the signal.
Affected repeaters:
1767 / 130 / 297
1769 / 130 / 296
1765 / 130 / 296
Deleting the TileTicks
entry for the affected repeaters and then replacing them seems to solve the issue.
I have no clue on why these tile tick entries don't delete themselves or why they're there in the first place, but this is not the first time something like this happens, see MC-158219.
Based on the high mspt on the world, this might have something to do with server lag. Not too sure about that though.
Thank you for your report!
We're already tracking this issue in MC-158219, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

I've been experiencing this issue too in a 1.14.4 singleplayer map. It seems to happen for me on redstone repeater / comparator clocks whenever the chunks have been unloaded. It happened twice when I died and went back later on. The clocks has stopped working and if a repeater were placed in those same coordinates they would still be unresponsive.