General Betting
There is currently 1 person viewing this thread.
Did anyone notice any problems around this time this morning?
My account was emptied on race 7 at Penn (USA racing). Not sure if its a problem with my software or at the exchange. It was as if my software just kept placing bets and failed to read those already matched.
Would be grateful if anyone has any info on if the exchange was fully working around that time.
My account was emptied on race 7 at Penn (USA racing). Not sure if its a problem with my software or at the exchange. It was as if my software just kept placing bets and failed to read those already matched.
Would be grateful if anyone has any info on if the exchange was fully working around that time.
sort by:
Show
per page
Replies: 8
|
By:
If I leave API connected late it often gets its connection dropped in the wee small hours. Can't help with above problem but you have to be aware of it.
On saturday when it was busy I thought something odd was happening with returning matched bets for a short period but nobody else apparently saw it. |
|
By:
Gruss was very sticky for me for a period whilst watching the Del Potro match last night, not sure of the exact time but it was around then.
|
|
By:
This morning at 01:30:13am (uk time), my software attempted to matchup my racecards with the bf's race markets for today (using the bf api) but it failed due to api connection issues. It may have been down/iffy much before then but can't say as this is when my program kicked in for this process. Btw, this process never fails and I know for sure it was either a problem with betfair or some external internet exchange somewhere? Hope this helps.
If your betting style allows, it is worth setting your exposure limit to a figure which won't clear you out in a black swan event? I have also found it helpful to have 2 forms of validation when dripping in bets: locally and from bf. I.e., before dripping in more bets, check the current liability on a selection, whether matched or not (requested through bf api), matches that of a locally stored liability amount (checking betids and txnids etc). This validation was a godsend when we had numerous Saturdays last year where the exchange went iffy around 3pm. During these iffy periods I found instances where matched/unmatched amounts as returned from BF were much lower than I had previously recorded. These understated amounts could have been very costly! The problems of technology failure! Hope you didn't lose too much. |
|
By:
Thanks for the info. Its bad code that there are not two forms of validation.
It cannot be a completely dropped connection because it wouldnt have kept on placing bets. It must have just being checking the current p and l that wasnt being updated or bet cancellations were not working and again the code doesnt validate the cancellations. Have have lost a couple of hundred before but this was £987.92. |
|
By:
I got lots of intermittent errors from 01:07 until 01:37, mostly 'service unavailable' errors reported when placing/reading bets. Reading the current odds mostly worked though.
|
|
By:
I'd say any bot should err 100% on the side of caution - if it has any doubts at all about the picture it's seeing, sit on its hands until the picture clears, regardless of whatever other API calls might be working.
|
|
By:
Yes similar problems here, with multiple bets getting placed where it's supposed to place only one.
|
|
By:
I'm possibly finding similar issues here at the moment. The market keeps sticking and freezing for seconds at a time. Either my bets aren't even hitting the market, or I'm struggling to cancel them. Makes betting/trading impossible. My internet connection is fine. Don't know what end the problem is at.
|