Skip to main content

AS44206

SIBSET-KRS-AS

----- Upstreams -----

Registry

Authoritative registration data

AS number
44206
Name
SIBSET-KRS-AS
Organisation
----- Upstreams -----
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS44206
77.240.160.0/20 IPv4 /20 not checked
80.253.224.0/20 IPv4 /20 not checked
89.250.16.0/20 IPv4 /20 not checked
79.99.216.0/21 IPv4 /21 not checked
94.127.248.0/21 IPv4 /21 not checked
185.103.160.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 AS44206 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS44206 in AS paths

Observed upstreams
Families
AS31133 MF-MGSM-AS 178 1,375
v4
AS3216 SOVAM-AS 114 999
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS44206 in AS paths

Observed downstreams
Families
AS48302 ATOMLINK-AS 116 1,310
v4
AS207978 KSC-SB-RAS-AS 14 14
v4
AS56326 ASDEVYATKA 7 14
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS25091 IP-Max 1 10
v4
AS49673 TRUENETWORK 1 10
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.