bgpreport

Network · data from 2026-11-12

AS61885 AS61885 - MGNETMOC LTDA

Registry name: AS61885 - MGNETMOC LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61885, 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.0.140.0/24 No ROA Other IRR onlyRADB 672 100% 67
131.0.141.0/24 No ROA Other IRR onlyRADB 672 100% 67
131.0.142.0/24 No ROA Other IRR onlyRADB 672 100% 67
131.0.143.0/24 No ROA Other IRR onlyRADB 672 100% 67
2804:1ac8::/34 No ROA Other IRR onlyRADB 633 100% 70
2804:1ac8:4000::/34 No ROA Other IRR onlyRADB 633 100% 70
2804:1ac8:8000::/34 No ROA Other IRR onlyRADB 633 100% 70
2804:1ac8:c000::/34 No ROA Other IRR onlyRADB 633 100% 70

AS-SET

AS61885 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 25 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none131.0.140.0/24No ROA covers it. Add a ROA for AS61885, maxLength 24.672 of 673
Route object: RIR131.0.140.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.0.141.0/24No ROA covers it. Add a ROA for AS61885, maxLength 24.672 of 673
Route object: RIR131.0.141.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.0.142.0/24No ROA covers it. Add a ROA for AS61885, maxLength 24.672 of 673
Route object: RIR131.0.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none131.0.143.0/24No ROA covers it. Add a ROA for AS61885, maxLength 24.672 of 673
Route object: RIR131.0.143.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:1ac8::/34No ROA covers it. Add a ROA for AS61885, maxLength 34.633 of 636
Route object: RIR2804:1ac8::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:1ac8:4000::/34No ROA covers it. Add a ROA for AS61885, maxLength 34.633 of 636
Route object: RIR2804:1ac8:4000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:1ac8:8000::/34No ROA covers it. Add a ROA for AS61885, maxLength 34.633 of 636
Route object: RIR2804:1ac8:8000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:1ac8:c000::/34No ROA covers it. Add a ROA for AS61885, maxLength 34.633 of 636
Route object: RIR2804:1ac8:c000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

45.184.120.0/23RADBNo ROA
45.184.120.0/24RADBNo ROA
45.184.121.0/24RADBNo ROA
45.184.122.0/23RADBNo ROA
45.184.122.0/24RADBNo ROA
45.184.123.0/24RADBNo ROA
131.0.140.0/22RADBNo ROA
131.0.140.0/23RADBNo ROA
2804:1ac8::/32RADBNo 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.