# The local time that happens twice

**Sun, 2026-11-01, 01:30 in America/New_York is Sun, 2026-11-01, 05:30 in UTC — but that local time happens twice.**

- Input: `2026-11-01 01:30` in `America/New_York`
- Target zone: `UTC`
- UTC instant: 2026-11-01T05:30:00.000Z
- Both candidates: `2026-11-01T05:30:00.000Z` and `2026-11-01T06:30:00.000Z`

## Readings

| Zone | Local time | Offset | Abbreviation |
| --- | --- | --- | --- |
| America/New_York | Sun, 2026-11-01, 01:30 | UTC−04:00 | EDT |
| UTC | Sun, 2026-11-01, 05:30 | UTC+00:00 | UTC |

## Warnings

### That local time happens twice (error)

01:30 on 2026-11-01 occurs twice in America/New_York, because the clock went back over it. Both candidate instants are listed, and they are a real hour apart. Every library silently picks one; which one it picks is rarely documented.

**Fix:** Say which occurrence you mean by giving the UTC offset explicitly, or store the instant rather than the local time.

### UTC does not observe daylight saving (info)

UTC 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/New_York

- `2026-11-01T06:00:14.062Z`: Clocks fall back an hour: the wall clock returns to 01:00, so that hour happens twice.
- `2027-03-14T07: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 UTC

None — this zone keeps one offset all year.

---

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