AS207154 PE Luseya Plyus

Uzbekistan LUSEYA-PLYUS-AS RIPE 2 IPv4 prefixes 1 IPv6 prefix

IPv4 addresses

2,048

IPv6 /48 networks

RPKI

3 valid0 no ROA

Peers and downstreams

Holder

AS name: LUSEYA-PLYUS-AS
Description: PE Luseya Plyus
Organisation: PE Luseya Plyus
Registered in: Tashkent, Uzbekistan
Abuse contact: info@spi.uz
Assigned: 2022-03-16
Registered: 2022-03-17
Record last changed: 2024-08-21 11:47 UTC

92.253.192.0/22 93.170.220.0/22

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade B · 85/100

pass	Prefixes covered by valid ROAs 3 of 3 announced prefixes are RPKI valid.	25/25
pass	No RPKI invalid announcements None of the announcements is RPKI invalid.	10/10
pass	Announces IPv6 1 IPv6 prefix.	15/15
partly	More than one upstream 1 upstream seen in BGP.	5/10
pass	Working abuse contact info@spi.uz is published.	15/15
fail	Publishes a geofeed No geofeed found. Without one, location databases have to guess.	0/10
pass	No prefixes smaller than /24 or /48 All prefixes are /24 (IPv4) or /48 (IPv6) or larger.	10/10
pass	Registry record maintained Last changed 2024-08-21.	5/5

Built from the announced prefixes, RPKI, the registry record and geofeeds. Checks without data are not counted. Also in the API.

Show this on your website

HTML

<a href="https://ip-fd.net/asn/207154"><img src="https://ip-fd.net/badge/asn/207154/health.svg" alt="AS207154 network health on IP-FD.net"></a>

Markdown

[![AS207154 network health](https://ip-fd.net/badge/asn/207154/health.svg)](https://ip-fd.net/asn/207154)

Use rpki.svg instead of health.svg for the RPKI badge.

Routing changes

Last 30 days

2026-10-04 10:06 UTC

New prefix

2a02:128:2000::/44

WHOIS

aut-num:        AS207154
as-name:        LUSEYA-PLYUS-AS
org:            ORG-PLP6-RIPE
sponsoring-org: ORG-ATS13-RIPE
admin-c:        PLPN1-RIPE
tech-c:         PLPN1-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         RIPE-DB-MNT
created:        2022-03-17T14:08:05Z
last-modified:  2024-08-21T11:47:52Z
source:         RIPE
% 2 routing policy lines (import/export) not shown

Routing data

Updated just now

Registry record

Fetched just now from RIPE

Prefixes and neighbours come from the RIPE RIS route collectors. Data older than 5 minutes is refreshed when this page is opened.

API

curl -H "X-API-Key: YOUR_KEY" https://ip-fd.net/api/v1/asn/207154

const res = await fetch('https://ip-fd.net/api/v1/asn/207154', {
  headers: { 'X-API-Key': 'YOUR_KEY' }
});
const data = await res.json();
console.log(data);

import requests

r = requests.get('https://ip-fd.net/api/v1/asn/207154', headers={'X-API-Key': 'YOUR_KEY'}, timeout=10)
r.raise_for_status()
print(r.json())

<?php
$ch = curl_init('https://ip-fd.net/api/v1/asn/207154');
curl_setopt($ch, CURLOPT_HTTPHEADER, ['X-API-Key: YOUR_KEY']);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$data = json_decode(curl_exec($ch), true);
print_r($data);

req, _ := http.NewRequest("GET", "https://ip-fd.net/api/v1/asn/207154", nil)
req.Header.Set("X-API-Key", "YOUR_KEY")
res, err := http.DefaultClient.Do(req)
if err != nil {
    log.Fatal(err)
}
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Works without a key at a lower rate. Get a free key.