We are a small team focused on timezone accuracy. We read every message but cannot always reply individually. Use the appropriate channel below for the fastest response.
Found an incorrect UTC offset, wrong city name, or outdated DST rule? Include the page URL, what the data currently shows, and what the correct value should be.
corrections@currenttimein.netResponse within 48 hours
Questions about the site, press inquiries, partnership proposals, or feedback about a feature? Use this address for anything that does not fit the data error category.
hello@currenttimein.netResponse within 5 business days
For GDPR data requests, newsletter unsubscribes, or privacy-related questions, see our Privacy Policy or email privacy@currenttimein.net.
Email corrections@currenttimein.net with the page URL, the time currently displayed, and the correct time (with a source if possible). Our clocks rely on the IANA timezone database and your browser's system clock. If your device clock is out of sync, the displayed time will be off by the same amount.
We do not offer a public API at this time. Our timezone data comes from the IANA Time Zone Database, which is public domain and freely available. For city data, see GeoNames (Creative Commons Attribution 4.0).
We include all cities with a population over 1,000 from the GeoNames database (approximately 166,000 places). If your city is missing, it may not be in the GeoNames dataset. Send the city name, country, and approximate population to hello@currenttimein.net and we will investigate.
No. We display timezone data from the IANA database but cannot answer questions about specific timezone legislation. For authoritative timezone rules, consult the IANA Time Zone Database directly or your national government's official time authority.