bgpreport

Network · data from 2026-11-12

AS61403 Sever-Telecom-Cher Sever Telecom JSC

Registry name: Sever-Telecom-Cher Sever Telecom JSC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61403, 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.
178.57.108.0/24 No ROA Nonecovered by 178.57.108.0/22 673 100% 66
178.57.96.0/20 No ROA RIR databaseRIPE 673 100% 66
178.57.96.0/21 No ROA RIR databaseRIPE 673 100% 66
178.57.98.0/24 No ROA RIR databaseRIPE 673 100% 66
178.57.103.0/24 No ROA RIR databaseRIPE 673 100% 66
178.57.104.0/21 No ROA RIR databaseRIPE 673 100% 66
178.57.107.0/24 No ROA RIR databaseRIPE 673 100% 66
178.57.108.0/22 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS61403 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: none8
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none178.57.108.0/24No ROA covers it. Add a ROA for AS61403, maxLength 24.673 of 673
Route object: none178.57.108.0/24No route object for it. A route object for 178.57.108.0/22 with origin AS61403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61403 in the RIR database for the space.673 of 673
ROA: none178.57.96.0/20No ROA covers it. Add a ROA for AS61403, maxLength 20.673 of 673
ROA: none178.57.96.0/21No ROA covers it. Add a ROA for AS61403, maxLength 21.673 of 673
ROA: none178.57.98.0/24No ROA covers it. Add a ROA for AS61403, maxLength 24.673 of 673
ROA: none178.57.103.0/24No ROA covers it. Add a ROA for AS61403, maxLength 24.673 of 673
ROA: none178.57.104.0/21No ROA covers it. Add a ROA for AS61403, maxLength 21.673 of 673
ROA: none178.57.107.0/24No ROA covers it. Add a ROA for AS61403, maxLength 24.673 of 673
ROA: none178.57.108.0/22No ROA covers it. Add a ROA for AS61403, maxLength 22.673 of 673

Route objects not announced

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

178.57.99.0/24RIPENo ROA
178.57.109.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.