bgpreport

Network · data from 2026-11-12

AS270282 AS270282 - SIMONE BARBOSA DO NASCIMENTO SOUZA COMUNICACAO

Registry name: AS270282 - SIMONE BARBOSA DO NASCIMENTO SOUZA COMUNICACAO, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270282, 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.
201.71.5.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 67
201.71.4.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 66
201.71.6.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 66
201.71.7.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
2804:69a4:c000::/34 Valid Other IRR onlyRADB 631 99% 69

AS-SET

AS270282 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 32 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
Route object: RIR201.71.5.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.71.4.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR201.71.6.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR201.71.7.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:69a4:c000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

201.71.4.0/22ALTDBNo ROA
201.71.4.0/23ALTDB, RADBNo ROA
201.71.6.0/23ALTDB, RADBNo ROA
2804:69a4::/32ALTDBNo ROA
2804:69a4::/33RADBNo ROA
2804:69a4::/34RADBNo ROA
2804:69a4::/35RADBNo ROA
2804:69a4::/36RADBNo ROA
2804:69a4:1000::/36RADBNo ROA
2804:69a4:2000::/35RADBNo ROA
2804:69a4:2000::/36RADBNo ROA
2804:69a4:3000::/36RADBNo ROA
2804:69a4:4000::/34RADBNo ROA
2804:69a4:4000::/35RADBNo ROA
2804:69a4:4000::/36RADBNo ROA
2804:69a4:5000::/36RADBNo ROA
2804:69a4:6000::/35RADBNo ROA
2804:69a4:6000::/36RADBNo ROA
2804:69a4:7000::/36RADBNo ROA
2804:69a4:8000::/33RADBNo ROA
2804:69a4:8000::/34RADBNo ROA
2804:69a4:8000::/35RADBNo ROA
2804:69a4:8000::/36RADBNo ROA
2804:69a4:9000::/36RADBNo ROA
2804:69a4:a000::/35RADBNo ROA
2804:69a4:a000::/36RADBNo ROA
2804:69a4:b000::/36RADBNo 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.