Skip to main content

AS43576

KUMIR-AS

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

Registry

Authoritative registration data

AS number
43576
Name
KUMIR-AS
Organisation
================================================================
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS43576
91.197.144.0/22 IPv4 /22 not checked
185.239.184.0/24 IPv4 /24 not checked
217.147.162.0/24 IPv4 /24 not checked
2a0c:6580::/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 AS43576
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4 · IPv6
Giganet IXN: Global exchange 10,000 Mbps IPv4 · IPv6
UA-IX 10,000 Mbps IPv4 · 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 AS43576 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS43576 in AS paths

Observed upstreams
Families
AS57455 918 2,370
v4
AS28917 294 721
v4
AS35320 322 718
v4 v6
AS6939 HURRICANE 74 103
v6
AS3303 SWISSCOM 11 26
v4 v6
AS6663 5 13
v4 v6
AS48648 7 11
v4 v6

No rows match “”.

Showing of

Observed downstreams

6 networks seen after AS43576 in AS paths

Observed downstreams
Families
AS21379 258 846
v4
AS39049 295 764
v4
AS41316 289 379
v4
AS35365 133 343
v4
AS204541 105 142
v4
AS207085 64 82
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 42
v4
AS49544 i3Dnet 4 16
v4 v6
AS59514 4 7
v4
AS48919 3 7
v4 v6
AS44901 3 6
v4
AS209823 3 6
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.