bgpreport

Network · data from 2026-11-12

AS48511 Sector Telecom Ltd.

Registry name: SECTOR-TELECOM-AS Sector Telecom Ltd., RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48511, 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.
146.120.223.0/24 Valid Nonecovered by 146.120.222.0/23 2 0%low visibility 2
95.46.196.0/24 Valid RIR databaseRIPE 673 100% 66
146.120.222.0/23 Valid RIR databaseRIPE 673 100% 66
2a02:128:22::/48 Valid RIR databaseRIPE 636 100% 68

AS-SET

AS48511's PeeringDB record names no 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none146.120.223.0/24No route object for it. A route object for 146.120.222.0/23 with origin AS48511 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48511 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS48511 is announced.

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.