Skip to main content

AS133399

HITECH1-AS-AP

HI-TECH SOLUTIONS LIMITED

Registry

Authoritative registration data

AS number
133399
Name
HITECH1-AS-AP
Organisation
HI-TECH SOLUTIONS LIMITED
Country
Flag of New Zealand NZ New Zealand
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS133399
103.226.112.0/22 IPv4 /22 not checked
45.64.116.0/22 IPv4 /22 not checked
103.240.133.0/24 IPv4 /24 not checked
2400:ab80::/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 AS133399
Address families
AKL-IX (Auckland NZ): AKL-IX 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 AS133399 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS133399 in AS paths

Observed upstreams
Families
AS4648 434 1,192
v4 v6
AS6939 HURRICANE 38 129
v4
AS17492 VECTOR-COMMUNICATIONS-AS 18 27
v6
AS64073 VETTA 1 4
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS133399 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS61138 1 4
v4 v6
AS132847 1 4
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.