AS60388 JSC "Oil Transportation and Production Telecommunications" #276

Russia TRANSNEFT-TELECOM-AS RIPE 19 IPv4 prefixes 5 IPv6 prefixes
IPv4 addresses
9,216
IPv6 /48 networks
131,072
RPKI
24 valid0 no ROA
Peers and downstreams
18

Holder

AS name
TRANSNEFT-TELECOM-AS
Description
Moscow Russia
Organisation
JSC "Oil Transportation and Production Telecommunications"
Registered in
Moscow, Russia
Abuse contact
stn-info@stn.transneft.ru
Assigned
2013-07-25
Registered
2013-07-26
Record last changed
2025-10-08 13:09 UTC

Upstream graph

Upstreams and their upstreams, from BGP paths

Network rating

#276 of 123,601 · 91.7/100
Customer cone
weight 27%, 88,059 networks behind this AS
97
Announced address space
weight 22%
93
Peers and providers
weight 16%
97
Registry record
weight 11%
70
Routing stability
weight 11%
79
RPKI and IPv6
weight 13%
100

Network health

Grade A · 90/100
pass Prefixes covered by valid ROAs
24 of 24 announced prefixes are RPKI valid.
25/25
pass No RPKI invalid announcements
None of the announcements is RPKI invalid.
10/10
pass Announces IPv6
5 IPv6 prefixes.
15/15
pass More than one upstream
10 upstreams seen in BGP.
10/10
pass Working abuse contact
stn-info@stn.transneft.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
pass Registry record maintained
Last changed 2025-10-08.
5/5

Routing changes

Last 30 days
2026-11-04 11:24 UTCNeighbour gone AS51369 upstream

WHOIS

aut-num:        AS60388
as-name:        TRANSNEFT-TELECOM-AS
descr:          Moscow Russia
org:            ORG-JTAP1-RIPE
remarks:        --= UPSTREAMS =--
remarks:        *** IPv4 ***
remarks:        *** IPv6 ***
remarks:        --= PEERS/IX =--
remarks:        *** IPv4 ***
remarks:        *** IPv6 ***
remarks:        --= DOWNSTREAMS =--
remarks:        *** IPv4 ***
remarks:        *** IPv6 ***
remarks:        BGP communities in advertisements towards downstream
remarks:        1. Route type:
remarks:        60388:901 Downstream's route
remarks:        60388:902 Peer's route
remarks:        60388:903 IX's route
remarks:        60388:905 Upstream's route
remarks:        2. Where the route has been received:
remarks:        60388:XYYZZ, where
remarks:        X - route type
remarks:        1 - customer
remarks:        2 - peer
remarks:        3 - IX
remarks:        5 - upstream
remarks:        YY - region
remarks:        02 - Ufa
remarks:        16 - Kazan
remarks:        24 - Krasnoyarsk
remarks:        27 - Khabarovsk
remarks:        28 - Blagoveschensk
remarks:        38 - Irkutsk
remarks:        52 - Nizhniy Novgorod
remarks:        54 - Novosibirsk
remarks:        55 - Omsk
remarks:        58 - Penza
remarks:        62 - Ryazan
remarks:        63 - Samara
remarks:        72 - Tumen
remarks:        74 - Chelyabinsk
remarks:        77 - Moscow
remarks:        ZZ - site id [00-99]
remarks:        BGP communities accepted from downstream
remarks:        1. Prepending :
remarks:        649XY:X, where
remarks:        X = 0 (upstreams + peers), 2 (peers), 5 (upstreams)
remarks:        Y = 1,3,5 - prepend Y times, 9 - do not advertise
remarks:        2. Prepending to upstream/peer ASN: 6480Y:ASN, where
remarks:        Y = 1,3,5 - prepend Y times, 9 - do not advertise
remarks:        3. Backup community:
remarks:        60388:00 - Set local preference 50 (backup)
admin-c:        SA44198-RIPE
tech-c:         SA44198-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         lir-ru-join-stock-1-MNT
created:        2013-07-26T12:03:35Z
last-modified:  2025-10-08T13:09:23Z
source:         RIPE
% 76 routing policy lines (import/export) not shown