We need to choose a host in Singapore with IPv4+IPv6 BGP support to extend ns2 with a location in Asia. Once that's added, it will be good enough for our current needs. The subset of our dedicated/colocated update servers with BGP could be used as extra ns2 locations eventually.

We've deployed our IPv4 /24 and IPv6 /48 for ns2 in production to replace the IPv4-only anycast tunnel system it relied on before. It has somewhat better latency and significantly better reliability now. We're waiting a bit longer for production deployment of our ns1 IPv6 /48.

No, but hopefully not.

It cost us US$50 to register with ARIN as an organization and US$262.50/year paid in advance to become an 3X-Small network. It'll be US$525/year when we get a 2nd IPv4 since we'll get pushed into 2X-Small. 2X-Small covers IPv4 /22, i.e. 4x /24, which we can get via the waitlist.

ARIN gave us an IPv4 /24 based on our NRPM 4.10 request in under 24 hours. It's being announced from our ns2 network:

github.com/GrapheneOS/n...

It will take a long time to propagate since the RPKI IRR/ROA data gets fetched via timed jobs rather than pushed hop-by-hop like BGP.

The initial phone will be similar to a regular Pixel, i.e. not the budget series or the Pro series but rather the regular ones without a suffix. All of the supported phones will use a flagship Snapdragon SoC for the foreseeable future because we want good support time and latest security features.

Those currently don't meet the driver/firmware update and hardware-based security feature requirements for GrapheneOS. There are going to be more devices than Pixels supported within the next 1-2 years due to an ongoing partnership with a major OEM which is going very well so far.

In the future, we plan to use these 2 anycast networks to provide recursive DNS resolvers as an option for our users. For now, it's only for the authoritative DNS used to provide other GrapheneOS services which is what DNS resolver servers query after the root and TLD servers.

This provides an overview of worldwide latency for our ns1 cluster via the Rage4 anycast service we currently use for IPv4+IPv6 with ns1:

ping6.ping.pe/2a05:b0c4:1::8

Here's ns1 via our own IPv6 /48:

ping6.ping.pe/2602:f4d9::1

Here's ns2 via our own IPv6 /48:

ping6.ping.pe/2602:f4d9:1::1

We applied for an IPv4 /24 for ns2 via NRPM 4.10 and can apply for one for ns1 after we obtain that one.

Our ns1 network has New Jersey, Miami, Los Angeles, Seattle, Frankfurt and Singapore.Our ns2 network currently has New York, Las Vegas and Bern. We'll be expanding both.

Forum discussion thread:

discuss.grapheneos.org/d/28005-vana...

We don't have a timeline for Pixel 10 support. When we have information to share, we'll make a post about it.

Android 16 was released in June 2025 and GrapheneOS fully migrated it in June 2025. We already have the Android 16 UI changes.

Android 16 QPR1 is a newer release currently exclusive to the stock Pixel OS which has not been released to the Android Open Source Project so we can't migrate to it yet.

Forum discussion thread:

discuss.grapheneos.org/d/27905-vana...

Yes, at least for the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL. Pixel 10 Pro Fold will take longer due to the lack of an Android 16 QPR1 release for AOSP. Android made a huge mess with delayed 16 QPR1 release, changes to security patches and dropping Pixel support from AOSP which burns our time.

> at least some other degoogled phone

See discuss.grapheneos.org/d/24134-devi... for a representative example of how that usually goes. iPhones provide much better privacy from apps and services than nearly all niche products advertised as private. /e/ even sends sensitive data to OpenAI itself.

Forum discussion thread:

discuss.grapheneos.org/d/27862-vana...