5 second bet delays

yes :/

It's happening now on race 4 at Emerald Downs and the market has still not been suspended long after the race is finished. I had one a few days ago too, something is clearly not right.

Well at least it ain't just me. But it's still extremely disconcerting.

"something is clearly not right."

Yep.

Emerald 2150 today not went in play, but still not suspended 8mins later.

2200 Prairie might just be the same.

11 meets on. Perhaps it's too many of them to juggle.

5 second delay on the race at Belmont just now.

whole site is goosed to varying degrees, live video via video page is not working , empty boxes on gruss, plus the massive bet placement delays.

oh well they've got to update things, it's only money.

Belmont there, my f/k not working either

I'm seeing the same delay issue. I've raised it and will report back what they say.

Same again at Belmont.

When did this 5 second delay begin in running on the US Racing - bet just there at Belmont- 5 second delay - WTF is going on?

I had it at Churchill Downs too. The site is goosed today, the video page has had an error message since 2pm , they are clearly rolling out updates and messing things up.

jamee, i reported it they said no other people have been affected. I know who I believe and it's not them.

And again at Belmont. It's the only track affected for me.

had a 9 second one there.

I'm tracking the betting delays. Belmont is on 5 secs but switches to 1 sec just as it suspends.

I've not seen any 9 secs.

No issues on any other tracks so far.

cheers jamee, had a 9 and a 10 in that race

Yes....me too, all evening.Even switched computer off and on again...5 sec delays.Was just about to uninstall then reinstall Gruss. Thought it was just my problem.

Might just be the site as it double registered a single bet on the tennis too....didn't realise till i went back and saw what had happened about 20 mins later. Luckily it hadn't cost me...but beware.

Belmont the only one I've seen today.

First time I noticed it in the last week or so, I had 5 second delay on one selection, and usual 1 second on another selection!

Back to 1 second there at Belmont.

BF came back to me. They intimated it was a problem but were quite non-committal about it. Said it was being looked at right now so who knows.

Seems "touchwood" to be operating normally again.

2339 R8 at Presque Isle, 5 second delay

I'm gonna leave an automation running 24/7 to check the delay on every race and will escalate all incidents to BF. Assuming it's an error, they need to stamp this out.

Thistledown 18:50 was 5 secs.

Finger Lakes 19:27

Horseshoe 20:12

Horseshoe 20:43 briefly 5 secs before reverting to 1 sec after a furlong.

this is getting ridculous, jamee have you DMd them?

and ridiculous

Yes, I've sent them a list. They said they are aware and it's being investigated.

Thistledown 18:50 remained @ 5 secs until just before final suspension.
Finger Lakes 19:27 was fixed after 12 secs.
Horseshoe 20:12 was fixed after 3 secs.
Horseshoe 20:43 was fixed after 5 secs.
Presque Isle 20:57 was fixed after 2 secs.
Horseshoe 21:14 was fixed after 3 secs.
Horseshoe 21:45 was fixed after 2 secs.
Presque Isle 21:51 was fixed after 23 secs.

Random fix times. Perhaps they are manually monitoring and fixing as they go?

jamee, what does 'fixed' mean?

Started out with 5 secs delay then reverted back to 1 sec.

For completeness:
Horseshoe 22:47 was fixed after 11 secs.
Presque Isle 23:39 was fixed after 32 secs.

Delaware race 4, still happening.

Yep. Right until the very end when it changed back to 1 sec delay three secs before suspension.

Race 4 Horseshoe 5 seconds.

Race 8 Delaware.

2313 R7 Hawthorne

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

is it an API issue?

2200 R1 Penn

Shame, with no issues up until Penn R1 I hoped the issue had been fixed.

May 30, 2025 -- 5:35PM, swiftynifty wrote:

is it an API issue?

Not API. I just put a bet into Penn R1 on the BF site and there was 5 secs delay.

May 30, 2025 -- 10:17PM, jamee1 wrote:

Shame, with no issues up until Penn R1 I hoped the issue had been fixed.

I thought the same last night. I actually loaded the thread one minute below that race I listed above because I hadn't noticed anything and wondered if there'd been a report on here. Felt I'd jinxed it!

They've just voided all IP bets at Penn r1 cos of the 5 second delay? Very very strange

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.

May 30, 2025 -- 11:02PM, BestShot wrote:

They've just voided all IP bets at Penn r1 cos of the 5 second delay? Very very strange

It was in play for over 20 mins so there might have been some other market mismanagement causing it to be voided.

May 30th - only two instances. Penn 22:00 and Penn 00:15.

Churchill race 7. Any times ?

Well still happening. Beggars belief.

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.

Santa Anita Race 1, another one.

Santa Anita Race 5

Santa Anita R7 too

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

So not just a random glitch it's a whole epidemic. Be assured the're working 24/7 to address the problem.

First at Laurel....5 sec delay.Won't be bothering anymore.....ridiculous.

just got me in r2 at  laurel, wtf is going on

Another there at Gulfstream, what a bloody joke

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.

It makes no sense that it can't be an accident.

Sent them a message but wont hold my breath

This time a 2 second delay, i dont get it

Laurel and Gulf completely gone, what an absolute joke of a company

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....

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.

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.

I think they'd be forced to give some answers/solutions if this was affecting UK races.

Back to normal last race at Laurel, what a treat

Gulfstream wasn't !

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.

Jun 1, 2025 -- 8:11PM, swiftynifty wrote:

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.

I don't think they need to try hard at ruining the in-running. Betfair's previous strategy and the GPS data are making a good job of that anyway.

Only thing I'm amazed about is the number of replies on here show there's still at least 6 people trying!!!

6 people?! I doubt that sometimes, just yourself against a few bots whilst the bot owners are tucked up in bed!

Some good news. There are three races at Finger Lakes tomorrow with coupled horses and betfair have listed them correctly.

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.

Finger race 1.....delay of 5 sec.

race 2 Finger..ok.

Jun 3, 2025 -- 6:08PM, Amanda Hugnkiss wrote:

Finger race 1.....delay of 5 sec.

Are you sure? My automation didn't pick it up.

Tempting fate, but there's not been an instance of 5 sec delay for over two days now. All fixed???

It's been well over a week since the last incident. I'm assuming the issue has been fixed and therefore switching off my monitoring.

If anyone comes across the issue again please update this thread.