Bug Reports

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

367 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.

Add a Comment: