|
By:
Race 8 Delaware.
|
|
By:
2313 R7 Hawthorne
|
|
By:
May 29th complete list of affected/partially affected races:
Delaware 19:02 Horseshoe 20:43 Delaware 20:58 Churchill 22:29 Hawthorne 23:13 Hawthorne 23:39 |
|
By:
is it an API issue?
|
|
By:
2200 R1 Penn
|
|
By:
Shame, with no issues up until Penn R1 I hoped the issue had been fixed.
|
|
By:
|
|
By:
|
|
By:
They've just voided all IP bets at Penn r1 cos of the 5 second delay? Very very strange
|
|
By:
Strange they've only picked that race. All races with the 5 secs delay should be voided plain and simple. Hopefully they've have spotted the issue, it's only taken them a week.
|
|
By:
May 30th - only two instances. Penn 22:00 and Penn 00:15.
|
|
By:
Churchill race 7. Any times ?
|
|
By:
Well still happening. Beggars belief.
|
|
By:
you need eyes everywhere, did it go in-play , are bets going in on time, will they just void the race. It's become a complete joke lately.
|
|
By:
Santa Anita Race 1, another one.
|
|
By:
Santa Anita Race 5
|
|
By:
Santa Anita R7 too
|
|
By:
There were loads yesterday
:Gulfstream 18:25, 19:28, 20:32, 21:05 Santa Anita 21:00, 23:06, 00:08, 01:08 Churchill 18:14, 18:43, 19:14, 20:18, 20:51, 21:23, 22:58 |
|
By:
So not just a random glitch it's a whole epidemic. Be assured the're working 24/7 to address the problem.
|
|
By:
First at Laurel....5 sec delay.Won't be bothering anymore.....ridiculous.
|
|
By:
just got me in r2 at laurel, wtf is going on
![]() |
|
By:
Another there at Gulfstream, what a bloody joke
|
|
By:
Laurel and Gulfstream.
This is getting ridiculous now. If this is being done on purpose to test how the market reacts because they have some daft idea to increase the delay to 5 seconds then that would be a big mistake and would be the end of in-running. |
|
By:
It makes no sense that it can't be an accident.
|
|
By:
Sent them a message but wont hold my breath
|
|
By:
This time a 2 second delay, i dont get it
|
|
By:
Laurel and Gulf completely gone, what an absolute joke of a company
|
|
By:
Best thing to do....is if you don't know what delay you will get. which we don't.......just put in a 10p bet early in the race...and see if it gets the delayed treatment....A pain but....
|
|
By:
Gulfstream again there. It begs the question are they trading their own markets, combining GPS data to clean up? Testing the water with a few races to see how much liquidity remains and if there's anything left to be cleaned up, then they do the calculations. Obviously it will signal the end of in-running for the majority bar a few pre-race/ in-play off-setters if they are.
|
|
By:
Dont see why they'd bother, if this became the norm there wouldn't be a single player left in running - having said that BF seem to love making awful decisions.
|
|
By:
I think they'd be forced to give some answers/solutions if this was affecting UK races.
|
|
By:
Back to normal last race at Laurel, what a treat
![]() |
|
By:
Gulfstream wasn't !
|
|
By:
The betting delay is at attribute on the API. eg If you're using Bet Angel you can see the betting delay live. Possibly can be seen on other software too.
|
|
By:
|
|
By:
6 people?! I doubt that sometimes, just yourself against a few bots whilst the bot owners are tucked up in bed!
|
|
By:
Some good news. There are three races at Finger Lakes tomorrow with coupled horses and betfair have listed them correctly.
|
|
By:
Got a reply last night saying that the traders were looking into the delay, and the later races all went smoothly, at least the ones I was involved in - so hopefully the meetings tonight go without a hitch.
|
|
By:
Finger race 1.....delay of 5 sec.
|