Internal Nominatim returning a different city than that returned by the public Nominatim

Hi, our team is hosting Nominatim(app version 3.6.0) internally with the latest North America OSM data downloaded from http://download.geofabrik.de/ and TIGER data set of 2019. We recently noticed that the reverse-geocoding result of a specific coordinate from our Nominatim is a bit different from that of the public Nominatim.

Coordinate of interest: (lat: 33.88741050822116, lon:-118.26697164758119)

What public Nominatim returns:

URL: https://nominatim.openstreetmap.org/reverse?format=json&lat=33.8874564&lon=-118.2669698&zoom=18&addressdetails=1#

{
   "place_id":264864471,
   "licence":"Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
   "osm_type":"way",
   "osm_id":466977226,
   "lat":"33.88741050822116",
   "lon":"-118.26697164758119",
   "display_name":"546, East Airline Way, West Rancho Dominguez, Los Angeles County, California, 90248, United States",
   "address":{
      "house_number":"546",
      "road":"East Airline Way",
      "hamlet":"West Rancho Dominguez",
      "county":"Los Angeles County",
      "state":"California",
      "postcode":"90248",
      "country":"United States",
      "country_code":"us"
   },
   "boundingbox":[
      "33.887360508221",
      "33.887460508221",
      "-118.26702164758",
      "-118.26692164758"
   ]
}

What our internal Nominatim returns:

Command we ran:

curl 'http://localhost:8080/reverse?format=json&lat=33.8874564&lon=-118.2669698&zoom=18&addressdetails=1' -H 'pragma: no-cache'   -H 'cache-control: no-cache'   -H 'sec-ch-ua: "Google Chrome";v="89", "Chromium";v="89", ";Not A Brand";v="99"'   -H 'sec-ch-ua-mobile: ?0'   -H 'upgrade-insecure-requests: 1'   -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36'   -H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9'   -H 'sec-fetch-site: none'   -H 'sec-fetch-mode: navigate'   -H 'sec-fetch-user: ?1'   -H 'sec-fetch-dest: document'   -H 'accept-language: en-US,en;q=0.9,ru-RU;q=0.8,ru;q=0.7,es-MX;q=0.6,es;q=0.5'   --compressed

 {
   "place_id":68635125,
   "licence":"Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
   "osm_type":"way",
   "osm_id":466977226,
   "lat":"33.88741050822116",
   "lon":"-118.26697164758119",
   "display_name":"546, East Airline Way, West Rancho Dominguez, El Monte, Los Angeles County, California, 90248, United States of America",
   "address":{
      "house_number":"546",
      "road":"East Airline Way",
      "hamlet":"West Rancho Dominguez",
      "city":"El Monte",
      "county":"Los Angeles County",
      "state":"California",
      "postcode":"90248",
      "country":"United States of America",
      "country_code":"us"
   },
   "boundingbox":[
      "33.887360508221",
      "33.887460508221",
      "-118.26702164758",
      "-118.26692164758"
   ]
}

The only difference is that our Nominatim returns "city":"El Monte" while the public one doesn't, however when visually checking this specific coordinate we found that it's actually pretty far from El Monte city, so in this case, the public Nominatim works correctly by not including "city":"El Monte" in the result.

We are curious about what could cause such a difference between the results, since our internal Nominatim is using the latest released version(3.6.0) and the latest OSM data(the only difference I could think of is that we're using TIGER data set of 2019, I'm not sure if the public Nominatim is actually using TIGER data set), we'd like to get some help from the community:) Thanks in advance!