Aye, it is indeed down, that's sad. The isochrones are loaded over the network on mouse hover. I thought that scheme would keep working and remain fast since t

Aye, it is indeed down, that's sad. The isochrones are loaded over the network on mouse hover. I thought that scheme would keep working and remain fast since the loaded vector data is completely static. I guess the /api/isochrones/<id> url does point to some server-side code which couldn't keep up, unfortunately. Actually, Vercel is returning "This Serverless Function was rate limited." and a 429 code i.e. too many requests. So it's more of a "hitting the limits of the Vercel plan" problem than anything.