@furkannozzturk Sorry for keeping you waiting. It was a glitch in the free API that caused the wrong time zone in historical time. It has been corrected.
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.
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.
@PokeNemo Apologize for the issue. We encountered a network latency issue with one of the hosting providers. We are working to migrate the traffics to alternative routes.
@VcsDana Apologize for the issue. We encountered a network latency issue with one of the hosting providers. We are working to migrate the traffics to alternative routes.