Australian racing

[gazuty]

Peter, gazuty and other bot guys - Do I understand correctly that "Orders" part was fkd up for some races, but the response from bet placement/cancelation worked as usual? It's all I can get from my logs investigation because they look perfectly fine - absolutely no errors from any api part (markets data, bets data, and others (hb, keepalive)), I guess that's because I never rely on "Orders" part of api solely. But what was happening in this "Orders" part exactly? Was it some lag in their system or did they mess up order.status or order.sizeremaining data?
Just trying to understand what happened from more in-depth technical point of view.

Bets fired in to the api correctly and if not immediately matched, were available to match. However the api was not reporting back p/l exposure as a result of those bets being matched (and also the api was not reporting back unmatched bets). So manual traders could not "see" what was happening and bots that rely on exposure limits etc and that make adjustments could not respond to what had gone before.

That is as best as I can describe it.

At one point BF thought it was a Bet Angel issue (as the issue was first reported by many Bet Angel users), but the issue was not confined to Bet Angel, it applied to other software, to people who have their own bespoke software and to people who were simply using the website.

@PDC

PDC gave a good description above viewtopic.php?p=279748#p279748

[Anbell]

gazuty probably has the best description

For further 'colour', I have a old bot that is supposed to have a maximum of one bet per horse and I fluked seeing that it was cancelling bets immediately (sub second) (I normally wouldnt look at this live for months) So I turned it off but it already had 50 bets on the race. It could have drained the account in seconds.

[napshnap]

...

[Morcego]

Ask at least for a goodwill gesture payment, worse they can say is no but often they will give you something.

I emailed them and included a screenshot which showed the bets and the back bets I tried to rescue the situation that failed. Guy on the phone said screenshots would be highly beneficial but they would get back to me in 24-48 hours.

But yeah I'm just assuming it is a loss now.

could you please tell me the email address of betfair australia

[andy28]

It crippled my small set up, Last 2 weeks worked for a nice profit and all gone and some from this error. Didn't clean me out but took a bit of my small bank as well. I couldn't figure out what was going on I put bets in and they were there for like 0.5s and then looked like they were cancelled. I clicked on a price where there was no money and saw my money there. At this point I clicked on green all hoping some bets were matched and this would also cancel any unmatched bets. But clearly this didn't work. I checked the log and said bets were placed yet I couldn't see them.

I thought I had screwed a setting up so I went to a later race and could place a bet and displayed as it should. I went back to the race in question to check what my liability was and it said 0.00 so I moved on. I don't look at my balance during the day and carried on, when I did I couldn't believe what I saw, lets just say lucky the cat was outside. I was so pissed off I shut everything down and just logged on to see this thread.

Living in NZ there are only a few events I can trade live one is Aussie racing and this happens, yes I know a rare thing but I am a lay better so have a high liability so rare as it is is still costly, I used to bet on Brazilian Football but you get stung by the match being suspended from almost the start of the game, so I stopped trading there, move to MSL and same thing nowhere near as bad as Brazil but still bad enough for me to lose confidence.

Time to take a week off I think

[gazuty]

I couldn't figure out what was going on I put bets in and they were there for like 0.5s and then looked like they were cancelled. I clicked on a price where there was no money and saw my money there. At this point I clicked on green all hoping some bets were matched and this would also cancel any unmatched bets. But clearly this didn't work. I checked the log and said bets were placed yet I couldn't see them.

I thought I had screwed a setting up so I went to a later race and could place a bet and displayed as it should. I went back to the race in question to check what my liability was and it said 0.00 so I moved on.

Sorry to hear that. If you contact BF Australia and report that you may receive some kind of ex gratia payment. I understand they might (emphasis on might) be looking at something.

[andy28]

Thanks for the advice, I am just venting, its not huge figures but has dented the confidence big time, coupled with the internet outage that cost me and now this my confidence is at an all time low. That's what's pissed me off the most.

The upside is that my strategy is working I was in profit and had a good strike rate and what happened is out of my control so I just need to get up dust myself off and carry on. I am confident in my strategy so will be my path back, I will just reduce the stake size and claw my way back to where I was. If it can do that then I know I am on to something.

[andy28]

Got a goodwill payment from Betfair

[andy28]

Dear Andrew,

We would like to apologise for the disruption to our service and we would like to assure you that reliability and performance have always been and continues to be one of Betfair's top priorities.

Please be advised that the value of XXX has been credited as a once-off gesture of goodwill to apologise for the disruption yesterday.

We know that the service provided was unsatisfactory and we’d like to reassure you that site stability and performance are our absolute priority. We'll be taking all necessary steps to reduce the risks of these failures in the future.

Please do not hesitate to contact us if you have any further enquiries.

Kind Regards,

Bree

[napshnap]

Thanks for the advice, I am just venting, its not huge figures but has dented the confidence big time, coupled with the internet outage that cost me and now this my confidence is at an all time low. That's what's pissed me off the most.
...

Must say this kind of problems in aus horseracing markets are rare and happen 1-2 times a year, so you just got very unlucky with that.

[andy28]

Yeah your right, at the end of the day I just got to worry about what I can control, lesson learnt

[gazuty]

For those awake in the UK or who wake early, Caulfield carnival continues today with a midweek G1 coming up later in the Australian afternoon.

[andy28]

Port Lincoln Race 5 couldn't cancel bets or green up. Froze for about 20s so I think I will sit out next few

[Euler]

For those awake in the UK or who wake early, Caulfield carnival continues today with a midweek G1 coming up later in the Australian afternoon.

Wednesdays seem to be a graveyard for me at the moment and my automation. Even if there is quality on the card, not sure why.

[Katla]

Peter, gazuty and other bot guys - Do I understand correctly that "Orders" part was fkd up for some races, but the response from bet placement/cancelation worked as usual? It's all I can get from my logs investigation because they look perfectly fine - absolutely no errors from any api part (markets data, bets data, and others (hb, keepalive)), I guess that's because I never rely on "Orders" part of api solely. But what was happening in this "Orders" part exactly? Was it some lag in their system or did they mess up order.status or order.sizeremaining data?
Just trying to understand what happened from more in-depth technical point of view.

Bets fired in to the api correctly and if not immediately matched, were available to match. However the api was not reporting back p/l exposure as a result of those bets being matched (and also the api was not reporting back unmatched bets). So manual traders could not "see" what was happening and bots that rely on exposure limits etc and that make adjustments could not respond to what had gone before.

That is as best as I can describe it.

At one point BF thought it was a Bet Angel issue (as the issue was first reported by many Bet Angel users), but the issue was not confined to Bet Angel, it applied to other software, to people who have their own bespoke software and to people who were simply using the website.

@PDC

PDC gave a good description above viewtopic.php?p=279748#p279748

Do you know if there could have been problems with lay och back odds aswell showing wrong odds?

There are reports of back odds showing to be higher then lay odds on the ladders. And when backchecking logs and compare them with the betting statement on betfair.com I find that I for example had 150 bets matched with 20 seconds between each bet, which is the reload time my bot has. Those bets were to be placed 5-15 ticks below the back price but were matched directly. Since this is on football it has not to do with "natural oddsmovement". So my conclusion is that my bot must have thought the odds were something else then it actually was.