Country Names Change More Often Than You Think (August 2026)
Most teams treat country lists as set-and-forget.
They are not.
In late August 2026, two real-world changes landed that affect address forms, onboarding flows, billing addresses, and anything that displays official country or region names.
If you hardcoded a JSON file six months ago, your users may already be seeing outdated labels.
Nauru is now Naoero
Following a constitutional change, the official short name of country code NR is no longer Nauru. It is Naoero. The formal name is now the Republic of Naoero.
District codes and boundaries did not change. Only the country name your users read on screen.
That matters anywhere you show:
- a country picker
- shipping or billing country labels
- compliance or KYC copy tied to official names
- printed or PDF documents generated from your database
Indonesia: one province name corrected
ISO also corrected a spelling mistake in the official name of Highland Papua (Papua Pegunungan): Papua Pengunungan is now Papua Pegunungan.
Small typo. Easy to miss.
Hard to explain to a user in Indonesia who selects their province and sees the wrong spelling in your form.
If you use CountriesDB, you are already covered
These updates are live in the CountriesDB database and API. No migration steps. No manual patch on your side.
The Indonesia subdivision fix (Papua Pegunungan) shows up in official subdivision data as soon as you load subdivisions for ID. That path does not depend on how country display names are rendered.
For country code NR, how you see Naoero in a widget depends on one setting:
Default widget mode uses localized country display names from Unicode CLDR. That is a separate upstream dataset from ISO 3166. CLDR typically catches up on renames months after ISO publishes them. Until then, NR may still read as "Nauru" in default mode even though our ISO records already say Naoero.
ISO Country Names mode reads ISO short names straight from our database. Enable it with iso_country_names=1 on the widget script URL, or isoCountryNames: true in window.CountriesDBConfig. You should see Naoero immediately. See the ISO Country Names example.
That is the point of using a maintained country database instead of copying a CSV once and hoping it stays true. When ISO moves faster than CLDR, you can opt into ISO names and stay current without waiting for CLDR to catch up.
If you maintain your own list, check these now
Search your codebase or CMS for:
Nauruwhere you mean the country NRPapua Pengununganin Indonesian subdivision data
Update the source, redeploy, and retest any flows that validate country or province names against a static allow-list.
Or stop maintaining the list yourself. Start with the free API plan and let us handle the next change too.
Why we publish these updates
Country data is infrastructure. When ISO changes a name, someone has to notice and fix it, or your product quietly goes stale.
We track official ISO 3166 changes and keep CountriesDB aligned so you can focus on your app, not geopolitical spelling.
For the bigger picture on why static datasets fail over time, read Why Open-Source Country Datasets Break in Production.