TimeZoneDB (@TimeZoneDB) profile picture

Free world time zone database in CSV and SQL format.

Joined October 2011
Photo by TimeZoneDB (@TimeZoneDB)
One of our email providers is blocking emails from our contact form. It's fixed now!
1
1
Starting 2022, all offline database releases will no longer include zone_id. This field will be deprecated and the time zone will be identified by their zone name.
4
Some users may experience high network latency with our API due to a routing issue with one of the providers in NYC. The issue is resolved now and please contact us if you still have any issues.
1
There is a caching issue in the list-time-zone interface causing some users to get gmt_offset=0. It has been solved by now.
1
The version 3 API is under development now. If you have any ideas, kindly feedback to us to be included in this version.
7
2
Having network issues with our premium service. The API response is slower right now. We are still working on this.
1
FYI, dstStart and dstEnd field has been renamed to zoneStart and zoneEnd in API v2.1.
This is awesome!
This Post is from an account that no longer exists. Learn more
2
To avoid confusions, the dstStart and dstEnd fields in our API will be renamed to zoneStart and zoneEnd.
1
Premium API was slow for over 24 hrs on 30 Jul. An abuser causing a node being shutdown. Backup server took place within 15 secs but having slow response due to API key replications. In past few days I came out with more automated backup nodes and better replication algorithms.
1
Some users were losing access to the API due to delay in key synchronization. We get them solved manually but still missed some. This is really challenging to keep our cost down and remaining highest uptime possible.
1
I has been monitoring the performance for several days. Everything is working perfectly now. If you still encountering any issues that I'm not aware of, please contact us immediately.
1
We noticed that one of our VIP service server is having slower respond that expected. We made some fixes on the network and still monitoring the performance.
1
Our main website is down due to hardware failure. We are working on it right now. API services are not affected.
SSL certificate for api.timezonedb.com is expired today. Just renewed it.
1
1