On Tuesday May 31 we are going to be migrating the entire HTR app (website, vendor dashboard and admin panel) to all new infrastructure along with upgrading over a dozen libraries which is a massive project that we have been working on over the last 7-months.

While we've tested the new infrastructure extensively in a staging environment, given the scope of the project it is inevitable for small issues and edge cases to arise which we'll be logging here to keep clients up to date. 

Please let us know if you run into any issues that are not logged below so we can work to reproduce and resolve them as quickly as possible.

🙏 We appreciate your patience and understanding and hope to have all issues resolved by Friday June 2nd

HTR recently became aware of an edge case related to the mapping of country codes to regions that was introduced along with the deployment of the Poseidon Algorithm update that we are working on a patch for that will be deployed in the next couple of days (expected go live week of 11/22).

• Impact: Minor.  Impacted only select countries and select reviews.  Some companies may have experienced slightly deflated region and country bonuses if they had reviews from select countries that had mapping issues when the user selected their location via the Google Places API.
• Issue: Edge case identified where certain country codes were not mapped properly to their region and/or country as it pertains to the calculation in the HT Score algorithm related to global reach bonuses.

What happened?

HTR typically pulls country data from the popular Google Places API (excluding mainland China reviews); however, a select group of countries and regions were found to be “unmatched” in the lookup function causing some vendors to experience artificially deflated country counts in their HTScore indexes.

Which countries were identified to have potential mapping issues?

Below is a list of countries that had anomalous entries in the database and were updated in the lookup function.  One such example is that 517 reviews in the database were classified as originating in ‘Czechia’ while the HTScore algorithm lookup function was searching for the term “Czech Republic” as defined by the Google Places API.

Please note that only a fraction of cases were impacted by these mapping issues in these countries so just because a country is listed does not mean all reviews from that country were not mapped correctly.

List of impacted regions:

• 'Virgin Islands
•  'United States of America'
•  'United Kingdom'
•  'Turks and Caicos Islands'
•  'Tanzania'
•  'Spain'
•  'Seychelles'
•  'Saint Martin (French part)'
•  'Saint Barthélemy'
•  'Russian Federation'
•  'Poland'
•  'Norway'
•  'Netherlands'
•  'Netherlands Antilles'
•  'Myanmar'
•  'Morocco'
•  'Maldives'
•  'Macedonia'
•  'Luxembourg'
•  'Korea
•  'Italy'
•  'Ireland'
•  'Greece'
•  'Germany'
•  'Gambia'
•  'France'
•  'Finland'
•  'Czech Republic'
•  'Congo (Kinshasa)'
•  'China'
•  'Belgium'
•  'Bahamas'
•  'Australia'
•  'Austria'
•  'Switzerland'
•  'Brunei Darussalam'
•  'Hungary'
•  'United Arab Emirates'
•  'Estonia'
•  'Fiji'
•  'Indonesia'
•  'Sweden'
•  'Cyprus'

Who was impacted and what was the impact?

Most vendors will not notice any difference in their scores or the scores of other products in their categories.  That said, vendors with reviews from the following countries MAY have been impacted; however, not necessarily as these were anomalies and in many cases the review countries were properly classified.  Impacted vendors may have experienced an increase in countries and regions served which would in many cases increase HTScores from understated scores previously visible on the platform.  These changes are extremely rare and likely unnoticeable but some vendors may notice a several point increase in scores as the algorithm begins detecting their accurate country and region counts once the mapping patch goes live.

It has been brought to our attention that some users may be experiencing a site routing issue.  HTR's hosting provider had an issue this morning that overwrote our DNS settings and was quickly resolved but may take up to 24-hours to propagate.

The issue has been resolved but we appreciate your patience as it may take up to 24-hours for some users to be able to access the site without the error message.