GoFree
Network and observability

Locations without exposing infrastructure

We publish the service region and aggregated path quality—not origin IPs, hostnames, internal node codes, or exact capacity. That separation is part of GoFree’s security model.

new-york-us

New York, United States

Awaiting activation

A practical route for North American services and international connectivity.

24-hour uptime
Available after launch
Median latency
Available after launch
24-hour packet loss
Available after launch
Last checked
Available after launch
tokyo-jp

Tokyo, Japan

Awaiting activation

An East Asia option for regional and Japan-focused services.

24-hour uptime
Available after launch
Median latency
Available after launch
24-hour packet loss
Available after launch
Last checked
Available after launch
tr

Türkiye

Awaiting activation

A nearby regional route for lower latency across Türkiye and surrounding countries.

24-hour uptime
Available after launch
Median latency
Available after launch
24-hour packet loss
Available after launch
Last checked
Available after launch
de

Germany

Awaiting activation

A general European route with broad client and protocol compatibility.

24-hour uptime
Available after launch
Median latency
Available after launch
24-hour packet loss
Available after launch
Last checked
Available after launch
ch

Switzerland

Awaiting activation

A complementary European route for network diversity and resilience.

24-hour uptime
Available after launch
Median latency
Available after launch
24-hour packet loss
Available after launch
Last checked
Available after launch

Automatically refreshes every 60 seconds

01

What stays private?

Origin addresses, the Hiddify administration surface, node identifiers, subscription secrets, and infrastructure-fingerprinting details never appear on this page or in the public API.

02

When servers go live

A monitoring agent on each node submits health results to the internal API. The site publishes only a delayed aggregate and refreshes it every 60 seconds.