Skip to main content

AS8683

NOMINET

ORG-NU1-RIPE

Registry

Authoritative registration data

AS number
8683
Name
NOMINET
Organisation
ORG-NU1-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

10

Total announced

19

Announced prefixes

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

Prefixes announced by AS8683
213.248.232.0/21 IPv4 /21 not checked
213.248.240.0/21 IPv4 /21 not checked
149.20.100.0/22 IPv4 /22 not checked
149.20.104.0/22 IPv4 /22 not checked
149.20.108.0/22 IPv4 /22 not checked
149.20.96.0/22 IPv4 /22 not checked
213.248.228.0/23 IPv4 /23 not checked
213.248.252.0/23 IPv4 /23 not checked
213.248.249.0/24 IPv4 /24 not checked
2a01:618:8000::/33 IPv6 /33 not checked
2a01:618:8000::/40 IPv6 /40 not checked
2a01:61c:1000::/40 IPv6 /40 RPKI valid
2a01:61c:1100::/40 IPv6 /40 RPKI valid
2a01:61c:1a00::/40 IPv6 /40 RPKI valid
2a01:61c:2000::/40 IPv6 /40 RPKI valid
2a01:61c:2100::/40 IPv6 /40 RPKI valid
2a01:61c:2a00::/40 IPv6 /40 not checked
2a01:61c:f001::/48 IPv6 /48 not checked
2a01:61c:f002::/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 AS8683
Address families
LINX LON1: Main 2,000 Mbps IPv4 · IPv6
LINX LON2 2,000 Mbps IPv4 · IPv6
LONAP: LON0 10,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 AS8683 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

40 networks seen before AS8683 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS8683 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

20 adjacencies that may be an artefact of collector peering

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.