User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
citymapper.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 1443 ms · 8 min ago.
No status feed
Citymapper does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:30 | 0 | 0.0 | 1442 ms | 0 |
| 20:45 | 0 | 0.0 | 1175 ms | 0 |
| 21:00 | 0 | 0.0 | 1217 ms | 0 |
| 21:15 | 0 | 0.0 | 1311 ms | 0 |
| 21:30 | 0 | 0.0 | 1585 ms | 0 |
| 21:45 | 0 | 0.0 | 1223 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 Citymapper 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 Citymapper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Citymapper alerts to Slack, Discord or a webhook — free.
We track Citymapper (citymapper.com) as part of the Travel group. Citymapper is a transit navigation app for major cities, owned by Via.
Citymapper has no official status feed we can read, so this page relies on our own checks and user reports.
Common problems people hit with Citymapper: live departures missing, routes not loading, and app errors.
Response time over the last 24 hours: 1302 ms average, 882–1585 ms range across 11 successful checks.
Checks are succeeding and user reports are near the baseline.
1302 ms on average over the last 24 hours (882–1585 ms).
Not one we can read. This page uses independent checks of citymapper.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 Citymapper, watch for live departures missing, routes not loading, and app errors. If many people report Citymapper here at once, the problem is on Citymapper's side.