User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
tripit.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 592 ms · 7 min ago.
No status feed
TripIt does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 18 | 0 | 0.0 | 188 ms | 0 |
| Tue 19 | 0 | 0.0 | 285 ms | 0 |
| Tue 20 | 0 | 0.0 | 168 ms | 0 |
| Tue 21 | 0 | 0.0 | 156 ms | 0 |
| Tue 22 | 0 | 0.0 | 237 ms | 0 |
| Tue 23 | 0 | 0.0 | 226 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 TripIt 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 TripIt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TripIt alerts to Slack, Discord or a webhook — free.
TripIt is listed in our Travel category and checked at tripit.com. Live checks and user reports.
TripIt 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: 256 ms average, 78–820 ms range across 33 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public TripIt incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
256 ms on average over the last 24 hours (78–820 ms).
Not one we can read. This page uses independent checks of tripit.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 TripIt here at once, the problem is on TripIt's side.