[Provider Bug] Geographic Location Misconfiguration: provider.ahn2-na.akash.pub

[Sandeep-Narahari]

Provider URL: provider.ahn2-na.akash.pub

Reported Region: North America / Missouri, US

Actual Physical Location: Zagreb, Croatia

1. Problem Description
   The provider attributes for provider.ahn2-na.akash.pub indicate a physical location in the United States (Missouri/North America). However, network diagnostics confirm the hardware is located in Zagreb, Croatia.

This metadata discrepancy forces latency-sensitive applications (such as VPN meshes or distributed databases) to route traffic incorrectly, leading to significant performance degradation.

2. Technical Evidence
   A. IP Geolocation Proof
   Executing curl ipinfo.io from within a container on this provider reveals the following location data:

   {
   "ip": "86.33.54.63",
   "city": "Zagreb",
   "region": "Zagreb",
   "country": "HR",
   "loc": "45.8144,15.9780",
   "org": "AS205714 Telemach Hrvatska d.o.o.",
   "timezone": "Europe/Zagreb"
   }

   B. Tailscale Network Diagnostics
   tailscale netcheck logs show the nearest relay is in Germany, with a latency that is physically impossible for a server located in the US Midwest:

   Nearest DERP: Frankfurt (fra)

   Latency to Frankfurt: 18.9ms

   Latency to Dallas (dfw): High/Timeout (Calculated at ~135ms from other nodes)

3. Impact on Users
   Network Latency: Expected latency to other US-Central nodes was <30ms; actual observed latency is ~158ms due to trans-atlantic data travel.

Routing Inefficiency: Automated networking stacks (like Tailscale) are forced to use European relays, hair-pinning traffic for US-based users through Frankfurt.

Deployment Integrity: Developers relying on Akash's regional attributes are unable to guarantee the location-based compliance or performance of their workloads.

4. Expected Behavior
   The provider should update its Akash attributes to accurately reflect its location in Europe/Croatia so that the marketplace can correctly assign workloads based on proximity.

5. Steps to Reproduce
   Deploy a container to provider.ahn2-na.akash.pub.

Run curl ipinfo.io.

Observe the country: "HR" and city: "Zagreb" output.