No, presently JobScheduler is able only to operate on local time of the server where the JS instance is running.
If the requirements for scheduling requests jobs running on different servers in different time zones one can taken into account that this can be achieved by
- using local instances of jobscheduler on these servers and
- with the remote configuration capability (How_does_a_supervisor_scheduler_distribute_the_%27central_configuration_directory%27%3F).
Different instances on different servers has the advantage that the JS is able to operate on the local server even if the network is broken. A local instance of a JS can operate as well at the same time as an "agent" and can execute jobs which are triggered and monitored from other JS.
The scheduling history of different instances can be stored in a single database.