The International Date Line

The IDL is one of the more unusual artifacts of the global time-zone system: a convention rather than a geographic feature, governing where the world's calendar date changes. It zigzags through the central Pacific, has been moved by sovereign decision multiple times, and corresponds to a 26-hour spread between the most extreme zones it bounds.

This article covers the IDL's convention, the geographic zigzag, the major sovereign moves, the travel rules, the Magellan day-loss incident that illustrated the underlying problem in 1522, and the software implications. Companion to /learn/time-zones-explained and /learn/the-1884-international-meridian-conference.

What the IDL is

The IDL is a conventional line, approximately following the 180° meridian, where the calendar date changes by one day:

• East of the IDL (in the central Pacific sense): one day earlier than west of the IDL.
• West of the IDL: one day later than east of the IDL.

So when it's Sunday afternoon east of the IDL (say, in Honolulu, UTC-10), it's already Monday afternoon west of the IDL (say, in Auckland, UTC+12). Both are at the same UTC instant; they just label the calendar date differently.

The line is not codified in any international treaty. It emerged from two sources:

1. The 1884 International Meridian Conference (see /learn/the-1884-international-meridian-conference) resolved that longitude would be reckoned 0° to ±180° from Greenwich. This implicitly made the 180° meridian a candidate for the date-change boundary.
2. Sovereign nations along the 180° meridian chose independently which side of the IDL their territory would be on. Most chose to keep their entire territory on one consistent date.

The result: the IDL is a de facto consensus of sovereign decisions, not a treaty obligation.

The zigzag

The IDL is far from straight. Major bends:

The Aleutian Islands

The Aleutian chain (US Alaska) extends west past the 180° meridian, with islands like Attu Island at roughly 173° E (in geographic terms, on the “Asian” side). But the IDL bends west of the entire Aleutian chain so that all of Alaska is on the US-side date. This puts Attu (geographically near Kamchatka) on Tuesday local time when Kamchatka is on Wednesday.

Kiribati (1995)

The Republic of Kiribati spans approximately 4,500 km of the central Pacific, including the Gilbert Islands (near 173° E), the Phoenix Islands (near 172° W), and the Line Islands (near 157° W). Until 1995, the IDL ran through Kiribati: the Gilbert Islands were on the western (Asian) side; the Phoenix and Line Islands were on the eastern (American) side. Kiribati therefore spanned two calendar dates at any instant — inconvenient for a single sovereign government.

On January 1, 1995, Kiribati moved the IDL eastward of all its territory. The Phoenix Islands jumped from UTC-11 to UTC+13. The Line Islands jumped from UTC-10 to UTC+14, the most extreme positive offset on Earth.

The change unified Kiribati under a single date. The Line Islands' UTC+14 offset is now the canonical location of the latest time zone in the world — when clocks tick midnight UTC, it's already 2 PM local time in the Line Islands.

Samoa (2011)

Samoa was on the western (Asian) side of the IDL until 1892, when the U.S. government (then dominant in the Pacific) persuaded Samoa to move to the eastern (American) side, putting Samoa on the same date as the US for trade purposes.

By the early 21st century, Samoa's major trading partners had shifted to Australia and New Zealand. Calendar misalignment meant Samoan businesses had only a few hours of overlap each day with Australian and NZ counterparts.

On December 30, 2011, Samoa (along with Tokelau) skipped directly from December 29 to December 31. December 30, 2011 did not exist in Samoa. The change moved Samoa from UTC-11 to UTC+13 (and to UTC+14 with DST). Business overlap with Australia/NZ went from a few hours to nearly the entire workday.

The change was a return to Samoa's pre-1892 orientation.

Other notable positions

• Hawaii (US): UTC-10, on the US-side of the IDL.
• American Samoa (US territory): stayed on UTC-11 even when Samoa moved to UTC+13 in 2011. American Samoa and (independent) Samoa are now ~25 km apart but on calendar dates one day apart.
• Baker Island and Howland Island (uninhabited US Pacific territories): UTC-12 — the earliest time zone (most negative offset) on Earth.
• Tonga: UTC+13 (Tonga moved to UTC+13 in 1968, ahead of Samoa).
• Tuvalu, Wallis and Futuna: UTC+12.
• Fiji: UTC+12 (with DST UTC+13).
• New Zealand: UTC+12 (with DST UTC+13).
• Chatham Islands (New Zealand): UTC+12:45 (with DST UTC+13:45).
• Kiritimati (Christmas Island, Kiribati): UTC+14 — earliest sunrise on Earth.

The 26-hour spread

The widest spread of UTC offsets currently in use is between UTC-12 (uninhabited Baker Island) and UTC+14 (Kiribati's Line Islands), a difference of 26 hours.

For most of the year, this means:

• When it is 12:00 noon UTC on Wednesday, it is 00:00 midnight Wednesday in Baker Island and 02:00 AM Thursday in the Line Islands.
• A New Year's celebration in Kiritimati happens 26 hours before the same New Year in Baker Island. (Kiritimati was the first inhabited place to enter the new millennium on January 1, 2000.)

The 26-hour spread is a direct consequence of the IDL bend around Kiribati: had the line stayed on the 180° meridian, the spread would be 24 hours (UTC-12 to UTC+12). The Kiribati bend created the extra 2 hours.

Crossing the IDL

Travel rules when crossing the IDL:

• Eastbound (e.g., Tokyo → Honolulu): set the calendar back one day. A passenger departing Tokyo on Monday 17:00 local time, arriving Honolulu after an 8-hour flight, arrives at Monday 07:00 local time — earlier on the same calendar day.
• Westbound (e.g., Los Angeles → Sydney): advance the calendar by one day. A passenger departing LAX on Wednesday 22:00 local time, arriving Sydney after a 15-hour flight, arrives at Friday 06:30 local time — Thursday was experienced briefly in flight before the date rolled over.

The clock-time math is straightforward (add/subtract the UTC offset difference); the calendar math is what trips people up. Airlines, hotels, and itinerary software handle this automatically — but anyone hand-computing arrival times across the IDL needs to account for it.

The Magellan day-loss incident (1522)

The IDL's underlying logic was first observed, without being named, by Ferdinand Magellan's circumnavigation expedition.

Magellan's fleet sailed westward from Spain in 1519. Magellan was killed in the Philippines in 1521; the surviving ship, Victoria, under Juan Sebastián Elcano, continued westward, crossing the Indian Ocean, rounding southern Africa, and returning to Spain in September 1522.

When Victoria arrived at the Cape Verde Islands (off the coast of West Africa, then Portuguese), the ship's logs recorded the date as Wednesday, July 9, 1522. The local Cape Verdeans reported the date as Thursday, July 10. The crew had lost a day.

The cause was unrecognized at the time. By sailing continuously westward, the ship had “outrun” the Earth's rotation by one day — observing one fewer sunrise than people who stayed in place. The crew had crossed the (not-yet-conceived) date line.

The incident was reported by Antonio Pigafetta, the expedition's chronicler, and triggered widespread discussion in 16th-century European scholarly circles. The Catholic Church was particularly interested: how could Christian sailors have observed the wrong calendar dates for their feast days? The incident is often cited as the historical precedent for the eventual establishment of the IDL in the 19th century.

Software implications

The IDL creates subtle bugs for date-and-time-aware software:

Date arithmetic across the IDL

A “next day” computation in local time can cross the IDL with surprising results. A meeting at “tomorrow at 10:00 AM Pacific/Apia time” might fall on a date the user didn't expect if they don't account for the +25-hour offset (Pacific/Apia is on the western side of the IDL while the user thinks of Samoa as “in the eastern Pacific”).

The fix: always serialize timestamps with explicit time zone (IANA name) and offset, and convert via the IANA tz database (see /learn/iana-time-zone-database) rather than guessing offsets.

Recurring events across the IDL

A weekly meeting scheduled at “Tuesday 10:00 in Auckland” and joined by participants in Los Angeles needs careful handling. The Los Angeles participants are joining on Monday afternoon local time. Software that computes “every Tuesday” in Los Angeles time would put the meeting on a different actual instant.

Historical timestamps near sovereign IDL changes

For the 1995 Kiribati change and the 2011 Samoa change, timestamps just before and just after the change need the right IANA zone-name version. The IANA tz database (see /learn/iana-time-zone-database) records these as historical transitions; software that uses outdated tz data will mis-handle pre-change timestamps.

A pre-2011 Samoan timestamp like “2011-06-15 12:00:00” should be interpreted as UTC-11 (Samoa at that moment); a post-2011 timestamp the same wall clock value is UTC+13. The tz database tracks this correctly via the Pacific/Apia zone-name history.

Time zone library availability

Some legacy systems use simplified time-zone tables that don't include the post-1995 Kiribati zones or the post-2011 Samoa zone. Applications relying on such systems compute wrong dates near the IDL. Modern tz-database-aware libraries (Python zoneinfo, JavaScript Intl, Java ZoneId, .NET TimeZoneInfo) handle these correctly when up-to-date.

The IDL is conventional, not physical

A common misconception: the IDL is a physical line on the Earth that you can “cross.” In reality, it's a convention applied to calendar labels. The underlying time instant is the same on both sides of the line; only the date label differs.

There's no physical marker at the IDL. It runs mostly through open ocean and across uninhabited islands. The few populated places straddling or near the IDL have boats, planes, and radio that work identically on both sides — only paper calendars differ.

UTC and TAI have no date discontinuity at the IDL. A UTC timestamp like “2026-05-24T17:30:00Z” is the same instant everywhere on Earth. The IDL is purely a civil-time convention.

Common misconceptions

“The IDL is an international treaty.” It isn't. It emerged from the 1884 conference's ±180° convention combined with sovereign decisions by Pacific island nations. There is no IDL treaty body; each nation independently chooses which side to be on and can change at will (as Kiribati did in 1995 and Samoa did in 2011).

“The IDL follows the 180° meridian exactly.” It approximately does, but zigzags significantly around the Aleutian Islands (west of the chain), Kiribati (east of all territory), Samoa (west of Samoa), Tonga (east of Tonga), and others. The zigzag spans up to ~3,000 km in the Pacific.

“Crossing the IDL adds or removes a day from your life.” It doesn't — the underlying time instant is identical on both sides. Only the calendar label changes. A passenger who flies Honolulu → Tokyo experiences an 8-hour flight; the “lost” day is a calendar bookkeeping artifact.

“UTC+14 is the highest possible time zone.” UTC+14 is the highest currently in use (Kiribati Line Islands). No country has chosen a higher offset, but nothing technically prevents one. A hypothetical “UTC+15” zone would shift even further east, requiring a corresponding adjustment in the IDL or in someone else's zone.

“The IDL changes the date at midnight UTC.” The IDL has no special relationship with UTC time. The date labels on either side of the IDL change at the local midnight in their respective time zones — midnight in Kiribati happens many hours apart from midnight in Hawaii, both at different UTC instants.

“The IDL was established in 1884.” The 1884 conference established the ±180° longitude convention. The IDL as such was not formally codified in that meeting; it emerged afterward from sovereign decisions and gradual cartographic convention. The first detailed IDL map proposal is sometimes attributed to Sandford Fleming's 1879 Time-Reckoning paper.

“Magellan's crew planned for the date loss.” They didn't — the day discrepancy was discovered upon arrival in Cape Verde in July 1522 and caused widespread confusion in the European scholarly community. The conceptual explanation emerged in the following decades; the IDL convention followed centuries later.

“You can stand with one foot in each date.” At a few locations near the IDL (notably the Diomede Islands in the Bering Strait — Big Diomede is Russian, Little Diomede is U.S., and they're 3.7 km apart with the IDL between them, so you can see the “next day” from one to the other), the visualization is more vivid. But the “line” itself is a convention, not a physical feature, and both feet are at the same UTC instant.