bgpreport

Network · data from 2026-11-12

AS271151 AS271151 - RAFAEL DOMINGOS DA SILVA LTDA

Registry name: AS271151 - RAFAEL DOMINGOS DA SILVA LTDA, BR · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
1Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS271151, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271151, 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.
179.42.118.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
179.42.116.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
179.42.117.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
2804:770c::/36 Valid Other IRR onlyTC 630 99% 67
2804:770c:1000::/36 Valid Other IRR onlyTC 630 99% 67
2804:770c:8000::/33 Valid Other IRR onlyTC 626 98% 67
2804:770c:f000::/36 Valid Other IRR onlyTC 626 98% 67
2804:770c::/33 Valid Other IRR onlyTC 1 0%low visibility 1

AS-SET

AS271151 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 13 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR179.42.118.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR179.42.116.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR179.42.117.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:770c::/36Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:770c:1000::/36Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:770c:8000::/33Route object only in TC. Add it in the RIR database for the space.626 of 636
Route object: RIR2804:770c:f000::/36Route object only in TC. Add it in the RIR database for the space.626 of 636
Route object: RIR2804:770c::/33Route object only in TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

179.42.116.0/22RADB, TCValid
179.42.116.0/23RADB, TCValid
179.42.118.0/23RADB, TCValid
179.42.119.0/24RADB, TCValid
2804:770c::/32RADB, TCValid

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.