bgpreport

Network · data from 2026-11-12

AS61686 A.J.D da Silva Manutenção de Micro

Registry name: AS61686 - A.J.D da Silva Manutencao de Micro, BR · PeeringDB

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

Announced routes

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

131.100.232.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
131.100.234.0/23 No ROA Other IRR onlyRADB, TC 672 100% 67

AS-SET

AS61686's PeeringDB record names no 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 40 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: none131.100.232.0/24No ROA covers it. Add a ROA for AS61686, maxLength 24.672 of 673
Route object: RIR131.100.232.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none131.100.234.0/23No ROA covers it. Add a ROA for AS61686, maxLength 23.672 of 673
Route object: RIR131.100.234.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

131.100.232.0/22RADB, TCNo ROA
131.100.232.0/23RADB, TCNo ROA
131.100.233.0/24RADB, TCNo ROA
131.100.234.0/24RADB, TCNo ROA
131.100.235.0/24RADB, TCNo ROA
2804:1cf8::/32RADB, TCNo ROA
2804:1cf8::/33RADBNo ROA
2804:1cf8::/34RADBNo ROA
2804:1cf8::/35RADBNo ROA
2804:1cf8::/36RADBNo ROA
2804:1cf8:1000::/36RADBNo ROA
2804:1cf8:2000::/35RADBNo ROA
2804:1cf8:2000::/36RADBNo ROA
2804:1cf8:3000::/36RADBNo ROA
2804:1cf8:4000::/34RADBNo ROA
2804:1cf8:4000::/35RADBNo ROA
2804:1cf8:4000::/36RADBNo ROA
2804:1cf8:5000::/36RADBNo ROA
2804:1cf8:6000::/35RADBNo ROA
2804:1cf8:6000::/36RADBNo ROA
2804:1cf8:7000::/36RADBNo ROA
2804:1cf8:8000::/33RADBNo ROA
2804:1cf8:8000::/34RADBNo ROA
2804:1cf8:8000::/35RADBNo ROA
2804:1cf8:8000::/36RADBNo ROA
2804:1cf8:9000::/36RADBNo ROA
2804:1cf8:a000::/35RADBNo ROA
2804:1cf8:a000::/36RADBNo ROA
2804:1cf8:b000::/36RADBNo ROA
2804:1cf8:c000::/34RADBNo ROA
2804:1cf8:c000::/35RADBNo ROA
2804:1cf8:c000::/36RADBNo ROA
2804:1cf8:d000::/36RADBNo ROA
2804:1cf8:e000::/35RADBNo ROA
2804:1cf8:e000::/36RADBNo ROA
2804:1cf8:f000::/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.