Bug Reports

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

657 Responses to “Bug Reports”

  1. Noam says:

    Thanks for your amazing database which allows to do so many insightful analysis.
    I noticed an error in the United States Grand Prix 1991 (raceId 305). Time delta for Piquet and Modena are wrong (+1:17 and +1:25), it is actually (+17s and +25s) (see formula1.com/en/results.html/1991/races/559/united-states/race-result.html )

    However, I was wondering if it is possible to add to the db Qualifying and Fastest Laps data for races available on the F1 website as their archives are quite complete.

  2. Noam says:

    Another small mistake is in the name of Boy Hayje (driverId 257), his surname is Lunger in the database

  3. Filip says:


    The wikipedia url (http://en.wikipedia.org/wiki/Marshall_Teague) for Marshall Teague seems to not land at the correct page. It lands at an intermediary page. I believe this is the correct one: https://en.wikipedia.org/wiki/Marshall_Teague_(racing_driver)

  4. Admin says:

    Thanks Filip – now corrected.

  5. Nick Xitco says:

    Hi there 🙂 big fan of your work, thank you for everything.

    For the 2020 Styrian GP qualifying, it looks like Kimi got Magnussen’s Q1 time of 1:21.140. Kimi should have a Q1 time of 1:21.372

  6. F1_charts says:

    Hi! I think there is bug in status of raceId = 1085 (France 2022) for driverId = 855 (Zhou). Currently status is 16 (+6 laps), but it was technical DNF caused by Power Unit as in https://en.wikipedia.org/wiki/2022_French_Grand_Prix
    I know that official results says +6 laps, but I suppose it should be DNF

  7. Christian says:

    Regulations say “Cars having covered less than 90% of the number of laps covered by the winner (rounded down to the nearest whole number of laps), will not be classified.” Winner in France covered 53 laps, 90% rounded down is 47 laps. Zhou completed exactly 47 laps, so he was classified 6 laps down, no DNF. I think his result is correct. 🙂

  8. F1_charts says:

    Christian, classifed/not classified is not same as DNF/not DNF. Driver can have DNF and still be classified.

    Look at Bottas at Hungary (1086 raceId) – situation is the same, he was classified as he completed 90% of race (so he has position), but in result/status he has DNF (status = 131) caused by Powr Unit failure. That is correct I think. Look at official result:


  9. F1_charts says:

    Hi, it seems that data about fastest laps is missing for last race (1089)

  10. Admin says:

    Hi F1_charts
    Thanks for the warning – now corrected.

  11. F1_charts says:

    Thank you Admin!

    One more thing – Pit Stop data for last race is also not available

  12. sd. says:

    The results for the 2020 Emilia Romagna Qualifying have Bottas’s “number” as 33 instead of 77 (although his “permanentNumber” is correct):


    Thank you for working on this wonderful resource!

  13. Admin says:

    Thanks sd – now corrected.

  14. emkaerr says:

    Hi Chris, there is info that database images are updated on 02/10/2022, however .csv files are still from 13/09/2022. Could you check please?

  15. Pablo says:

    Hi. In 2018 Italy GP positionText doesn’t match position starting with Ocon

  16. Kieran says:

    The 2021 Sprint result does not contain fastest lap information for Gasly

  17. Admin says:

    Thanks Pablo – now corrected.

  18. Admin says:

    Hi Kieran,
    AFAICT Gasly didn’t register any lap times in the sprint qualifying session at the 2021 Italian Grand Prix – he crashed out in the first lap.

  19. Pablo says:

    Hi, in Spanish GP 2022, Mick Schumacher Q3 lap time should be 1:20.368 instead of 1:20.638

  20. Admin says:

    Thanks Pable – now corrected.

  21. Rolandas says:

    Hi, Alonso get back 7th place at USA GP 🙂

  22. Admin says:

    Thanks Rolandas – now updated.

  23. F1 Race Fan says:


    I built an iOS
    widget – https://github.com/Svalbard15/scriptable-widgets
    based on the sciptable app – https://scriptable.app/
    (Scriptable allows to use Javscript to code iOS widgets)

    As of today it’s broken.

    I am loading this API https://ergast.com/api/f1/current/next.json

    I tried to load the URL from Safari (iOS browser) but Safari can’t load it either.
    I can load the URL on Windows just fine.

    Wondering if anything changed? Maybe with the certificate?

    Thank you,
    F1 Race Fan

  24. Brandon says:

    Good evening. I noticed that P15 is missing in 2022 Round 21. http://ergast.com/api/f1/2022/21/qualifying

  25. Admin says:

    Hi Brandon,
    Thanks for the warning – now corrected

  26. Admin says:

    Hi F1 Race Fan,
    It seems to be ok this morning.
    When you try the URL in Safari what do you see? Does it hang and timeout or do you get a 403 error?

  27. Me says:

    2022 Round 21 Brazil Race – Gasly grid position should be 10, currently returning 0.

  28. Admin says:

    Thanks Me – now corrected.

  29. Enrique says:

    Not sure if this is a bug or not, but here:


    This call shows only 18 drivers, when there are really 22 in that session. It seems that the API is taking only the statistics of the drivers who have finished at least one race or something like that, since it is a problem that is repeated in the first rounds of other sessions too. These results are a bit strange.

  30. Otman says:

    Hi, First of all, thanks for you database open source.

    I notice the results for the Brazilian Sprint aren’t indicate in the URL :


    it’s normal?


  31. Pablo says:

    I saw that you added 2023 season. However, the new Las Vegas circuit has the same circuitId than old Caesars Palace Grand Prix during the 80s. It should be different, isn’t it?

  32. Admin says:

    Hi Pablo,
    Good point. Unfortunately, there isn’t a Wikipedia page for the new circuit yet – just an entry on Grand Prix page:
    which I’ve used for now.

  33. Vaibhav says:


    Thank you for the amazing databse!

    I noticed points error for Lando Norris in Round 4 of 2022 Season. Norris won 19 points that weekend but data reports 15 points.

    I came across this issue when I was calculating total career points for all drivers. I checked it for Hamilton, Leclerc and Norris. Total points for all three drivers did not match what was relfected on F1’s website. So I decided to manually check all the results for Norris and came across this error. I think Hamilton and Leclerc might have similar errors. I’ll keep you posted if I notice something.

    Thank you.


  34. Vaibhav says:


    Please ignore my last comment. I just realised that the data on F1’s website is wrong for Imola and Brazil races of 2022 season. :’)


  35. y34hbuddy says:

    I’ve noticed that the API endpoint exhibits quite a lot of downtime recently, returning HTTP 500 for most of the day and printing an error about establishing a database connection. Is this expected?

  36. Admin says:

    Hi y34hbuddy,
    Unfortunately, a technical issue has appeared in last fortnight causing the server to run out of memory every few hours. I introduced a temporary fix last night but I’m still looking for the root cause.

  37. lorand44 says:

    First of all thanks for this amazing service!

    I discovered an error: some of 2022 GPs appear as their qualis/FPs have been held in 2023. For an example at the 2022 Abu Dhabi GP the qualy date is 2023-11-19.

    Also, I would like to donate you, but I don’t have PayPal. Could you make another supporting page (like Patreon) for this purpose?

    Thank you,

  38. Admin says:

    Hi Lorand,
    Whoa – thanks for the warning. Unfortunately, the schedule is entered manually, so this is a bad case of operator error.

  39. DN says:

    The 2019 Japanese GP shows both Russell and Kubica in 16th (http://ergast.com/api/f1/2019/17/results). And the 1956 Argentine GP shows both Musso and Fangio with 5 points, but only Fangio got the fastest lap point (http://ergast.com/api/f1/1956/1/results).

  40. Admin says:

    Thanks DN – now corrected.

  41. rutherium says:


    first of all, thanks for the API.
    I noticed, that the ‘current’ parameter refers to the 2022 season. As this weekend the first race of 2023 takes place, it should refer to the 2023 season instead.


  42. Admin says:

    Hi Rutherium,
    See this part of the FAQ: http://ergast.com/mrd/faq/#shortcuts

  43. Chris says:

    Looks like you have a bug on the race endpoint : for example : 2020/1/races.json doesn’t return Qualifying object.

    Can you fix it ?


  44. Admin says:

    Hi Chris,
    The qualifying endpoint is: https://ergast.com/api/f1/2020/1/qualifying.json

  45. David says:

    I can’t access alonso’s laps (http://ergast.com/api/f1/2023/1/drivers/alonso/laps). Is it everything fine?


  46. Admin says:

    Hi David,
    It’s working for me. Note there is often a delay between the race results appearing and the lap times appearing – there was yesterday as I had to wait a while for the latter to be published.

  47. Chris says:

    I’m not talking about the results but the schedule of the qualifying,
    For 2022 season and above, an object “Qualifying” is present :
    Example : https://ergast.com/api/f1/2022/1/races.json
    But for 2021 and previous seasons, the object is not present :
    Example : https://ergast.com/api/f1/2020/1/races.json
    Best regards,

  48. Admin says:

    Hi Chris,
    Support for the qualifying, sprint and practice sessions was introduced in 2022. I’ll add a note to the documentation page.

  49. This lack of those to ask and search for one of the best Bitcoin mining pools.
    A crypto mining powerhouse has accumulated on the NYSE Sprecher burdened that one.
    As decentralized platforms and was jailed for 12 years in prison for.

  50. Rolandas says:


    Alonso get back 3th place at Saudi Arabian GP ?

Add a Comment: