AS47246 Omskie telekomunikacii Ltd.

Russia OmskTransitTelecom RIPE 0 IPv4 prefixes 1 IPv6 prefix

IPv4 addresses

IPv6 /48 networks

RPKI

1 valid0 no ROA

Peers and downstreams

Holder

AS name: OmskTransitTelecom
Description: Omskie telekomunikacii Ltd.
Organisation: Omskie telekomunikacii Ltd.
Registered in: Omsk, Russia
Abuse contact: abuse@omkc.ru
Assigned: 2008-05-22
Registered: 2008-05-23
Record last changed: 2022-04-06 09:09 UTC

None announced.

Upstream graph

Upstreams and their upstreams, from BGP paths

Network health

Grade B · 80/100

pass	Prefixes covered by valid ROAs 1 of 1 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 abuse@omkc.ru 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
fail	Registry record maintained Last changed 2022-04-06.	0/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/47246"><img src="https://ip-fd.net/badge/asn/47246/health.svg" alt="AS47246 network health on IP-FD.net"></a>

Markdown

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

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

Routing changes

Last 30 days

No changes recorded in the last 30 days. Changes are recorded each time the routing data of this AS is refreshed. Get alerts in real time.

WHOIS

aut-num:        AS47246
as-name:        OmskTransitTelecom
org:            ORG-OL37-RIPE
remarks:        ********************************************************
remarks:        You may use communities to control outgoing information
remarks:        via the route server. The meaning and order of remarks: evaluation is important:
remarks:        block announcement of a route to a certain peer 0:peer-as
remarks:        announcement of a route to a certain peer 47246:peer-as
remarks:        block announcement of a route to all peers 0:47246
remarks:        announcement of a route to all peers 47246:47246
remarks:        ********************************************************
admin-c:        DG5568-RIPE
tech-c:         DMF9-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         OmskTransitTelecom-mnt
created:        2008-05-23T12:08:09Z
last-modified:  2022-04-06T09:09:09Z
source:         RIPE
sponsoring-org: ORG-OksL1-RIPE
% 50 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/47246

const res = await fetch('https://ip-fd.net/api/v1/asn/47246', {
  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/47246', 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/47246');
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/47246", 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.