Skip to main content

AS196924

NETMASTER

*********************************************************************

Registry

Authoritative registration data

AS number
196924
Name
NETMASTER
Organisation
*********************************************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS196924
195.191.126.0/24 IPv4 /24 not checked
195.191.127.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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS196924 in AS paths

Observed upstreams
Families
AS48648 KYIVLINK 130 290
v4
AS6939 HURRICANE 16 32
v4
AS14840 ASN14840 2 8
v4
AS6663 TTI-NET 1 2
v4
AS263444 ASN263444 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS196924 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
AS24482 SGGS-AS-AP 1 8
v4
AS48919 UA-CITY-AS 1 2
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.