Skip to main content

AS197999

klarinet-as

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

Registry

Authoritative registration data

AS number
197999
Name
klarinet-as
Organisation
========================================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS197999
31.217.216.0/21 IPv4 /21 not checked
193.33.216.0/23 IPv4 /23 not checked
185.202.7.0/24 IPv4 /24 not checked
195.66.91.0/24 IPv4 /24 not checked
2a03:1a80::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS197999 in AS paths

Observed upstreams
Families
AS33891 CORE-BACKBONE 247 1,043
v4 v6
AS5404 conova-as 98 358
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS197999 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
AS35369 LINZAG-TELEKOM-AS 1 5
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.