Skip to main content

AS199243

ZL4CAT-NET

=============

Registry

Authoritative registration data

AS number
199243
Name
ZL4CAT-NET
Organisation
=============
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

13

Total announced

15

Announced prefixes

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

Prefixes announced by AS199243
44.30.196.0/23 IPv4 /23 not checked
44.30.197.0/24 IPv4 /24 not checked
2a0c:9a40:d500::/40 IPv6 /40 RPKI valid
2a10:ccc3:1300::/40 IPv6 /40 RPKI valid
2a0c:9a40:d508::/48 IPv6 /48 not checked
2a0c:9a40:d510::/48 IPv6 /48 RPKI valid
2a0c:9a40:d520::/48 IPv6 /48 RPKI valid
2a0c:9a40:d5f0::/48 IPv6 /48 not checked
2a0c:9a40:d5f1::/48 IPv6 /48 RPKI valid
2a10:ccc3:1308::/48 IPv6 /48 RPKI valid
2a10:ccc3:1310::/48 IPv6 /48 RPKI valid
2a10:ccc3:1320::/48 IPv6 /48 RPKI valid
2a10:ccc3:13f0::/48 IPv6 /48 not checked
2a10:ccc3:13f1::/48 IPv6 /48 not checked
2a10:ccc3:13ff::/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 AS199243
Address families
AMS-IX 1,000 Mbps IPv4 · IPv6
Barcelona-IX 1,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · IPv6
NetIX: NetIX 100 Mbps IPv4 · IPv6
ONIX 1,000 Mbps IPv4 · IPv6
ixFabric - Amsterdam 1,000 Mbps 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 AS199243 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

22 networks seen before AS199243 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS199243 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

46 adjacencies that may be an artefact of collector peering

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.