bgpreport

Network · data from 2026-11-12

AS28812 JSCBIS-AS PJSC "Bashinformsvyaz"

Registry name: JSCBIS-AS PJSC "Bashinformsvyaz", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28812, 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.

31.8.0.0/16 No ROA RIR databaseRIPE 672 100% 67
37.122.0.0/17 No ROA RIR databaseRIPE 672 100% 67
62.133.160.0/19 No ROA RIR databaseRIPE 672 100% 67
77.94.96.0/19 No ROA RIR databaseRIPE 672 100% 67
83.174.192.0/18 No ROA RIR databaseRIPE 672 100% 67
92.245.32.0/19 No ROA RIR databaseRIPE 672 100% 67
94.75.0.0/18 No ROA RIR databaseRIPE 672 100% 67
95.110.0.0/17 No ROA RIR databaseRIPE 672 100% 67
109.187.0.0/16 No ROA RIR databaseRIPE 672 100% 67
178.129.0.0/16 No ROA RIR databaseRIPE 672 100% 67
185.169.100.0/22 No ROA RIR databaseRIPE 672 100% 67
213.189.224.0/20 No ROA RIR databaseRIPE 672 100% 67
2a02:240::/44 No ROA RIR databaseRIPE 635 100% 68

AS-SET

AS28812 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 52 are in fix.csv.

  • ROA: none13
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
ROA: none31.8.0.0/16No ROA covers it. Add a ROA for AS28812, maxLength 16.672 of 673
ROA: none37.122.0.0/17No ROA covers it. Add a ROA for AS28812, maxLength 17.672 of 673
ROA: none62.133.160.0/19No ROA covers it. Add a ROA for AS28812, maxLength 19.672 of 673
ROA: none77.94.96.0/19No ROA covers it. Add a ROA for AS28812, maxLength 19.672 of 673
ROA: none83.174.192.0/18No ROA covers it. Add a ROA for AS28812, maxLength 18.672 of 673
ROA: none92.245.32.0/19No ROA covers it. Add a ROA for AS28812, maxLength 19.672 of 673
ROA: none94.75.0.0/18No ROA covers it. Add a ROA for AS28812, maxLength 18.672 of 673
ROA: none95.110.0.0/17No ROA covers it. Add a ROA for AS28812, maxLength 17.672 of 673
ROA: none109.187.0.0/16No ROA covers it. Add a ROA for AS28812, maxLength 16.672 of 673
ROA: none178.129.0.0/16No ROA covers it. Add a ROA for AS28812, maxLength 16.672 of 673
ROA: none185.169.100.0/22No ROA covers it. Add a ROA for AS28812, maxLength 22.672 of 673
ROA: none213.189.224.0/20No ROA covers it. Add a ROA for AS28812, maxLength 20.672 of 673
ROA: none2a02:240::/44No ROA covers it. Add a ROA for AS28812, maxLength 44.635 of 636

Route objects not announced

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

31.8.0.0/18RIPENo ROA
31.8.64.0/18RIPENo ROA
31.8.128.0/18RIPENo ROA
37.122.64.0/18RIPENo ROA
62.133.160.0/20RIPENo ROA
62.133.160.0/21RIPENo ROA
62.133.168.0/21RIPENo ROA
62.133.176.0/20RIPENo ROA
62.133.184.0/21RIPENo ROA
77.94.96.0/21RIPENo ROA
77.94.96.0/22RIPENo ROA
77.94.104.0/21RIPENo ROA
77.94.112.0/22RIPENo ROA
77.94.120.0/22RIPENo ROA
77.94.124.0/22RIPENo ROA
83.174.192.0/20RIPENo ROA
83.174.208.0/20RIPENo ROA
83.174.208.0/21RIPENo ROA
83.174.224.0/20RIPENo ROA
83.174.224.0/21RIPENo ROA
83.174.232.0/22RIPENo ROA
83.174.236.0/22RIPENo ROA
83.174.240.0/21RIPENo ROA
83.174.248.0/21RIPENo ROA
91.220.92.0/24RIPENo ROA
91.234.178.0/24RIPENo ROA
95.110.0.0/19RIPENo ROA
95.110.32.0/19RIPENo ROA
95.110.64.0/19RIPENo ROA
95.110.96.0/19RIPENo ROA
109.187.0.0/17RIPENo ROA
109.187.128.0/17RIPENo ROA
178.129.0.0/17RIPENo ROA
178.129.128.0/17RIPENo ROA
185.169.100.0/23RIPENo ROA
185.169.102.0/23RIPENo ROA
213.189.255.0/24RIPENo ROA
2a02:240::/32RIPENo ROA
2a02:240:100::/40RIPENo 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.