User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Travel
going.com · Travel
Is Going down?
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → going.com—
Your browser → us—
Our checksReaching it
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Our checks
Reaching it
Last check reached it in 787 ms · 9 min ago.
Official status
No status feed
Going does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 18:45 | 0 | 0.0 | 355 ms | 0 |
| 19:00 | 0 | 0.0 | 406 ms | 0 |
| 19:15 | 0 | 0.0 | 421 ms | 0 |
| 19:30 | 0 | 0.0 | 514 ms | 0 |
| 19:45 | 0 | 0.0 | 594 ms | 0 |
| 20:00 | 0 | 0.0 | 559 ms | 0 |
| 20:15 | 0 | 0.0 | 457 ms | 0 |
| 20:30 | 0 | 0.0 | 625 ms | 0 |
| 20:45 | 0 | 0.0 | 314 ms | 0 |
| 21:00 | 0 | 0.0 | 474 ms | 0 |
| 21:15 | 0 | 0.0 | 751 ms | 0 |
| 21:30 | 0 | 0.0 | 442 ms | 0 |
| 21:45 | 0 | 0.0 | 427 ms | 0 |
| 22:00 | 0 | 0.0 | 574 ms | 0 |
| 22:15 | 0 | 0.0 | 637 ms | 0 |
| 22:30 | 0 | 0.0 | 470 ms | 0 |
| 22:45 | 0 | 0.0 | 546 ms | 0 |
| 23:00 | 0 | 0.0 | 920 ms | 0 |
| 23:15 | 0 | 0.0 | 787 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed a live Going status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Going yet. Outages of 10 minutes or more get their own page here.
Having trouble with Going?
One report per service every 10 minutes from this network. No account.
Follow Going
Get an email when Going goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Going alerts to Slack, Discord or a webhook — free.
About Going
Going, at going.com, is one of the Travel services we monitor. Live checks and user reports.
Going has no official status feed we can read, so this page relies on our own checks and user reports.
Common problems for 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: 531 ms average, 289–920 ms range across 31 successful checks.
Questions
Is Going down right now?
Checks are succeeding and user reports are near the baseline.
When was Going last down?
We have not recorded a public Going incident since monitoring began 1 day ago.
What is Going's uptime?
From our own checks: 100% over 1 day of checks.
How fast does Going respond?
531 ms on average over the last 24 hours (289–920 ms).
Does Going have an official status page?
Not one we can read. This page uses independent checks of going.com and user reports.
Going not working for me but the status is fine. What now?
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 Going here at once, the problem is on Going's side.