how do i detect where durableobject is located ?

Here's what I do. Note that this relies on functionality that isn't guaranteed, and thus may cease to function in the future.

ts
((
  await (await fetch("https://www.cloudflare.com/cdn-cgi/trace")).text()
).match(/^colo=(.+)/m) as string[])[1]

should this be executed inside of durable object?

Yes

thanks i will have a try

i've got AMS is it amsterdam

Yes

how do i know which regions support durable objects?

because my db is in frankfurt

FRA

Here is the DO Spawn statistics for *Frankfurt(FRA)*:

39.89% Amsterdam (AMS), 60.11% Frankfurt (FRA)

So it looks like it is working fine

Or well

The colo matches

okay so if i want to reset creation i just need to change id?

Yes. Though note that this still won't guarantee being spawned in FRA, just that there is a 60.11% chance that it will

it worked thanks

it looks fine but i don't get what LAX in cf-ray means

That means that your request entered the CF network from the *Los Angeles(LAX)* colo, and was subsequently routed to FRA.

but how it that possible

I assume your ISP connects to the open internet somewhere near Los Angeles?

nah i'm from china but i use vpn that proxies me through Taiwan and accually it's correct in logs

i don't know why it displays LAX in ray

Might be a Taiwan ISP that happens to peer in LAX. BGP is weird sometimes.

?anycast

Take a look here to see why the Cloudflare datacenter you are routed towards isn't always the closest geographically: https://community.cloudflare.com/t/peering-why-dont-i-reach-the-closest-datacenter-to-me/76479

i will try to change vpn server and let's see the difference

I am trying to build a helpful twitter bot, and wondering if a durable object is the right tool for the job The bot will poll twitter every second, looking to see if it mentioned. If it is - it will send some backend request and post the result. The durable object will have to poll twitter every second, and manage which mentions were already answered or waiting for BE response I was also considering to use workers with cron and r2, or to just develop a standalone node server. What do you think? Any caveats I should expect with durable worker?