Suggestion
I would like you to clarify the rules for scheduling event periods according to the type of event, and try to resolve the confusion and disadvantages caused by time zones.
Season, limited-time, weekly, and anniversary events:
Fix all of their start and end times to either JST or UTC.
Only set community-focused local events, such as mass outbreaks and interceptions, to local time.
Current Status
There is no consistency in event times—they vary from event to event—and despite issues and inconveniences arising, this continues to be left unaddressed.
Depending on time zones:
When a local-time event starts after a unified-time event ends,
a blank period of an entire day with no events can occur depending on the time zone.
If there is a one-day gap in JST, it leads to a situation where lagging time zones have no events for two days.
When Hunt-a-thons change due to ending at local time:
The number of players who can match for Hunt-a-thons in regions where the event is still active decreases over time, and due to the active player count in that specific time zone alone, there are times when matchmaking does not happen at all.
Adopting the proposed event schedule would solve all of these current problems.