bgpreport

Network · data from 2026-11-12

AS268946 AS268946 - SMNET TELECOMUNICACOES

Registry name: AS268946 - SMNET TELECOMUNICACOES, BR · not in PeeringDB

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

Announced routes

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

45.176.156.0/22 No ROA Other IRR onlyTC 671 100% 66
45.176.157.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.176.158.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.176.159.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.176.158.0/23 No ROA Other IRR onlyRADB 669 99% 66
45.176.156.0/24 No ROA Other IRR onlyRADB 668 99% 66
2804:5d04:c000::/34 No ROA Other IRR onlyRADB 636 100% 69
2804:5d04::/32 No ROA Other IRR onlyRADB, TC 635 100% 69
2804:5d04:4000::/34 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

AS268946 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 20 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.176.156.0/22No ROA covers it. Add a ROA for AS268946, maxLength 22.671 of 673
Route object: RIR45.176.156.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.176.157.0/24No ROA covers it. Add a ROA for AS268946, maxLength 24.670 of 673
Route object: RIR45.176.157.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.176.158.0/24No ROA covers it. Add a ROA for AS268946, maxLength 24.670 of 673
Route object: RIR45.176.158.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.176.159.0/24No ROA covers it. Add a ROA for AS268946, maxLength 24.670 of 673
Route object: RIR45.176.159.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.176.158.0/23No ROA covers it. Add a ROA for AS268946, maxLength 23.669 of 673
Route object: RIR45.176.158.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.176.156.0/24No ROA covers it. Add a ROA for AS268946, maxLength 24.668 of 673
Route object: RIR45.176.156.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:5d04:c000::/34No ROA covers it. Add a ROA for AS268946, maxLength 34.636 of 636
Route object: RIR2804:5d04:c000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:5d04::/32No ROA covers it. Add a ROA for AS268946, maxLength 32.635 of 636
Route object: RIR2804:5d04::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5d04:4000::/34No ROA covers it. Add a ROA for AS268946, maxLength 34.635 of 636
Route object: RIR2804:5d04:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.176.156.0/23RADBNo ROA
2804:5d04::/34RADBNo 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.