1. Home
  2. Services
  3. GettingOut
GettingOut viapath.com Live · Operational

Is GettingOut down right now? Live status and outage tracker

No, GettingOut is up.

No widespread outage detected. 136 user reports in the last hour is within the normal range.

Reports, last hour
136
Usual at this hour
Almost none
Vs the hour before
−31%

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 89 normal · 0 elevated · 7 outage

Not working for you?

Last spike · · Data refreshes every 5 minutes

01 · User reports
136 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

02 · Our check, Frankfurt
Answered in 197 ms

Our server loaded www.viapath.com 1 h ago. Behind Cloudflare.

03 · 12 cities, check-host.net
12 of 12 got an answer

Fastest from Frankfurt (35 ms), slowest from Singapore (372 ms). 1 h ago.

Last 24 hours

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.

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.
  • 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
Reports, last hour
136
31% on the hour before
Uptime, 24 h
92.71%
1 h 45 min of outage
Last outage
15 min ago
Lasted 1 h 45 min
Busiest 15 minutes
69
69 reports, 1 h ago
GettingOut status card: No, GettingOut is up. User reports over the last 24 hours.
Share this statusThe picture people see when this page is shared: the answer and the last 24 hours of reports.

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 ago
    Lasted 1 h 45 min
    69peak reports
This month

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.

  1. App68%
  2. Messaging16%
  3. Login15%
  4. Voice calls1%

Share of 74 recent reports that said what was wrong.

World map

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
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

GettingOut problem spikes, last 30 days

Since 4 November, GettingOut had 1 outage spike.

  • Outage
    Thu 5 Nov, 00:57–02:42
    Lasted 1 h 45 min
    74peak 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

Troubleshooting

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.

  1. Reload and restart

    Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.

  2. 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.

  3. Update the app

    Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.

Same time

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.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Servers and network

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).

LocationResultTimeAddress reached
FrankfurtGermanyUp · HTTP 30135 ms141.193.213.10
ViennaAustriaUp · HTTP 30153 ms141.193.213.10
MilanItalyUp · HTTP 30158 ms141.193.213.10
ParisFranceUp · HTTP 301102 ms141.193.213.10
AmsterdamNetherlandsUp · HTTP 301129 ms141.193.213.10
MadridSpainUp · HTTP 301118 ms141.193.213.10
WarsawPolandUp · HTTP 30199 ms141.193.213.10
DallasUSAUp · HTTP 30187 ms141.193.213.10
Los AngelesUSAUp · HTTP 30192 ms141.193.213.10
São PauloBrazilUp · HTTP 301228 ms141.193.213.10
SingaporeSingaporeUp · HTTP 301372 ms141.193.213.10
TokyoJapanUp · HTTP 301285 ms141.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.

Official channels

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.

For your site

Put the GettingOut status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

GettingOut status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/gettingout/"><img src="https://isitdownrightnow.app/badge/gettingout.svg" alt="GettingOut status" height="20"></a>
Markdown, for README files
[![GettingOut status](https://isitdownrightnow.app/badge/gettingout.svg)](https://isitdownrightnow.app/services/gettingout/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

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.

Elsewhere

Check other services