Skip to main content

AS44383

KMR-UA-AS

--------------------------------------------------

Registry

Authoritative registration data

AS number
44383
Name
KMR-UA-AS
Organisation
--------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS44383
91.201.180.0/22 IPv4 /22 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 AS44383 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS44383 in AS paths

Observed upstreams
Families
AS1820 836 1,266
v4
AS35614 495 797
v4
AS3326 389 636
v4
AS6663 TTI-NET 4 5
v4

No rows match “”.

Showing of

Observed downstreams

10 networks seen after AS44383 in AS paths

Observed downstreams
Families
AS31072 301 778
v4
AS42095 533 687
v4
AS52182 299 389
v4
AS203706 165 212
v4
AS60455 46 154
v4
AS57441 58 62
v4
AS49389 STEALTH-AS 2 34
v4
AS204875 8 22
v4
AS51216 18 18
v4
AS6939 HURRICANE 6 8
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 5 38
v4
AS209823 5 6
v4
AS48919 4 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.