We recently asked for additional sponsored 10Gbps dedicated servers in Europe. We received over a dozen offers and are still looking into and following those up. So far, we've received a 10Gbps update server from Zare in London and a 20Gbps one in Amsterdam from Cherry Servers.

We now have a total of 5 sponsored update servers:

20Gbps from Cherry Servers in Amsterdam
10Gbps from Zare in London
10Gbps from Xenyth in Toronto
10Gbps from ReliableSite in Miami
10Gbps from ReliableSite in Los Angeles

Cherry Servers also provided a 2nd server for geocoding.

We have a full list of our public-facing servers at https://grapheneos.org/articles/grapheneos-servers including details on the sponsored servers with links to the websites of the sponsors. All the update servers are sponsored since paying for the amount of traffic we'll be using would be very expensive.
GrapheneOS servers

Documentation on GrapheneOS servers.

GrapheneOS

In addition to the primary purpose of updates, we use these servers as a subset of our 11 locations for website/network services.

We moved our mail server to a system container on the Xenyth server where we're using our own AS and IP space via BGP to avoid spam filtering issues.

We're also going to be using a subset of these as additional ns2 anycast DNS locations. We already use the Xenyth server as 1 of our 9 ns2 locations and plan to use the Zare server for it soon too. This depends on BGP support including BGP communities for traffic engineering.
Cherry Servers also provided a 2nd sponsor server in Amsterdam for us to use as our first geocoding server via Nominatim. Nominatim is very demanding and calls for at least around 128GB of memory and 4TB fast NVMe storage. The initial data import for Nominatim took almost 2 days.
Geocoding means converting the description of a location such as an address or the name of a place to coordinates. It supports many different kinds of searches such as finding a pharmacy or park within a certain zone. There's also reverse search to convert coordinates to names.
We provide geocoding as an opt-in service with a choice between our proxy to the OpenStreetMaps Nominatim server (recommended) or directly using their service. Our proxy will soon be pointed at the server from Cherry Servers and then replaced with a new multi-server GeoDNS setup.
You can try out our new self-hosted geocoding server at https://ams.nominatim.grapheneos.org/ui/search.html. In addition to OpenStreetMaps data, we've imported the primary/secondary Wikipedia importance data, US/UK postcodes, US house data and OSM special phrases. It should be close to the OSM service now.
Nominatim Demo

@GrapheneOS so this is basically like open source google maps websearch? is there a way to integrate it with organicmaps or other gps nav apps?
@chingalamigra Yes, the forward search portion is equivalent to search in Google Maps. The majority of Android apps using geocoding are using the OS geocoding service because Google provides a free implementation on Google Mobile Services devices. Geocoding is normally offered as a very expensive metered service meaning paying for each request. Google's pricing for the regular service starts out around $5 per 1k requests and gradually drops as the volume goes up. Most apps will use what we ship.
@chingalamigra The search bar at https://www.openstreetmap.org/ is based on Nominatim and is the same software and data we're now self-hosting for use in GrapheneOS. In Settings > Location > Location services we added entries for Network location and Geocoder to opt into our implementations of those. Both network location and geocoding are currently provided via a choice of using our proxy or using the service the proxy uses directly but we're going to be self-hosting implementations of both.
OpenStreetMap

OpenStreetMap is a map of the world, created by people like you and free to use under an open license.

OpenStreetMap
@GrapheneOS i see... so when i search in an osm app like organic maps, its already using an equivalent to this?
@chingalamigra Yes, but unlike Organic Maps or CoMaps most apps implement this via the OS service which is a free version of Google's geocoding service on Google Mobile Services devices. On GrapheneOS, that's unavailable until users opt-in to it by choosing between the GrapheneOS proxy to OpenStreetMaps or OpenStreetMaps. Our self-hosted server will replace our proxy entirely since the proxy is pointless if we're self-hosting it and avoids the problematic OSM rate limiting impacting it.