bgpreport

Network · data from 2026-11-12

AS48000 STREAM-TV-TAMBOV-AS MTS PJSC

Registry name: STREAM-TV-TAMBOV-AS MTS PJSC, RU · not in PeeringDB

7IPv4 routes 0.0% RPKI valid · 57.1% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS48000, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48000, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
5.227.105.0/24 No ROA Other origin only 671 100% 67
79.143.236.0/24 No ROA Other origin only 671 100% 67
213.176.254.0/23 No ROA Nonecovered by 213.176.248.0/21 7 1%low visibility 7
213.176.248.0/21 No ROA RIR databaseRIPE 673 100% 67
46.148.248.0/23 No ROA RIR databaseRIPE 671 100% 67
77.93.124.0/22 No ROA RIR databaseRIPE 671 100% 67
91.211.28.0/22 No ROA RIR databaseRIPE 671 100% 67

AS-SET

AS48000 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none5.227.105.0/24No ROA covers it. Add a ROA for AS48000, maxLength 24.671 of 673
Route object: none5.227.105.0/24Route objects for it name AS8359. Add a route object with origin AS48000 in the RIR database for the space.671 of 673
ROA: none79.143.236.0/24No ROA covers it. Add a ROA for AS48000, maxLength 24.671 of 673
Route object: none79.143.236.0/24Route objects for it name AS8359. Add a route object with origin AS48000 in the RIR database for the space.671 of 673
ROA: none213.176.254.0/23No ROA covers it. Add a ROA for AS48000, maxLength 23.7 of 673
Route object: none213.176.254.0/23No route object for it. A route object for 213.176.248.0/21 with origin AS48000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48000 in the RIR database for the space.7 of 673
ROA: none213.176.248.0/21No ROA covers it. Add a ROA for AS48000, maxLength 21.673 of 673
ROA: none46.148.248.0/23No ROA covers it. Add a ROA for AS48000, maxLength 23.671 of 673
ROA: none77.93.124.0/22No ROA covers it. Add a ROA for AS48000, maxLength 22.671 of 673
ROA: none91.211.28.0/22No ROA covers it. Add a ROA for AS48000, maxLength 22.671 of 673

Route objects not announced

Route objects with origin AS48000 whose prefix no peer sees AS48000 announce. Many are kept on purpose (backup routes, space announced only in some places).

81.177.79.0/24RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.