Gap between two time intervals

Give each interval a start and end with a UTC designator or numeric offset, and the result is normalized to UTC before comparison. The calculator returns zero when the ranges overlap or meet at a boundary, so it works cleanly for schedules, logs, reservations, and timeline validation. Along with milliseconds and seconds, it provides an ISO 8601 duration and identifies which interval comes first.

Enter complete intervals with explicit offsets

Provide four values: the start and end of the first interval, followed by the start and end of the second. Every value must be a complete ISO 8601 datetime such as <code>2026-07-25T09:00:00Z</code> or <code>2026-07-25T12:00:00+01:00</code>. The explicit zone is essential because a local clock reading alone does not identify one instant. Each start must be no later than its matching end, but the first interval does not have to occur first chronologically. Fractional seconds are supported with one, two, or three digits. Calendar-only dates, zone names, leap seconds, and omitted offsets are rejected instead of being guessed. This strict input contract makes the result portable across servers and browsers. It also prevents daylight-saving settings on the machine running the calculation from changing the answer. If your source stores named zones, resolve those values to explicit offsets before calling this capability, using the correct offset for each endpoint's actual date.

Understand how the UTC gap is calculated

Each endpoint is converted through calendar arithmetic to a UTC millisecond position. The calculator then checks both possible chronological arrangements. When the first interval ends before the second begins, the gap is the second start minus the first end. When the second interval ends before the first begins, the calculation is reversed. In every other case the ranges overlap or touch, and the gap is exactly zero. Touching includes equality at one boundary: an interval ending at 10:00 and another beginning at 10:00 has no elapsed time between them. Offsets are normalized before these comparisons, so 12:00 at +01:00 is treated as the same instant as 11:00Z. The response includes the gap in milliseconds, the same quantity in seconds, a machine-friendly ISO 8601 duration, and an order label. The method uses no current clock, locale, network service, or runtime date parser, making repeated calls deterministic.

Use the result safely in scheduling workflows

The zero-or-positive result is useful when a workflow cares about idle time rather than total span. A booking system can test the cleanup window between reservations; an observability pipeline can measure silence between incidents; and an import validator can detect whether reported operating periods conflict. Check the order label when downstream logic needs to know which interval came first. Treat <code>overlap_or_touch</code> as a deliberate combined state: the numerical gap is zero in both situations, because neither leaves elapsed time between the ranges. If you need overlap length, calendar-aware business hours, or a distinction between touching and intersecting interiors, use a dedicated calculation rather than deriving it from this gap alone. The browser runner executes the same pure solver as the API, which makes it suitable for manual verification before automation. API requests use the published base price of $0.002. Preserve the returned millisecond value when exact subsecond comparisons matter, and use the ISO duration for interchange or display formatting.