User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
trip.com · Travel
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1021 ms · 5 min ago.
No status feed
Trip.com does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 18:45 | 0 | 0.0 | 1851 ms | 0 |
| 19:00 | 0 | 0.0 | 1921 ms | 0 |
| 19:15 | 0 | 0.0 | 1823 ms | 0 |
| 19:30 | 0 | 0.0 | 2876 ms | 0 |
| 19:45 | 0 | 0.0 | 1777 ms | 0 |
| 20:00 | 0 | 0.0 | 1365 ms | 0 |
| 20:15 | 0 | 0.0 | 1129 ms | 0 |
| 20:30 | 0 | 0.0 | 2121 ms | 0 |
| 20:45 | 0 | 0.0 | 1847 ms | 0 |
| 21:00 | 0 | 0.0 | 1686 ms | 0 |
| 21:15 | 0 | 0.0 | 1288 ms | 0 |
| 21:30 | 0 | 0.0 | 1990 ms | 0 |
| 21:45 | 0 | 0.0 | 1094 ms | 0 |
| 22:00 | 0 | 0.0 | 2117 ms | 0 |
| 22:15 | 0 | 0.0 | 2367 ms | 0 |
| 22:30 | 0 | 0.0 | 1021 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Trip.com yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Trip.com goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Trip.com alerts to Slack, Discord or a webhook — free.
Trip.com, at trip.com, is one of the Travel services we monitor. Live checks and user reports.
Trip.com has no official status feed we can read, so this page relies on our own checks and user reports.
Typical issues with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 1803 ms average, 1021–3040 ms range across 26 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Trip.com incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
1803 ms on average over the last 24 hours (1021–3040 ms).
Not one we can read. This page uses independent checks of trip.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report Trip.com here at once, the problem is on Trip.com's side.