# Isochrones \> 60 minutes

**URL:** <https://ask.openrouteservice.org/t/isochrones-60-minutes/8060>\
**Category:** openrouteservice\
**Created:** [September 21, 2026, 5:15pm UTC](https://ask.openrouteservice.org/t/isochrones-60-minutes/8060 "2026-09-21T17:15:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eduardo\_Bienkowski](https://ask.openrouteservice.org/user_avatar/ask.openrouteservice.org/eduardo_bienkowski/32/4602_2.png) [@Eduardo\_Bienkowski](https://ask.openrouteservice.org/u/Eduardo_Bienkowski)\
**Post date:** [September 21, 2026, 5:15pm UTC](https://ask.openrouteservice.org/t/isochrones-60-minutes/8060/1 "2026-09-21T17:15:58Z")

</div>

Hi,

is it possible to create isochrones for travel times above 60 minutes? Exactly 90 minutes

---

<div class="post-metadata">

**Author:** ![jschnell](https://ask.openrouteservice.org/user_avatar/ask.openrouteservice.org/jschnell/32/971_2.png) [@jschnell](https://ask.openrouteservice.org/u/jschnell)\
**Post date:** [September 22, 2026, 6:37am UTC](https://ask.openrouteservice.org/t/isochrones-60-minutes/8060/2 "2026-09-22T06:37:37Z")

</div>

Hey,

the hosted openrouteservice at [api.heigit.org](http://api.heigit.org) does not allow for this.  
The [API restrictions](https://openrouteservice.org/restrictions/), which include the 60min isochrone time limit for driving profiles, are a hard limit on the hosted APIs capabilities.

You can however set up your own openrouteservice instance and configure that as you like.  
Several different [installation instructions](https://giscience.github.io/openrouteservice/run-instance/) exist for any needs, and you can [configure your isochrones endpoint as you like](https://giscience.github.io/openrouteservice/run-instance/configuration/endpoints/isochrones).

Best regards