Skip to main content

AS3663

NETNET-NET

NetNet

Registry

Authoritative registration data

AS number
3663
Name
NETNET-NET
Organisation
NetNet
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

48

IPv6 prefixes

1

Total announced

49

Announced prefixes

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

Prefixes announced by AS3663
108.167.192.0/18 IPv4 /18 not checked
142.11.0.0/18 IPv4 /18 not checked
184.95.64.0/18 IPv4 /18 not checked
192.173.192.0/18 IPv4 /18 not checked
198.190.64.0/18 IPv4 /18 not checked
50.116.128.0/18 IPv4 /18 not checked
96.126.0.0/18 IPv4 /18 not checked
108.167.192.0/19 IPv4 /19 not checked
108.167.224.0/19 IPv4 /19 not checked
142.11.0.0/19 IPv4 /19 not checked
142.11.32.0/19 IPv4 /19 not checked
173.254.128.0/19 IPv4 /19 not checked
184.95.64.0/19 IPv4 /19 not checked
184.95.96.0/19 IPv4 /19 not checked
192.173.192.0/19 IPv4 /19 not checked
192.173.224.0/19 IPv4 /19 not checked
206.40.96.0/19 IPv4 /19 not checked
50.116.128.0/19 IPv4 /19 not checked
50.116.160.0/19 IPv4 /19 not checked
63.135.128.0/19 IPv4 /19 not checked
70.40.224.0/19 IPv4 /19 not checked
96.126.0.0/19 IPv4 /19 not checked
96.126.32.0/19 IPv4 /19 not checked
173.254.160.0/20 IPv4 /20 not checked
206.40.96.0/20 IPv4 /20 not checked
70.40.224.0/20 IPv4 /20 not checked
70.40.240.0/20 IPv4 /20 not checked
74.213.208.0/20 IPv4 /20 not checked
173.254.160.0/21 IPv4 /21 not checked
173.254.168.0/21 IPv4 /21 not checked
206.40.112.0/21 IPv4 /21 not checked
206.40.120.0/21 IPv4 /21 not checked
63.135.136.0/21 IPv4 /21 not checked
64.246.240.0/21 IPv4 /21 not checked
64.246.248.0/21 IPv4 /21 not checked
74.213.208.0/21 IPv4 /21 not checked
74.213.216.0/21 IPv4 /21 not checked
199.115.224.0/22 IPv4 /22 not checked
70.40.254.0/23 IPv4 /23 not checked
142.11.1.0/24 IPv4 /24 not checked
142.11.2.0/24 IPv4 /24 not checked
206.40.105.0/24 IPv4 /24 not checked
206.40.109.0/24 IPv4 /24 not checked
206.40.114.0/24 IPv4 /24 not checked
206.40.115.0/24 IPv4 /24 not checked
206.40.125.0/24 IPv4 /24 not checked
63.135.128.0/24 IPv4 /24 not checked
63.135.159.0/24 IPv4 /24 not checked
2607:f430::/32 IPv6 /32 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 AS3663
Address families
Equinix Chicago 100,000 Mbps IPv4 · IPv6
MICE: Shared Peering 100,000 Mbps IPv4 · IPv6
QCIX: Main 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 AS3663 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS3663 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 1,292 10,757
v4 v6
AS6461 ZAYO-6461 561 7,974
v4 v6
AS174 COGENT-174 272 3,544
v4 v6
AS137409 GSLNETWORKS-AS-AP 11 158
v4
AS8220 COLT 3 8
v4

No rows match “”.

Showing – of

Observed downstreams

6 networks seen after AS3663 in AS paths

Observed downstreams
Families
AS397463 WASHINGTON-ISLAND-ELECTRIC-COOP 498 1,480
v4 v6
AS398370 NORTHWOODS-COMMUNICATION-TECHNOLOGIES 277 752
v4
AS7268 ATHENET 172 700
v4
AS394660 NORVADO-NE 232 654
v4
AS395091 PLEXUS 276 377
v4
AS12081 GREENHECK 215 302
v4

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 6 177
v4 v6
AS49544 i3Dnet 5 116
v4 v6
AS394414 AS394414 7 62
v4 v6
AS36236 NETACTUATE 6 59
v4 v6
AS35280 F5 6 56
v4
AS1828 UNITAS 2 3
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.