|
By:
yes :/
|
|
By:
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.
|
|
By:
Well at least it ain't just me. But it's still extremely disconcerting.
"something is clearly not right." Yep. |
|
By:
Emerald 2150 today not went in play, but still not suspended 8mins later.
|
|
By:
2200 Prairie might just be the same.
11 meets on. Perhaps it's too many of them to juggle. |
|
By:
5 second delay on the race at Belmont just now.
|
|
By:
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.
|
|
By:
oh well they've got to update things, it's only money.
|
|
By:
Belmont there, my f/k not working either
|
|
By:
I'm seeing the same delay issue. I've raised it and will report back what they say.
|
|
By:
Same again at Belmont.
|
|
By:
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?
|
|
By:
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.
|
|
By:
jamee, i reported it they said no other people have been affected. I know who I believe and it's not them.
|
|
By:
And again at Belmont. It's the only track affected for me.
|
|
By:
had a 9 second one there.
|
|
By:
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. |
|
By:
cheers jamee, had a 9 and a 10 in that race
|
|
By:
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.
|
|
By:
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.
|
|
By:
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! |
|
By:
Back to 1 second there at Belmont.
|
|
By:
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.
|
|
By:
Seems "touchwood" to be operating normally again.
|
|
By:
2339 R8 at Presque Isle, 5 second delay
|
|
By:
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.
|
|
By:
Thistledown 18:50 was 5 secs.
|
|
By:
Finger Lakes 19:27
|
|
By:
Horseshoe 20:12
|
|
By:
Horseshoe 20:43 briefly 5 secs before reverting to 1 sec after a furlong.
![]() |
|
By:
this is getting ridculous, jamee have you DMd them?
|
|
By:
and ridiculous
|
|
By:
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? |
|
By:
jamee, what does 'fixed' mean?
|
|
By:
Started out with 5 secs delay then reverted back to 1 sec.
|
|
By:
For completeness:
Horseshoe 22:47 was fixed after 11 secs. Presque Isle 23:39 was fixed after 32 secs. |
|
By:
Delaware race 4, still happening.
|
|
By:
Yep. Right until the very end when it changed back to 1 sec delay three secs before suspension.
![]() |
|
By:
Race 4 Horseshoe 5 seconds.
|