bgpreport

Network · data from 2026-11-12

AS268934 AS268934 - Placido e Siqueira Som e Imagem LTDA-ME

Registry name: AS268934 - Placido e Siqueira Som e Imagem LTDA-ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268934, 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.72.0/24 No ROA Nonecovered by 45.176.72.0/22 671 100% 67
45.176.73.0/24 No ROA Nonecovered by 45.176.72.0/22 671 100% 67
45.176.74.0/24 No ROA Nonecovered by 45.176.72.0/22 671 100% 67
45.176.75.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:5cd8::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS268934 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: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.176.72.0/24No ROA covers it. Add a ROA for AS268934, maxLength 24.671 of 673
Route object: none45.176.72.0/24No route object for it. A route object for 45.176.72.0/22 with origin AS268934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268934 in the RIR database for the space.671 of 673
ROA: none45.176.73.0/24No ROA covers it. Add a ROA for AS268934, maxLength 24.671 of 673
Route object: none45.176.73.0/24No route object for it. A route object for 45.176.72.0/22 with origin AS268934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268934 in the RIR database for the space.671 of 673
ROA: none45.176.74.0/24No ROA covers it. Add a ROA for AS268934, maxLength 24.671 of 673
Route object: none45.176.74.0/24No route object for it. A route object for 45.176.72.0/22 with origin AS268934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268934 in the RIR database for the space.671 of 673
ROA: none45.176.75.0/24No ROA covers it. Add a ROA for AS268934, maxLength 24.671 of 673
Route object: RIR45.176.75.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:5cd8::/32No ROA covers it. Add a ROA for AS268934, maxLength 32.636 of 636
Route object: RIR2804:5cd8::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.176.72.0/22TCNo 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.