Bug Reports

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

657 Responses to “Bug Reports”

  1. Admin says:

    Unfortunately, I don’t have any experience with sqlite, so would be unable to test the results.

  2. Kai says:

    Hi, it seems like the Racing Point constructor points have not been updated to reflect the 15 point ‘Tracing Point’ deduction – the API returns 56 points instead of 41 after the 70th Anniversary GP.

    Great API by the way!

  3. Admin says:

    Hi Kai,
    Thanks for the warning. I hate it when they do that! Now updated.

  4. arek says:

    hi my friend, it seems like at 2016 australian gp duration of pit stops take for some teams above 18 minutes if i see well. the same with some pit stop times at 2014 and 2017 year.
    i saw it when i made avg from all pit stops

  5. mkl says:

    That’s when the entire field was in the pits for the red flag period. The official timing data counts this as a pit stop, but not consistently. You can see the previous discussion on that matter a few comment pages back: https://ergast.com/mrd/bugs/comment-page-3/#comment-14735

  6. Colo says:

    Hello, there seems to errors in the fastest laps from the 2019 Japan race. The problem is that multiple drivers don’t have their correct fastest laps. An example is Danill Kvyat’s time is reported to be 1:34.921 while the official F1 website says that it is 1:33.239. Not all drivers have the wrong fastest lap associated with them, multiple do.

  7. Admin says:

    Hi Colo,
    Thanks for the warning – now corrected.

  8. TK says:

    Hi Chris,

    Was running some queries and noticed that Kvyat’s “qualifying” record for 2019 Brazil (driverId = 826, qualifyId = 8353, raceId = 1029) has the wrong constructorId. It’s set to to Redbull (9) rather than Toro Rosso (5).


    BTW, Kvyat’s record for this race in the “results” table looks okay; constructor is set to TR.

  9. Admin says:

    Hi TK,
    Thanks for the warning – now corrected,

  10. PZ says:


    First of all hats off for this nice database, so much interesting data to look at!

    I was wondering if safety car deployments/laps where safety car was active is anywhere in the data, since I can’t find it anywhere?

    Kind regards

  11. Admin says:

    Hi PZ,
    Unfortunately not – it’s not easy to find that data.

  12. Ab says:


    I don’t understand the pitstop information from the last race (Mugello). is the ‘red flag’ period not counted?


    Great work to collect all this information.

  13. G.Letellier says:

    Application take some times to give all laptimes for a race , example https://ergast.com/api/f1/2020/9/laps.json

    , by adding an index on race table performance increase :

    ALTER TABLE `races` ADD INDEX `inxYearRound` (`year` , `round`);

  14. Miguel Bento says:

    Hi Chris,

    When checking the integrity of your database, I detected the following bugs:

    – All URLs in tables circuits, constructors, drivers and races should be https instead of http.

    – The URL for driver 806 (Oscar Gonzallez) is wrong. It should be:

    – The URL for race 909 (2014 German GP) is wrong. It should be:

    – The time for result 20992 (Hamilton, 2011 German GP) is wrong. It should be:

    – The time for result 21088 (Vettel, 2011 Singapore GP) is wrong. It should be:

    – The miliseconds for result 19302 (Hawthorn, 1954 British GP) is wrong. It should be:

    – The constructor results for races 784 and 790 (1956 Argentine and German GPs) should be removed, because the constructors championship only started in 1958.

    Thanks, and keep up the good work!

  15. Admin says:

    Hi Ab,
    Thanks for the warning – they’re now included.

  16. Admin says:

    Hi G.Letellier,
    There is a raceId index on this table so the issue is probably due to an inefficient query – I’ll try to speed it up.

  17. Kim says:


    According to Race Result, Webber should have no lap times in 2008 Italian Grand Prix.
    But there are 52 lap times named Mark Webber in 2008 Italian Grand Prix in DB.

  18. Tiago says:

    Is the McLaren info correct? They’re supposed to have 155 fastest laps but i can’t get that number from the query

  19. Admin says:

    Hi Tiago – fastest lap times are only available from the 2004 season onwards. Does that affect your query?

  20. Ab says:

    Hi Chris,

    Thank you for correcting the information about the pitstops for Mugello (round 9), but could you also correct the info for Monza (round 8). Also this race was suspended and all the cars went in the pit (and changed tyres).

    you can check with this link;



  21. Admin says:

    Hi Ab,
    Thanks for the warning – same issue.
    Now updated.

  22. Admin says:

    Hi Kim,
    The race result records 53 laps for Webber:
    Which matches the number of entries in the laps table:
    Have I misunderstood your query?

  23. Richard says:


    It looks like the Mercedes constructor standings is missing after the latest race (raceid 1040) in the csv data.

    Thanks for the great work with this.

  24. Admin says:

    Hi Richard,
    This seems to be a bug in mysql. I’ll check at the weekend but hopefully it will fix itself after the next Grand Prix.

  25. TK says:

    Hi Chris,

    Have you ever considered adding something to account for race starts like Hungary this year? Grosjean and KMag pitted after the formation lap and started from the pitlane, instead of their original grid spots.


    Wiki uses an explicit Start Grid column. Maybe adding a record in Pitstops for lap 0, to avoid a schema change?


  26. TK says:

    Btw, noticed an inconsistency with the results for 2016 Austria.

    Massa and Kvyat started from the pitlane, due to breaking Parc Ferme. But the db still has them in their original grid spots.




  27. Admin says:

    Hi TK,
    Thanks for the warning – I’ve corrected these now in 2016/9 and 2020/03 using “0” for starting in the pit lane – an approach used elsewhere in the database. With hindsight it should be a string field rather than an integer :-/

  28. Wesley says:

    Hi Chris,
    The time for the eiffel grand prix race is wrong. It should be 14:10 GMT. Right now it is 15:10 GMT.

  29. Admin says:

    Hi Wesley, I’m finding it difficult to obtain reliable start times for this year’s amended schedule. Let me know if you find a reliable source (in UTC)

  30. Hi Chris,
    It is possible to get it from the formula 1 website. You can find the complete schedule here:
    Only downside is that you have to click through the pages. You can press any race and then click on full schedule to see all the start times.

  31. Hi Chris,
    I just found something else. Look at this page, you can set it to UTC yourself:

  32. indigo-dev says:

    Regarding the calendar topic, a very good source is also https://f1calendar.com/.
    They have all session infos, and also an API. They’ve sent me the link as it’s not officially documented on their website. For season 2020 the URL looks like



  33. Thanks Daniel! Exactly what I was looking for!


  34. Hi Chris,

    The driver standing list of this season has all zeros in the Wins column.


  35. indigo-dev says:


    what has happened with the database?
    Suddenly, all of the time-consuming queries like fetching a driver’s lap times and alltime rankings perform as if they would run locally.

    This was causing me so much headache in the past, and now it kinda flies.
    Just how?

  36. Admin says:

    Hi Indigo,
    I had to move to a new server so updated to MySQL 5.7. It may be faster but several things have stopped working so I’m not as happy as you are!

  37. indigo-dev says:

    That’s unfortunate!
    I hope you get your problems sorted out. Good luck mate!

  38. Admin says:

    Hi Wesley,
    Thanks for the warning. Now corrected.

  39. Alex South says:


    I’ve noticed the positions the Monaco Grand Prix 2019 (1015) particularly are incorrect.

    Real Race Result API Result
    Ham Ham
    Vet Ver
    Bot Vet
    Ver Bot

    There were a few others throughout Monaco, I haven’t checked any other races yet but this was the first one I noticed to be incorrect

  40. theodor says:

    The race times are wrong? It listed to show UTC times but Bahrain today start 14:10 UTC not 15:10

  41. Admin says:

    Hi Alex,
    I can’t see a problem with the first four places in this race. However, Kevin Magnussen’s 5 second penalty was missed – I presume that came after I entered the results. Now corrected.

  42. Admin says:

    Hi Theodor,
    Thanks for the alert – now corrected. Not sure why that was wrong.

  43. mkl says:


    The Abu Dhabi ’20 results list gaps for P9 and P10 (Ocon and Stroll) as intervals to the driver in front, not gaps to the winner. This messes up their race times in miliseconds in the database, as well.

  44. Admin says:

    Hi mkl,
    Thanks for the warning – now corrected.

  45. Ab says:

    Hi Chris,

    I’ve found a mistake in the data:

    Season 2016 round 18 (US) pitstop information
    – the driversIds for Vettel and Raikkonen have been swapped.

    According to other websites Raikkonen did make one pitstop and Vettel two. Timing info etc are correct.


  46. Admin says:

    Hi Ab,
    Which websites are you looking at? According to the data I have they both made 3 stops at the 2016 US Grand Prix.

  47. Ab says:

    Hi Chris,

    Happy New Year to you.

    Sorry made typing mistake 2017, Sites I’ve been used are:
    – FIA archives https://www.fia.com/events/fia-formula-one-world-championship/season-2017/lap-chart-3
    – motorsport.com https://www.motorsport.com/f1/results/2017/united-states-gp-159709/?st=PT


  48. Admin says:

    Hi Ab,
    Thanks – that matches. I’ve corrected the IDs as suggested.

  49. RR says:

    Hi, is it possible to set “\N” in URL for driver Thomas Monarch?

  50. Admin says:

    Hi RR,
    The URL field isn’t nullable and changing this would require changes to the runtime. Instead, I’ve set the URL to the only place he’s mentioned in Wikipedia which is: http://en.wikipedia.org/wiki/Talk:1963_Mexican_Grand_Prix#Who_was_Thomas_Monarch.3F
    Hope that helps.

Add a Comment: