Skip to main content

AS8423

NETCORR-AS

NetcoRR

Registry

Authoritative registration data

AS number
8423
Name
NETCORR-AS
Organisation
NetcoRR
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

5

Total announced

14

Announced prefixes

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

Prefixes announced by AS8423
78.31.128.0/21 IPv4 /21 not checked
195.225.84.0/22 IPv4 /22 not checked
91.200.96.0/22 IPv4 /22 not checked
91.207.124.0/23 IPv4 /23 not checked
193.200.141.0/24 IPv4 /24 not checked
78.31.129.0/24 IPv4 /24 not checked
91.207.124.0/24 IPv4 /24 not checked
91.207.125.0/24 IPv4 /24 not checked
91.213.16.0/24 IPv4 /24 not checked
2a0d:ca40::/29 IPv6 /29 not checked
2001:67c:44::/48 IPv6 /48 not checked
2a0d:ca47:3733::/48 IPv6 /48 not checked
2a0d:ca47:862::/48 IPv6 /48 not checked
2a0d:ca47:876::/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 AS8423
Address families
RoNIX 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 AS8423 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS8423 in AS paths

Observed upstreams
Families
AS39737 Prime-Telecom-AS 118 1,786
v4 v6
AS174 COGENT-174 120 1,413
v4 v6
AS2914 NTT-DATA-2914 69 983
v4 v6
AS6939 HURRICANE 77 640
v4 v6
AS8708 DIGI-RO 2 23
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS8423 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS56430 CHROOT 1 14
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.