We started checking Navan on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Navan reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Navan's own status page declared. Below it, any public chatter we saw about Navan and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Navan's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Navan in the last 24 hours, which is not evidence that nothing is wrong.
Navan's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Navan's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Navan next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
150
US-West
100.00%
119
Europe
100.00%
108
Asia-Pacific
100.00%
65
Their declared record
Navan's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Inventory provider degradationMinor incident
Oct 23, 2026, 3:51 PM UTC to Oct 23, 2026, 7:36 PM UTC (3h 45m)resolved
their latest update (Oct 23, 2026, 7:36 PM UTC): **The inventory provider issue has been fully resolved.** All flight and hotel search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Hilton contract errorsAll systems operational
Oct 20, 2026, 6:55 PM UTC to Oct 20, 2026, 9:01 PM UTC (2h 7m)resolved
their latest update (Oct 20, 2026, 9:01 PM UTC): **The hotel inventory issue has been fully resolved.** All hotel search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Navan customer support degradedAll systems operational
Oct 20, 2026, 4:36 AM UTC to Oct 20, 2026, 6:40 AM UTC (2h 4m)resolved
their latest update (Oct 20, 2026, 6:40 AM UTC): The issue has been fully resolved
Hotels inventory degradedAll systems operational
Oct 14, 2026, 7:05 PM UTC to Oct 15, 2026, 6:19 PM UTC (23h 14m)resolved
their latest update (Oct 15, 2026, 6:19 PM UTC): **The hotel inventory issue has been fully resolved.** All hotel search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Travel logs unavailableMinor incident
Oct 5, 2026, 6:27 PM UTC to Oct 5, 2026, 8:32 PM UTC (2h 5m)resolved
their latest update (Oct 5, 2026, 8:32 PM UTC): **The admin functionality issue has been fully resolved.** All admin functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Hotels Inventory DegradedAll systems operational
Oct 2, 2026, 9:08 PM UTC to Oct 3, 2026, 12:03 AM UTC (2h 55m)resolved
their latest update (Oct 3, 2026, 12:03 AM UTC): **The hotel inventory issue has been fully resolved.** All hotel search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
MakeMyTrip inventory outageAll systems operational
Sep 30, 2026, 2:45 PM UTC to Sep 30, 2026, 6:05 PM UTC (3h 19m)resolved
their latest update (Sep 30, 2026, 6:05 PM UTC): **The hotel inventory issue has been fully resolved.** All hotel search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Outage to EU CarrierAll systems operational
Sep 21, 2026, 11:58 AM UTC to Sep 21, 2026, 12:53 PM UTC (54 min)resolved
their latest update (Sep 21, 2026, 12:53 PM UTC): **The train inventory issue has been fully resolved.** All train search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Train bookings in the USMinor incident
Sep 17, 2026, 1:54 PM UTC to Sep 17, 2026, 5:00 PM UTC (3h 6m)resolved
their latest update (Sep 17, 2026, 5:00 PM UTC): **The train inventory issue has been fully resolved.** All train search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Hotels inventory degradedMinor incident
Aug 18, 2026, 7:08 PM UTC to Aug 18, 2026, 9:34 PM UTC (2h 26m)resolved
their latest update (Aug 18, 2026, 9:34 PM UTC): **The hotel inventory issue has been fully resolved.** All hotel search and booking functionality has been restored. Thank you for your patience during this incident. If you continue to experience any issues, please contact our support team.
Showing the 10 most recent of 25 incidents Navan has declared in the history we hold.
These entries are Navan's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Navan's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.