# Scheduling a meeting across three zones

**Mon, 2026-06-15, 09:00 in America/Chicago is Mon, 2026-06-15, 22:00 in Asia/Singapore.**

- Input: `2026-06-15 09:00` in `America/Chicago`
- Target zone: `Asia/Singapore`
- UTC instant: 2026-06-15T14:00:00.000Z

## Readings

| Zone | Local time | Offset | Abbreviation |
| --- | --- | --- | --- |
| America/Chicago | Mon, 2026-06-15, 09:00 | UTC−05:00 | CDT |
| Asia/Singapore | Mon, 2026-06-15, 22:00 | UTC+08:00 | GMT+8 |

## Warnings

### Asia/Singapore does not observe daylight saving (info)

Asia/Singapore keeps the same offset all year, so its clocks never change. If the other zone does observe it, the gap between them shifts twice a year even though nothing changes on this side.

## Upcoming clock changes in America/Chicago

- `2026-11-01T07:00:14.062Z`: Clocks fall back an hour: the wall clock returns to 01:00, so that hour happens twice.
- `2027-03-14T08:00:00.000Z`: Clocks jump forward an hour: 01:59 is followed by 03:00, and the times in between never happen.

## Upcoming clock changes in Asia/Singapore

None — this zone keeps one offset all year.

---

Canonical URL: https://timezone-truth.gumballtools.com/tz/meeting-across-timezones
JSON API: `GET https://timezone-truth.gumballtools.com/api/v1/convert?time=...&from=...&to=...`
MCP endpoint: `https://timezone-truth.gumballtools.com/api/mcp`