GrapheneOS (@[email protected])
grapheneos.social
This provides an overview of worldwide latency for our ns1 cluster via the Rage4 anycast service we currently use for IPv4+IPv6 with ns1: https://ping6.ping.pe/2a05:b0c4:1::8 Here's ns1 via our own IPv6 /48: https://ping6.ping.pe/2602:f4d9::1 Here's ns2 via our own IPv6 /48: https://ping6.ping.pe/2602:f4d9:1::1

We received an ASN and IPv6 space for GrapheneOS from ARIN: AS40806 and 2602:f4d9::/40.

We’ve deployed 2 anycast IPv6 networks for our authoritative DNS servers to replace our existing setup: 2602:f4d9::/48 for ns1 and 2602:f4d9:1::/48 for ns2. BGP/RPKI setup is propagating.

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.

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

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

Here’s ns1 via our own IPv6 /48:

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

Here’s ns2 via our own IPv6 /48:

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