{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreializrisi46kj4zeptnxp5dvqjjoygmc5wflzfv5j6ruphl5qbadi",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mnm5xeafrrz2"
  },
  "path": "/t/feature-request-enable-ipv6-support-for-hugging-face-api/176581#post_1",
  "publishedAt": "2026-06-06T07:02:56.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Currently, Hugging Face endpoints do not resolve to IPv6 (no AAAA records). With the global exhaustion of IPv4 addresses, cloud providers like AWS and Google Cloud (GCP) now charge extra for public IPv4 addresses, encouraging developers to deploy workloads in IPv6-only environments (e.g., using `--no-address` on GCP VM or IPv6-only subnets).\n\nRunning inference or downloading models directly from an IPv6-only server currently fails unless we use a paid NAT gateway or third-party DNS64 translation.\n\nPlease consider adding AAAA records to your CDN/load balancers (Cloudflare/AWS CloudFront) to support native IPv6.",
  "title": "Feature Request: Enable IPv6 Support for Hugging Face API"
}