Stavanger · Norway
PeeringDB records one internet exchange in Stavanger, SIX Stavanger, with 10 participants, and one colocation facility, GC-FAB7 Stavanger, holding three networks. That is the whole of the city's recorded network presence. An address that geolocates to Stavanger tells you where its operator registered the block, not where a device is connected.
Internet exchanges in Stavanger
An exchange is a shared switch where networks hand traffic to each other directly. Participant counts come from PeeringDB, where each network maintains its own record.
| Exchange | Participants | Registry carriers peering |
|---|---|---|
SIX Stavanger | 10 | none in the registry |
Exchange records: PeeringDB.
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which shows where capacity in the city sits.
| Facility | Networks present | Address |
|---|---|---|
| GC-FAB7 Stavanger | 3 | Fabrikkveien 7 |
What a Stavanger IP address tells you
SIX Stavanger is the only exchange PeeringDB records here, and its 10 participants are the entire public peering footprint of the city. Colocation adds little on top, one facility, GC-FAB7 Stavanger, with three networks recorded in it. The exchange therefore carries more of the local interconnection than the colocation listing does, and neither side is big. No participant at SIX Stavanger is flagged as a carrier ASN, and the carrier registry holds no Norwegian mobile operator entries to check against.
An address that geolocates to Stavanger may sit on a device far from it. An operator announces a block from a registry record holding a single administrative address, and geolocation databases inherit that address for every prefix under it. Mobile networks widen the distance again, because handsets across a region leave through a few gateways and take a public address registered to the gateway rather than to the cell they are on. A city tag on such an address reflects the operator's own published location and nothing about the handset.
Someone checking a Stavanger address should read the origin ASN and the netname on the specific prefix rather than the city field. The ASN identifies the network announcing the block, and the netname points at the registry record and the organisation holding it. Set that against what PeeringDB puts in Stavanger, 10 exchange participants and three networks in one facility, and it is quick to see whether the announcing network is present in the city.
Questions
Which internet exchanges are in Stavanger?
One. PeeringDB records SIX Stavanger with 10 participants. Alongside it the registry lists a single colocation facility in the city, GC-FAB7 Stavanger, holding three networks, so 10 participants and three facility networks describe the recorded interconnection here.
Do Norwegian mobile carriers peer in Stavanger?
Not according to the records. SIX Stavanger lists no participant flagged as a carrier ASN, and the carrier registry holds no Norwegian mobile operator entries, so nothing here shows a mobile network peering in the city one way or the other.
Does an IP that geolocates to Stavanger mean the device is there?
No. Geolocation databases repeat the location an operator publishes for a registered address block, and a mobile address usually belongs to a gateway serving a wide area. Look at the origin ASN and the netname on the exact prefix before treating the city as fact.
Sources
- PeeringDB - exchanges, participant counts, facilities and network presence, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - operator ASNs used to match peering participants