Is Navan Down?

No — Navan is up

Navan's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 163 ms

Right now

The verdict is the worse of these two. How we decide

Navan's status page

status.navan.com · read 3 minutes ago · checked every 3 minutes

Operational

Navan's components, as its status page reports them
Component	Status
Website	Operational
Travel	Operational
Expense	Operational

Open their status page

FlareWarden checks

app.navan.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 163 ms
Checked: 4 hours ago

By region

Ashburn reachable, 134 ms
Chicago reachable, 133 ms
Johannesburg reachable, 182 ms
London reachable, 99 ms
Los Angeles reachable, 171 ms
Singapore reachable, 192 ms
São Paulo reachable, 232 ms
Tokyo reachable, 164 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	56 ms	1 ms	7 ms	133 ms
Chicago	11 ms	2 ms	7 ms	132 ms
Johannesburg	19 ms	1 ms	13 ms	181 ms
London	45 ms	3 ms	11 ms	98 ms
Los Angeles	96 ms	3 ms	14 ms	169 ms
Singapore	148 ms	2 ms	8 ms	191 ms
São Paulo	146 ms	2 ms	12 ms	231 ms
Tokyo	122 ms	1 ms	7 ms	164 ms

We check that app.navan.com loads, not every feature behind it. Test it yourself

History

Incidents Navan reported

Since Oct 22, 15 days · from status.navan.com

Incidents: 1
Major or critical: 0
Median to resolve: 3h 45m

Inventory provider degradation
minor · Oct 23
lasted 3h 45m

Navan website availability

Measured by FlareWarden · app.navan.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 154ms

Last 30 days

50-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of app.navan.com from multiple regions every 6 hours. Navan's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 50 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Navan does

Navan is a corporate travel and expense platform that puts booking, company cards and expense reporting in one app. Employees book flights and hotels inside company policy, and finance teams use the same system to track spend and reimburse expenses. An outage can strand a traveller mid-trip as easily as it delays month-end close.

What an outage looks like

The web app will not load or sign-in loops back to the login screen. Flight and hotel searches return errors or never finish, so a booking cannot be made or changed. Expense submissions fail, receipts will not attach, and approvals sit untouched. The mobile app may still show upcoming trips while any action that needs the server fails.

What to do about it

Check status.navan.com, which reports Website, Travel and Expense as three separate components, so a broken expense report does not mean booking is down. If you are travelling and need to change a flight urgently, contact the airline or hotel directly rather than waiting, and record the change in Navan once it recovers so the trip record and your expense report still match.

Is it down for everyone, or just you?

If this page says Navan is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Navan outage FAQ

Is Navan down or just the expense side?

Check the individual rows on status.navan.com. Navan reports Website, Travel and Expense as separate components, so expense submission can fail while travel booking works, or the reverse. If only Expense is affected, hold receipts and submit once it recovers. If Travel is affected and you need to book now, ask your travel manager how your company handles bookings made outside Navan.

What should I do if I am travelling during a Navan outage?

Deal with the airline or hotel directly for anything urgent. Your existing tickets and reservations were issued by those suppliers and do not stop being valid because Navan is unreachable. Keep confirmation emails and receipts for anything you change or buy, then update the trip and expenses in Navan afterwards so the company's records are complete.

Will an expense I submitted during an outage be lost?

Do not assume it went through. If submission returned an error, it was probably not saved. Once Navan recovers, open your expense list and confirm the item appears with its receipt attached before resubmitting, because submitting twice creates a duplicate that someone in finance then has to find and reject.

Why does the mobile app show my trip but I cannot change it?

The app can display details it already loaded while any change still needs a live connection to Navan. That makes a partial outage look like a problem with one booking. Check the Travel component on the status page, and try the website from another network before contacting support.

Is Navan down for everyone or just me?

Look at the status page and this page's regional measurements together. If Navan reports all three components operational and our probes reach the app from several regions, the fault is likely local: a corporate VPN, single sign-on with your identity provider, or an expired session. Failures from several regions at once point to Navan itself.

How we measure this

We request Navan's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Navan publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Navan itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Navan goes down

We check Navan every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required