bgpreport

Network · data from 2026-11-12

AS61002 SMART-SOLUTIONS-AS Smart Solutions & Soft SRL

Registry name: SMART-SOLUTIONS-AS Smart Solutions & Soft SRL, RO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61002, 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.
85.120.128.0/22 Invalid: origin Other origin only 3 0%low visibility 3
85.120.132.0/22 Invalid: origin Other origin only 3 0%low visibility 3
80.96.4.0/23 No ROA RIR databaseRIPE 671 100% 67
80.96.188.0/23 No ROA RIR databaseRIPE 671 100% 67
80.97.54.0/23 No ROA RIR databaseRIPE 671 100% 67
81.180.80.0/24 No ROA RIR databaseRIPE 670 100% 67
81.180.81.0/24 No ROA RIR databaseRIPE 670 100% 67
77.111.80.0/22 Valid RIR databaseRIPE 671 100% 67
121.127.36.0/24 Valid RIR databaseRIPE 671 100% 67
217.156.28.0/24 Valid RIR databaseRIPE 671 100% 67
217.156.108.0/23 Valid RIR databaseRIPE 671 100% 67
80.96.107.0/24 Valid RIR databaseRIPE 670 100% 67
80.97.55.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS61002 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 10 are in fix.csv.

  • ROA: origin2
  • ROA: none5
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin85.120.128.0/22ROAs covering it name AS2914, not AS61002. If AS61002 should announce it, add a ROA for AS61002.3 of 673
Route object: none85.120.128.0/22Route objects for it name AS2914. Add a route object with origin AS61002 in the RIR database for the space.3 of 673
ROA: origin85.120.132.0/22ROAs covering it name AS2914, not AS61002. If AS61002 should announce it, add a ROA for AS61002.3 of 673
Route object: none85.120.132.0/22Route objects for it name AS2914. Add a route object with origin AS61002 in the RIR database for the space.3 of 673
ROA: none80.96.4.0/23No ROA covers it. Add a ROA for AS61002, maxLength 23.671 of 673
ROA: none80.96.188.0/23No ROA covers it. Add a ROA for AS61002, maxLength 23.671 of 673
ROA: none80.97.54.0/23No ROA covers it. Add a ROA for AS61002, maxLength 23.671 of 673
ROA: none81.180.80.0/24No ROA covers it. Add a ROA for AS61002, maxLength 24.670 of 673
ROA: none81.180.81.0/24No ROA covers it. Add a ROA for AS61002, maxLength 24.670 of 673

Route objects not announced

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

80.96.106.0/23RIPENo 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.