Skip to main content

AS14746

NOCTEL

NocTel Communications, Inc.

Registry

Authoritative registration data

AS number
14746
Name
NOCTEL
Organisation
NocTel Communications, Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

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

Prefixes announced by AS14746
192.69.24.0/24 IPv4 /24 not checked
192.69.25.0/24 IPv4 /24 not checked
192.69.26.0/24 IPv4 /24 not checked
192.69.27.0/24 IPv4 /24 not checked
192.69.28.0/24 IPv4 /24 not checked
192.69.29.0/24 IPv4 /24 not checked
192.69.30.0/24 IPv4 /24 not checked
192.69.31.0/24 IPv4 /24 not checked
205.151.255.0/24 IPv4 /24 not checked
2620:11f:9002::/48 IPv6 /48 not checked
2620:11f:9006::/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 AS14746
Address families
NWAX: Primary Peering VLAN 1,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 AS14746 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS14746 in AS paths

Observed upstreams
Families
AS20055 AS-WHOLESAIL 344 2,674
v4 v6
AS11404 AS-WAVE-1 79 505
v4 v6
AS396930 OPUS-INTERACTIVE-VA1 124 168
v4
AS3257 GTT-BACKBONE 133 163
v4
AS6939 HURRICANE 97 124
v6
AS286 KPN 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS14746 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
AS36236 NETACTUATE 1 3
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.