Skip to main content

AS26467

HYPERTEK

HyperTEK Corporation

Registry

Authoritative registration data

AS number
26467
Name
HYPERTEK
Organisation
HyperTEK Corporation
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS26467
208.69.216.0/24 IPv4 /24 not checked
208.69.217.0/24 IPv4 /24 not checked
208.69.218.0/24 IPv4 /24 not checked
208.69.219.0/24 IPv4 /24 not checked
208.69.220.0/24 IPv4 /24 not checked
208.69.221.0/24 IPv4 /24 not checked
208.69.222.0/24 IPv4 /24 not checked
208.69.223.0/24 IPv4 /24 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 AS26467
Address families
DET-iX 20,000 Mbps IPv4

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 AS26467 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS26467 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 235 2,010
v4
AS174 COGENT-174 261 910
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS26467 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
AS20205 AMPLEX 1 6
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.