Bug Reports

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

Comments

820 responses to “Bug Reports”

  1. Michel Avatar
    Michel

    Thanks again for providing the data. It seems some stop and lap values for pitstops are turned around.

    For example https://ergast.com/api/f1/2024/1/pitstops/12
    this should be stop: 1 and lap: 12.

    Is going wrong for the pitstops below:
    https://ergast.com/api/f1/2024/1/pitstops/12
    https://ergast.com/api/f1/2024/1/pitstops/13
    https://ergast.com/api/f1/2024/1/pitstops/33
    https://ergast.com/api/f1/2024/1/pitstops/34

  2. Admin Avatar
    Admin

    Thanks Michel – now corrected.
    Cheers,
    Chris

  3. Dan Avatar
    Dan

    Hello! Thanks for all the great work.

    I noticed that the race schedule results, such as http://ergast.com/api/f1/current/next are not currently including the times of all the race sessions like they did in previous years.

    Is there any plan to add in session times for this season?

    Thanks!

  4. Luigi Avatar
    Luigi

    Hello! Thanks for all the great work Chris.

    The race table on database image not including any times and date for Fp1,Fp2,Fp3 Sprint and pole

    Is there any plan to add them in for this season?

    Thanks!

  5. Dan Avatar
    Dan

    The Chinese GP has a sprint race according to https://www.formula1.com/en/racing/2024/China.html

    Currently, the API is showing China as a regular race with no sprint. Could you please update this so that the correct session names appear on http://ergast.com/api/f1/current/5.json ?

    Thank you!

  6. Ab Avatar
    Ab

    Thank you the hardwork on the Ergast database. In the latest version of the csv files is nr 842 (Pierre Gasly) missing.

    840,”stroll”,18,”STR”,”Lance”,”Stroll”,”1998-10-29?,”Canadian”,”http://en.wikipedia.org/wiki/Lance_Stroll”
    841,”giovinazzi”,99,”GIO”,”Antonio”,”Giovinazzi”,”1993-12-14?,”Italian”,”http://en.wikipedia.org/wiki/Antonio_Giovinazzi”
    843,”brendon_hartley”,28,”HAR”,”Brendon”,”Hartley”,”1989-11-10?,”New Zealander”,”http://en.wikipedia.org/wiki/Brendon_Hartley”
    844,”leclerc”,16,”LEC”,”Charles”,”Leclerc”,”1997-10-16?,”Monegasque”,”http://en.wikipedia.org/wiki/Charles_Leclerc”

  7. Ab Avatar

    Mine statement above is not correct. Gasly is in the list about 400 places higher.

    Although the list appears to be sorted, it is not.

    Thanks
    Ab

  8. Robert Avatar
    Robert

    Hi,

    I see from the current driverstandings that the permanentNumber from verstappen is not correct. It should be “1” and it’s still “33”.

    But many thanks for providing all these data, makes me very happy! 🙂

    Regards,

  9. Dan Avatar
    Dan

    Hello! Could you please add a “code” property for Oliver Bearman’s “Driver” object. Currently this property is missing for him but is included for all other 2024 drivers.

    Thank you as always!

  10. Admin Avatar
    Admin

    Hi Robert – IIRC permanent numbers don’t change but drivers can opt to use “1” whilst they’re world champion. Hence the API provides both a “number” and “permanentNumber” field.
    Cheers,
    Chris

  11. Reuben Avatar
    Reuben

    Oliver Bearman currently has no date of birth (empty string) – see https://github.com/ReubenFrankel/tap-f1/issues/21.

    Thanks for your work on the API!

    Cheers,
    Reuben

  12. Admin Avatar
    Admin

    Hi Reuben,
    Thanks for the warning – now corrected
    Chris

  13. ash Avatar
    ash

    current driverStandings and current constructorStandings don’t work

  14. Admin Avatar
    Admin

    Hi Ash,
    Standings look ok from here. What’s the issue?
    Chris

  15. Craig Thomas Avatar
    Craig Thomas

    Hi Admin.

    Thanks for this awesome resource and all your efforts to keep it going for so long – I do hope the site/API is able to continue beyond 2024.

    I think there may be an issue with the fastest lap times in the 2023 Austrian race results – they seem out of sequence or attached to the wrong driver compared to the FIA results document.

    Please compare:
    http://ergast.com/api/f1/2023/9/results.json
    To the FIA final classification document:
    https://www.fia.com/sites/default/files/decision-document/2023%20Austrian%20Grand%20Prix%20-%20Final%20Race%20Classification.pdf

    (Apologies if your results are the correct ones.)
    I hope you can check and clarify if the API’s JSON results are correct or not?

    Thanks

  16. Mark Herring Avatar
    Mark Herring

    Hi, thanks for all your great work. I’m having some issues with pitstops. For example if I use:-

    http://ergast.com/api/f1/current/4/pitstops.json

    I believe this should get me all the pitstops for the last race at Japan 2024 in JSON format?

    What I am getting is the first 30 pitstops (which matches what is on the Formula 1 site https://www.formula1.com/en/results.html/2024/races/1232/japan/pit-stop-summary.html) but then there seems to be a further 24 missing from the end. The data seems to be there as I can run something like:-

    http://ergast.com/api/f1/current/4/drivers/hamilton/pitstops.json

    and I can see all of his pitstops including ones that are in the missing 24.
    For the 2024 races so far I’m seeing

    Bahrain – Found 30 missing 13
    Saudi Arabia – Found 19 missing 0
    Australia – Found 30 missing 6
    Japan – Found 30 missing 24

    30 seems to be a limiting factor for some reason.

    Hope you can help.

  17. Craig Thomas Avatar
    Craig Thomas

    This years Saudi result doesn’t seem to match up with the FIA results order. In particular Tsunoda and Sargeant are not in the same order – it may be that the penalties for Tsunoda were not included in the Ergast results?

    Ergast Results:
    https://ergast.com/api/f1/2024/2/results.json

    FIA Results:
    https://www.fia.com/sites/default/files/decision-document/2024%20Saudi%20Arabian%20Grand%20Prix%20-%20Final%20Race%20Classification.pdf

  18. Admin Avatar
    Admin

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

  19. Admin Avatar
    Admin

    Hi Mark,
    Have a look at the section on Response Paging in the API documentation. The default response size is 30. You can get all the pitstops in one query by setting a higher limit e.g.
    https://ergast.com/api/f1/current/4/pitstops.json?limit=100
    Cheers,
    Chris

  20. Admin Avatar
    Admin

    Thanks Craig – now corrected
    Cheers,
    Chris

Leave a Reply

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