What a gap in AirTag location history means
A gap means nobody with an Apple device came near your tag during that stretch. It is an absence of sightings, not an absence of movement, and it says nothing about where the item was in between. We leave gaps visible rather than joining the two ends with a line, because an invented line is the fastest way to weaken a real record.
What is a gap in an AirTag history?
It is a stretch of time with no reports in it. Nothing more. A location only comes into existence when a passing Apple device hears your tag and files an encrypted report, so a quiet period on the map is a quiet period in the world around the tag.
The two ends of a gap are the load-bearing parts. The last point before it and the first point after it are both real, timestamped observations. The space between them is honest emptiness.
Gaps are the normal condition of AirTag tracking rather than an exception to it. A record with no gaps at all usually means the item spent the whole period somewhere busy, not that the tracking was better.
What does a gap not mean?
- Not that the item stopped moving. A truck driving overnight through empty country produces almost nothing.
- Not that the tag failed. A healthy tag broadcasting into an empty car park generates zero points and is working perfectly.
- Not that the item stayed where the last point was. That point is where it was last heard, not where it remained.
- Not that anyone hid anything. Depots close, containers seal, ships sail.
- Not that the tracking service missed something. There was nothing filed to collect.
The last one is worth stressing because it is the assumption people arrive with. A gap is not a dropped report. Reports sit encrypted until they are collected, and a poll every 5 minutes does not lose them. It finds nothing there.
What causes gaps, and how long do they usually run?
Most gaps have an obvious physical explanation, and matching one to the shape of the gap is usually enough to know what happened. These are ranges people commonly see rather than guaranteed figures. Nothing about the network promises a duration.
| Cause | Typical length | What it looks like in the record |
|---|---|---|
| Closed depot, yard, or office overnight | Hours, often the length of the closure | Last point in the evening, next one when staff arrive |
| Sealed steel container or metal trailer | Hours to days | Points stop at loading and resume at unloading |
| Ocean crossing | Days to weeks | A point near the port, then nothing until landfall |
| Underground: basement, tunnel, car park | Minutes to hours | A gap that ends where the route surfaces |
| Rural or sparsely populated route | An hour to several hours | Sparse points strung along a road, not a continuous line |
| Failing or flat battery | Permanent, until the cell is replaced | Reports thin out over days, then stop and never resume |
| Tag separated from the item | No gap at all | Points keep arriving, from a place the item is not |
Why don't we draw a line across the gap?
Because we would be making it up. A straight line between two points nine hours apart asserts a route nobody observed, and the moment it appears in an evidence report it is the first thing an opposing party can attack.
Interpolation also destroys the one thing a gap is genuinely good for. An unexplained nine-hour silence between a warehouse and a port is itself a fact worth putting in front of somebody. Smoothed into a line, it disappears into a plausible-looking journey.
So a quiet stretch is shown as a quiet stretch, with the timestamps at either end intact. That is our limitation stated plainly: we can show you every sighting that happened and nothing about the time in between.
How do you describe a gap to a claims desk?
Claim the two ends and refuse to claim the middle. An adjuster who catches you overstating one part of the record starts doubting all of it, and the ends are usually where the argument actually is.
- State the last observation with its timestamp: the tag was heard at this location at this time.
- State the first observation after the gap the same way.
- Say plainly that no sightings were recorded in between, and why that is expected: a closed depot, a sealed container, an ocean leg.
- Draw only the conclusion the two ends support: the item was not at the place the other party says it was, at the times either end covers.
- Attach the exported record rather than a screenshot, so the timestamps and the gap are both visible.
That framing is stronger than a guess, not weaker. "No sightings were recorded overnight, which is normal for a closed yard" is a sentence an adjuster has no reason to fight. "It was on the M6 at 3am" invites the question of how you know.
Can you reduce gaps before they happen?
Somewhat, and only in advance. Once a stretch has passed unheard there is nothing to recover: the reports were never filed, so no tool and no amount of reconnecting can reconstruct them.
- Place the tag near the outer wall of a box or crate, not buried in the middle under dense goods.
- Keep it out of direct contact with large metal surfaces where you can.
- Use two tags in different parts of a large shipment, so the network has two chances to hear something.
- Fit a fresh battery before a long leg rather than during one.
- Connect before the item ships. History starts when you connect, and nothing reconstructs the days before that.
Beyond that, the route decides. A shipment that passes through cities leaves a rich record; the same box through empty country leaves a sparse one, and no configuration on either side changes that.
Frequently asked questions
Why are there gaps in my AirTag location history?
Because no Apple device came near the tag during that stretch. AirTags have no GPS and cannot report themselves; a point exists only when a passing iPhone hears the tag and files an encrypted report. Closed buildings, sealed containers, rural roads, and ocean legs all produce long stretches with nothing filed.
Does a gap mean my AirTag stopped working?
Usually not. A healthy tag in an empty place produces no points at all, which looks identical to a failure. Suspect the hardware only if reports thinned out over several days first, or if the silence began somewhere busy. Both point toward a failing battery rather than coverage.
Can I recover the locations missing from a gap?
No, and no tool can. Those reports were never created: nobody heard the tag, so nothing was filed on Apple's servers to collect later. A history contains exactly the sightings that happened while you were recording, and the missing stretch is genuinely absent rather than hidden.
Why doesn't the map draw a line through the gap?
Because that line would be invented. Joining two points hours apart asserts a route nobody observed, and a single made-up segment gives an insurer or a carrier a reason to doubt the real points around it. We show the sightings we have and leave the quiet stretches visible.
How do I explain a gap in an insurance claim?
State both ends with their timestamps, say clearly that no sightings were recorded in between, and give the ordinary reason: a closed depot, a sealed container, an ocean leg. Then draw only the conclusion the two ends support. Conceding the gap makes the observations either side harder to dispute.
How long can a normal gap last?
It depends entirely on where the item is. Overnight closures produce gaps of a few hours, sealed containers hours to days, and ocean crossings can run for weeks with almost nothing. None of those durations is guaranteed, because nothing about the network promises a report will ever arrive.
Do gaps mean AirTag history is unreliable evidence?
No, provided it is presented as what it is. Each point is a timestamped observation that the tag was near a device at that moment, and gaps are the expected condition of a crowdsourced network. A record that admits its quiet stretches is more credible than a smooth line that cannot be supported.
Start keeping the route
AirTag History polls your AirTags every 5 minutes and keeps the timeline Find My overwrites. Free for 7 days, and your history starts the moment you connect, not before, so connect ahead of the move.