Bug Reports

If you identify any API bugs or errors in the data please record them here.

Comments

796 responses to “Bug Reports”

  1. dot Avatar
    dot

    Hello, yeah, Alonso one more time got 3rd place. It’s official:

    https://www.formula1.com/en/latest/article.breaking-fernando-alonsos-saudi-arabian-grand-prix-podium-reinstated-after.1QaHGAtZu9W5k6nYsnR1id.html

    So need to change those points values and position.

  2. alex Avatar
    alex

    Hi – the CSV database images have not updates

  3. Jon Avatar
    Jon

    I notice there are some endpoints that have data from the Saudi Arabia and others that do not. When do you anticipate those will be updated?

  4. Brandon Avatar
    Brandon

    Just FYI – It also looks like Fastest Lap data is not in the JSON response for Round 2, but it is in Round 1:
    http://ergast.com/api/f1/2023/2/results.json

  5. Rolandas Avatar
    Rolandas

    The Fastest Lap results have been included in the Round 2 results, but they are incorrect in terms of positions and times.

  6. Edvardas Avatar
    Edvardas

    Saudi Arabian Fastest laps still have incorrect fastest lap (Still says that Perez got it even though Verstappen got the fastest lap).

  7. Caitlin Avatar
    Caitlin

    Nyck de Vries’s number is outputting as 45, which is the number he ran with Williams last year, but his current number at AlphaTauri is 21.

  8. Admin Avatar
    Admin

    Hi Caitlin,
    Thanks for the warning – now fixed.
    I thought driver numbers were meant to be permanent!
    Cheers,
    Chris

  9. Admin Avatar
    Admin

    Jon, Alex, Jocke,
    Apart from the race results, the FIA data was published a couple days late for Jeddah – and it has errors.
    Chris

  10. Admin Avatar
    Admin

    Edvardas, Rolandas, Brandon,
    The FIA data was published a couple days late for Jeddah – and it appears it has serious errors. I’ve never seen this before. I will check and correct the data but it will have to be done manually.
    Cheers,
    Chris

  11. Brandon Avatar
    Brandon

    No worries – I appreciate the update!

  12. Admin Avatar
    Admin

    Hi all,
    The fastest laps errors in the Jeddah results have been corrected.
    Cheers,
    Chris

  13. Jeremy P Avatar
    Jeremy P

    Hi, seeing Perez and Bottas have a “grid: 0” as their starting positions the 2023 Australian Grand Prix. Both started from the pit lane, so wondering if that is expected behavior or needs to be looked at/fixed. Looking at this endpoint: http://ergast.com/api/f1/current/last/results.json (or https://ergast.com/api/f1/2023/3/results.json if Baku has already happened)!

    Thanks!
    Jeremy

  14. Remco Avatar
    Remco

    Hi,

    Concerns f1, 2023, round 3 race results.

    According to https://www.formula1.com/en/results.html/2023/races/1143/australia/race-result.html, positions 13-20 did not finish: DNF.

    The api return only positions 18-20 as Retired: R

    Why?

  15. Philipp Avatar
    Philipp

    Hi, occasionally the API responds with “Unable to select database” which is totally fine. But it is confusing that this messages has the HTTP Status Code 200 while this is obviously an error. It makes handling of this a bit unintuitive. Maybe this could be changed at some point?
    Regards, Philipp

  16. Admin Avatar
    Admin

    Hi Jeremy, That’s correct. There’s a note in the results table documentation. It stems from a poor decision to make the field an integer when building the database was first built.
    Cheers,
    Chris

  17. Admin Avatar
    Admin

    Hi Remco,
    I’ve always used “Retired” if drivers aren’t running at the end of the race. I would use “Not Classified” if they were running but failed to cover enough race distance to be classified. This approach was probably inherited from Wikipedia when the historical data was ingested. This is what they’ve put for the Australian Grand Prix: https://en.wikipedia.org/wiki/2023_Australian_Grand_Prix
    Cheers,
    Chris

  18. Admin Avatar
    Admin

    Hi Philipp,
    Good suggestion. Unfortunately, I’m currently having trouble with Apache/PHP (after over a decade with no issues).
    Cheers,
    Chris

  19. Ab Avatar
    Ab

    Hello Chris,

    Do you have already an idea how you will implement the new Sprint Qualification? Do you for see other changes due to the new Sprint format?

    Thank you for your hard work to keep this data up-to-date,

    Ab

  20. Brandon Avatar
    Brandon

    Just a quick heads up..the fastest lap data is missing again in the Round 4 JSON:
    http://ergast.com/api/f1/2023/4/results.json

    Thanks!

  21. Joey Avatar
    Joey

    i noticed that the time for Practice 1 and 2 for the Miami GP are incorrect, since the offset i normally need is +2 hours to match it with my local timezone but for P1+P2 of Miami i suddenly need +3 hours offset

    Also wanted to say thank you for making this API possible 😀 keep up the good work

  22. Admin Avatar
    Admin

    Hi Ab,
    Not sure I can do anything about this in the near future. At least the grid positions from the Sprint Qualification session will be in the Sprint Race results.
    Cheers,
    Chris

  23. Admin Avatar
    Admin

    Hi Brandon,
    Yeah, the FIA didn’t publish the data until today. I’ve added it this evening.
    Cheers,
    Chris

  24. Admin Avatar
    Admin

    Hi Joey,
    Thanks, I’ll update. The schedule in the API was set before the season started so maybe they changed it.
    Cheers,
    Chris

  25. MH Avatar
    MH

    The query for constructor standings after the xth race of yearY does not seem to work.

    Example:
    # Constructor standings after the 16th race of 2007
    pyergast.constructor_standings(2007, 16)

    gives the same result as:
    pyergast.constructor_standings(2007, 1)
    pyergast.constructor_standings(2007, 2)

  26. Admin Avatar
    Admin

    Hi MH,
    These queries all give different results as expected:
    https://ergast.com/api/f1/2007/1/constructorStandings
    https://ergast.com/api/f1/2007/2/constructorStandings
    https://ergast.com/api/f1/2007/16/constructorStandings
    So I think this is a bug in pyergast, which was developed by Weiran Yu rather than Ergast. You can raise issues here: https://github.com/weiranyu/pyErgast/issues
    Cheers,
    Chris

  27. Chris Avatar

    Hello, times for Lewis Hamilton and George Russel are not correct for Miami Grand Prix (season 2023 and round 5)

  28. Mark Avatar
    Mark

    Hi,

    How complete and correct the historical data is?
    I’m using the database image you post after each race and I noticed that some historical data is missing. For example, there’s no record on Niki Lauda (driverId = 182) in the qualification table whatsoever. The endpoint http://ergast.com/api/f1/1975/drivers/lauda/qualifying returns nothing as well (he had 9 pole positions in 1975).

    Best,
    Mark

  29. Dan Avatar
    Dan

    As Chris says, the finishing times for the Mercedes drivers in Miami appear to be wrong, and also the same two drivers and Logan Sargeant in Azerbaijan. As others have said, thanks very much for maintaining this amazing resource – much appreciated.

    Dan

  30. Shaykat Avatar
    Shaykat

    Hello. I’m building an app to analyse f1 race data using this API, but I would like to add informations about tyres used at each lap. Is it possible to add this feature to the laps API and/or pitstops API ?

  31. Admin Avatar
    Admin

    Hi Mark,
    Each documentation page gives some idea of the completeness of the data e.g. the Qualifying Results page states that “results are only fully supported from the 2003 season onwards”.
    Cheers,
    Chris

  32. Admin Avatar
    Admin

    Hi Shaykay,
    Unfortunately, I’ve never been able to find a reliable and consistent source of tyre data.
    Cheers,
    Chris

  33. Admin Avatar
    Admin

    Hi Chris,
    Thanks for the warning – now corrected.
    Chris

  34. Admin Avatar
    Admin

    Thanks Dan – now corrected. There seems to be more bugs this year so I’ll have to do more checking.
    Cheer,
    Chris

  35. Mark Avatar
    Mark

    Hi Chris,

    The starting position of VER in the last race results is incorrect (https://ergast.com/api/f1/current/last/results). “grid” for VER must be 9 instead on 0.

    Best,
    Mark

  36. Admin Avatar
    Admin

    Thanks Mark – now corrected
    Chris

  37. ewald kuiper Avatar

    Look that the f1 api not avaliable is. Get a connection refused when i tried to connect to https://ergast.com/api/f1/2023/6/result.json

  38. Robert Avatar
    Robert

    Hi, can you check the api access on ergast.com with ssl? Seems like HTTPS is not working anymore, only HTTP is working.

    Kind regards,
    Robert

  39. Sachin Avatar
    Sachin

    Hi,

    I am just wondering why my connection to this site is no longer secure since two days ago? Originally I was encountering an error that said “Error establishing database connection” and could not reach this site/fetch data from the API. I can now access this site but the connection is no longer secure and still, I cannot fetch data from the API.

    Kind Regards,
    Sachin

  40. Flemming B Avatar

    First of all, thank you for a great API! Next up –

    https seems to be broken. I can access

    http://ergast.com/api/f1/2023/3/results.json

    but not

    https://ergast.com/api/f1/2023/3/results.json

    Is this an error or is https no longer supported?

    Reagrds
    Flemming B

  41. Namob Avatar
    Namob

    Cant make https requests to the api

  42. Luca Avatar
    Luca

    Hi,
    this api returns 500 code and the content looks truncated
    http://ergast.com/api/f1/2023/1/driverStandings.json

  43. y34hbuddy Avatar
    y34hbuddy

    Your new SSL certificate for ergast.com is not trusted by Python clients due to a missing intermediate CA certificate.

    Also verified here: https://www.sslchecker.com/sslchecker

  44. Christian Avatar
    Christian

    Hello Chris,

    As y34hbuddy wrote yesterday: the new certificate from 2023-05-31 also does not work when using nodeJS. It ends up throwing a “UNABLE_TO_VERIFY_LEAF_SIGNATURE” error.

    Regards,
    Christian

  45. rgaloc Avatar
    rgaloc

    Will it be possible to fix the issue of the intermediate CA certificate in python?

  46. Toquete Avatar
    Toquete

    The same SSL certificate error that y34hbuddy reported is happening on Android clients too.

  47. Aymar Avatar

    Hello !

    I think this is the same for Node.js apps, as i’m not able to fetch the API anymore, through my Next.js application.

    (I’m only using this endpoint : https://ergast.com/api/f1/2023.json)

    “Error: connect ECONNREFUSED ::1:52916
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
    errno: -61,
    code: ‘ECONNREFUSED’,
    ….”

  48. y34hbuddy Avatar
    y34hbuddy

    Thanks for resolving the SSL certificate issue!

  49. sperry Avatar
    sperry

    It looks like the cancelled Emilia Romagna Grand Prix is still being listed as “Round 6” on the F1 schedule, with Monaco as “Round 7”, however Monaco’s results are under Round 6 in the API.

    Is this intentional? Is there a chance that it will be updated in the future to align with F1’s numbering?

  50. Admin Avatar
    Admin

    Hi y34hbuddy,
    Thanks for confirming it’s working. Apologies for the breakage.
    Cheers,
    Chris

Leave a Reply

Your email address will not be published. Required fields are marked *