Skip to main content

AS999

CORIX-999

CORIX NETWORKS

Registry

Authoritative registration data

AS number
999
Name
CORIX-999
Organisation
CORIX NETWORKS
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

19

Total announced

27

Announced prefixes

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

Prefixes announced by AS999
38.57.240.0/22 IPv4 /22 not checked
208.89.72.0/24 IPv4 /24 not checked
208.89.73.0/24 IPv4 /24 not checked
208.89.74.0/24 IPv4 /24 not checked
208.89.75.0/24 IPv4 /24 not checked
23.145.72.0/24 IPv4 /24 not checked
38.105.3.0/24 IPv4 /24 not checked
38.57.116.0/24 IPv4 /24 not checked
2607:1640::/32 IPv6 /32 not checked
2607:1640:1036::/48 IPv6 /48 not checked
2607:1640:1037::/48 IPv6 /48 not checked
2607:1640:1040::/48 IPv6 /48 not checked
2607:1640:145::/48 IPv6 /48 not checked
2607:1640:243::/48 IPv6 /48 not checked
2607:1640:50::/48 IPv6 /48 not checked
2607:1640:51::/48 IPv6 /48 not checked
2607:1640:52::/48 IPv6 /48 not checked
2607:1640:54::/48 IPv6 /48 not checked
2607:1640:55::/48 IPv6 /48 not checked
2607:1640:56::/48 IPv6 /48 not checked
2607:1640:57::/48 IPv6 /48 not checked
2607:1640:62::/48 IPv6 /48 not checked
2607:1640:72::/48 IPv6 /48 not checked
2607:1640:73::/48 IPv6 /48 not checked
2607:1640:74::/48 IPv6 /48 not checked
2607:1640:75::/48 IPv6 /48 not checked
2607:1640:999::/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 AS999
Address families
CIX-NoVA 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 AS999 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS999 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 2,197 13,435
v4 v6
AS6453 AS6453 622 3,857
v4 v6
AS174 COGENT-174 455 2,192
v4 v6
AS22356 903 1,843
v4 v6
AS1031 PEER1-1031 230 359
v4 v6
AS28663 ASN28663 235 323
v4 v6
AS52925 6 40
v4
AS14840 ASN14840 2 37
v6
AS29838 AMC 6 28
v4
AS35280 F5 7 23
v4 v6
AS6057 6057 3 23
v4 v6
AS3303 SWISSCOM 8 10
v4
AS7195 7195 2 10
v6
AS137409 GSLNETWORKS-AS-AP 3 4
v4 v6
AS33891 CORE-BACKBONE 2 2
v6
AS9498 BBIL-AP 1 1
v4

No rows match “”.

Showing of

Observed downstreams

30 networks seen after AS999 in AS paths

Observed downstreams
Families
AS272713 1,308 9,345
v4
AS20253 928 2,596
v4
AS262428 30 836
v4
AS262761 ASN262761 185 558
v4
AS262403 200 554
v4
AS28146 125 529
v4
AS26615 16 473
v4
AS52892 28 321
v4
AS4230 ASN4230 112 280
v4
AS263649 20 264
v4
AS267344 82 184
v4
AS10429 37 116
v4
AS269311 70 115
v4
AS263308 ASN263308 12 66
v4
AS264477 14 62
v4
AS28640 ASN28640 11 57
v4
AS61745 8 26
v4
AS267638 15 16
v4
AS52557 9 16
v4
AS270735 5 13
v4
AS7738 4 10
v4
AS268763 8 8
v4
AS14619 AS-THERA-US 7 7
v4
AS268696 7 7
v4
AS3356 LEVEL3 1 5
v4
AS1031 PEER1-1031 4 4
v4
AS8167 1 3
v4
AS22381 2 2
v4
AS52780 ASN52780 2 2
v4
AS61609 2 2
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS263152 167 847
v4 v6
AS49544 i3Dnet 83 742
v4 v6
AS199524 GCORE 3 11
v4 v6
AS24482 SGGS-AS-AP 1 4
v4 v6
AS51185 MAINSTREAMING-AS 1 3
v4 v6
AS52873 ASN52873 1 3
v4 v6
AS22548 1 2
v4 v6
AS28624 ASN28624 1 2
v6
AS28634 ASN28634 1 2
v4
AS36236 NETACTUATE 1 2
v4 v6
AS52320 52320 1 2
v6
AS60503 1 2
v4 v6
AS263237 1 2
v4 v6
AS264479 1 2
v4 v6
AS198150 SIACOM-AS 1 1
v4
AS262427 1 1
v4
AS271253 ASN271253 1 1
v4

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.