Novibet Odd

No, that is not normal, and it is our problem rather than the bookmaker's. Thank you for giving the exact match - it made this findable. Internacional v Remo exists twice in our odds layer, once per upstream source. One copy kept updating until ten minutes before kick-off; the other stopped on 15 August at 02:34, which is 68 hours before the match. You were reading the second one, and that lines up with the 66 hours you saw. Novibet itself is healthy: 1.27M lines and last checked 12 minutes ago as I write this. Nothing is stalling on their side. Two copies per fixture is normal and deliberate - different sources cover different bookmakers, and pooling them is how you get 70+ books instead of 30. What is not normal is one going quiet while the other keeps going, and the API handing you either one without saying which is fresher. Across the last 7 days that happened on 21 of 986 fixtures, so it is uncommon but it is real and you hit it. Until it is fixed, the reliable guard on your side is the updated_at on each row: if it is hours old while the match is hours away, you are on the stale copy and there is a fresher one for the same fixture. Bzzoiro

Following up because this one was closed with "reopen when the fix lands", and it landed today. The endpoint no longer serves a stale copy. When a fixture exists more than once in our odds layer, the copies are now compared against each other and any that has fallen materially behind the freshest is not served at all. Your Internacional v Remo was the case that found it, and Lincoln Red Imps v Larne was the same fault a few days later. It applies to every sport, not just football, since the duplicate copies exist wherever two sources describe the same fixture. Thanks for pushing on it twice - one report reads like a bad match, two reads like a bug, and you were right.