Skip to main content

AS56186

DIGINET-NZ

Digital Island Ltd

Registry

Authoritative registration data

AS number
56186
Name
DIGINET-NZ
Organisation
Digital Island Ltd
Country
Flag of New Zealand NZ New Zealand
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS56186
202.3.80.0/21 IPv4 /21 not checked
202.92.216.0/21 IPv4 /21 not checked
103.13.8.0/22 IPv4 /22 not checked
43.245.240.0/22 IPv4 /22 not checked
202.92.222.0/23 IPv4 /23 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 AS56186
Address families
AKL-IX (Auckland NZ): AKL-IX 10,000 Mbps IPv4
MegaIX Auckland: MegaIX 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 AS56186 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS56186 in AS paths

Observed upstreams
Families
AS4648 SPARK-NZ 124 720
v4
AS6939 HURRICANE 21 102
v4
AS64073 VETTA 1 5
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS56186 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
AS35280 F5 1 5
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.