GettingOut outages and problems
User reports, last 24 hours
336 reports in total, counted in 15-minute windows
In the last hour, 136 problem reports came in for GettingOut, and at this time of day there are usually almost none. Over the last 24 hours there were 336 reports. Most recent reports were about app (68%) and messaging (16%). The last spike in reports was 16 min ago and lasted 1 h 45 min. These are user reports from the US, where most people report GettingOut problems.
- NormalClose to the usual level22 h 15 min · 4 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's average1 h 45 min · 332 reports
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 336 user reports came in for GettingOut. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 92.71% uptime for the day.
The most recent spike big enough to count as an outage was 15 minutes ago. The busiest 15-minute window of the day had 69 reports, about 1 hour ago.
-
Outage
Ended 15 min agoLasted 1 h 45 min69peak reports
GettingOut in November 2026
- Problem reports in November (since 4 November)
- 341
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for GettingOut.
Share of 74 recent reports that said what was wrong.
Where GettingOut problem reports come from
The map shows where recent problem reports for GettingOut came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
GettingOut problem spikes, last 30 days
Since 4 November, GettingOut had 1 outage spike.
-
Outage
Thu 5 Nov, 00:57–02:42Lasted 1 h 45 min74peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 4 November 2026. Monthly reports for all services
How to fix GettingOut not working
GettingOut is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach viapath.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not GettingOut.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as GettingOut
Since 4 November, GettingOut's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
GettingOut: Thu 5 Nov, 00:57 to 02:42
- USPS, outage,4 Nov 10:42 to 01:57
- Facebook, outage,4 Nov 13:42 to 02:57
- Deutsche Glasfaser, outage,4 Nov 13:57 to 01:57
- Sam's Club, outage,4 Nov 13:57 to 01:12, 01:42 to 02:27
- Capital One, outage,4 Nov 16:57 to 02:57
- Escape from Tarkov, outage,4 Nov 18:12 to 01:12, 01:42 to 01:57
- Roblox, outage,4 Nov 19:27 to 01:12
- Bell Canada, outage,4 Nov 19:57 to 02:57
102 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
GettingOut IP address, servers and network
- IPv4 addresses
- 141.193.213.10
Show all 2
- 141.193.213.11
- IPv6
- Not offered
- Network
- AS209242 · Cloudflare London, LLC, registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Cloudflare
- HTTPS certificate
- Issued by Let's Encrypt, valid until 1 Feb 2027 (88 days)
- HTTP/3
- Supported
- Our check
- Answered in 197 ms
Checked from our server in Frankfurt, Germany, 1 h ago, for www.viapath.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from viapath.com. Fastest from Frankfurt (35 ms), slowest from Singapore (372 ms). Every location connected to the same address, on Cloudflare London, LLC (AS209242).
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 35 ms | 141.193.213.10 |
| ViennaAustria | Up · HTTP 301 | 53 ms | 141.193.213.10 |
| MilanItaly | Up · HTTP 301 | 58 ms | 141.193.213.10 |
| ParisFrance | Up · HTTP 301 | 102 ms | 141.193.213.10 |
| AmsterdamNetherlands | Up · HTTP 301 | 129 ms | 141.193.213.10 |
| MadridSpain | Up · HTTP 301 | 118 ms | 141.193.213.10 |
| WarsawPoland | Up · HTTP 301 | 99 ms | 141.193.213.10 |
| DallasUSA | Up · HTTP 301 | 87 ms | 141.193.213.10 |
| Los AngelesUSA | Up · HTTP 301 | 92 ms | 141.193.213.10 |
| São PauloBrazil | Up · HTTP 301 | 228 ms | 141.193.213.10 |
| SingaporeSingapore | Up · HTTP 301 | 372 ms | 141.193.213.10 |
| TokyoJapan | Up · HTTP 301 | 285 ms | 141.193.213.10 |
Checked with check-host.net from its servers in these cities 1 h ago, for viapath.com. Time is how long each server took to load the page.
Contact GettingOut support
Tip: GettingOut doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track GettingOut
The status on this page comes from user-submitted problem reports for GettingOut, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for GettingOut, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. GettingOut doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.