bgpreport

Network · data from 2026-11-12

AS61655 MASTERONLINE INTERNET FIBRA

Registry name: AS61655 - MASTERONLINE PROVEDOR DE INTERNET SCM EIRELI, BR · PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
5IPv6 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
4Route objects not announced registered with origin AS61655, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61655, 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.236.0/22 No ROA Other IRR onlyRADB, TC 669 99% 67
168.195.16.0/22 No ROA Other IRR onlyRADB, TC 669 99% 67
168.195.18.0/23 No ROA Other IRR onlyRADB 669 99% 67
2804:1c6c::/32 No ROA Other IRR onlyRADB, TC 635 100% 69
2804:1c6c::/33 No ROA Other IRR onlyRADB 635 100% 69
2804:1c6c:300::/40 No ROA Other IRR onlyRADB 635 100% 69
2804:1c6c:600::/40 No ROA Other IRR onlyRADB 635 100% 69
2804:1c6c:8000::/33 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

AS61655'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 20 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none131.100.236.0/22No ROA covers it. Add a ROA for AS61655, maxLength 22.669 of 673
Route object: RIR131.100.236.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none168.195.16.0/22No ROA covers it. Add a ROA for AS61655, maxLength 22.669 of 673
Route object: RIR168.195.16.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none168.195.18.0/23No ROA covers it. Add a ROA for AS61655, maxLength 23.669 of 673
Route object: RIR168.195.18.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:1c6c::/32No ROA covers it. Add a ROA for AS61655, maxLength 32.635 of 636
Route object: RIR2804:1c6c::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:1c6c::/33No ROA covers it. Add a ROA for AS61655, maxLength 33.635 of 636
Route object: RIR2804:1c6c::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1c6c:300::/40No ROA covers it. Add a ROA for AS61655, maxLength 40.635 of 636
Route object: RIR2804:1c6c:300::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1c6c:600::/40No ROA covers it. Add a ROA for AS61655, maxLength 40.635 of 636
Route object: RIR2804:1c6c:600::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1c6c:8000::/33No ROA covers it. Add a ROA for AS61655, maxLength 33.635 of 636
Route object: RIR2804:1c6c:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

131.100.236.0/23RADBNo ROA
131.100.238.0/23RADBNo ROA
168.195.16.0/23RADBNo ROA
168.195.17.0/24RADBNo 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.