Skip to main content

AS39871

NETNOD-GBG

Netnod Equipment located at IX in Gothenburg

Registry

Authoritative registration data

AS number
39871
Name
NETNOD-GBG
Organisation
Netnod Equipment located at IX in Gothenburg
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS39871
192.36.133.0/24 IPv4 /24 not checked
2001:67c:254c::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS39871
Address families
Netnod Gothenburg -- MTU1500: MTU1500 100,000 Mbps IPv4 · IPv6
Netnod Gothenburg -- MTU4470: MTU4470 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS39871 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS39871 in AS paths

Observed upstreams
Families
AS1257 SWIPNET 512 885
v4 v6
AS1653 SUNET 215 465
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS39871 in AS paths

Observed downstreams
Families
AS57021 NTP-SE 367 680
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS3399 OBE-NET 2 5
v4 v6
AS39351 ESAB-AS 2 4
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.