Weekly digest
Pick the categories you care about: movies, AI launches, sports, eclipses, and major public dates. One email per week, and never anything you did not ask for.
Want full preferences? Customize your digest →
Meeting planner.
Find the best time for meetings across multiple time zones. Add participants from different regions and see overlapping working hours at a glance.
Drag the window. Green means working hours, amber is early or late, and navy is sleep.
Add each participant's time zone, read the overlap of working hours on the timeline, and pick the hour that works best for the whole team.
Add a row for every attendee and set their time zone or city. The planner converts everyone onto a shared 24-hour scale so the cities can be compared directly.
Use the timeline and heatmap to see where everyone's working hours overlap. Hours that fall inside business hours for all participants are highlighted as the strongest candidates.
Check the suggested best time, which favours hours inside working hours for the most people, then select an hour to see the exact local time it maps to in every participant's city.
Copy a shareable link or a plain-text summary of the chosen time, or save the team so the same set of cities is ready the next time you plan a meeting.
Tool evidence
Practical use cases
Trust boundaries
Methodology
City and timezone calculations use IANA timezone identifiers where possible, so offsets follow real regional rules instead of fixed UTC shortcuts.
Meeting suggestions favor shared working hours first, then reduce sleep conflicts and spread inconvenient times more fairly.
Daylight-saving changes are date-aware. If a region changes policy, regenerated pages pick up the updated rule set from the app data pipeline.
Saved cities, teams, and preferences stay in the browser on the same device unless you explicitly share or export them.
Data-backed checks
Timezone rules
IANA tzdb
IANA identifiers keep offsets date-aware instead of fixed to one UTC shortcut.
City records
GeoNames
GeoNames-derived records anchor city pages, search, and popular hub lists.
Freshness
Apr 30, 2026
Live values render on request; editorial/source notes carry the reviewed date.
Sources: IANA tzdb, GeoNames-derived city records, Nager.Date, OurAirports, exchange calendars, and curated event source links. Source notes
Reviewed:
Live snapshots: Current times, daylight, market states, and countdown values are rendered at request time; review dates describe the underlying content, not a guarantee that authorities, exchanges, airlines, or event organizers will not change schedules.
Meetings can drift when regions change daylight saving time on different weekends. This radar calls out those risk windows.
Planning patterns
Choose a baseline time, then watch for DST drift so a weekly call does not quietly become too early or too late for one region.
Find windows where both sides are awake and within normal business hours before promising a live handoff or escalation.
When there is no perfect overlap, rotate the inconvenience instead of assigning every late night or early morning to the same office.
Decide fast
The fastest way to use a meeting planner is to stop hunting for a perfect hour and look for the clearest shared block.
Start with the cities or zones that matter most, scan the overlap heatmap, and widen the group only after you see the first workable window.
Popular pairs
Related tools
FAQ
