bgpreport

Network · data from 2026-11-12

AS52860 Isaque Oliveira de Santana

Registry name: AS52860 - Isaque Oliveira Comercial LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52860, 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.
170.78.156.0/23 No ROA Nonecovered by 170.78.156.0/22 5 1%low visibility 4
170.78.158.0/23 No ROA Nonecovered by 170.78.156.0/22 5 1%low visibility 4
177.87.208.0/23 No ROA Nonecovered by 177.87.208.0/22 3 0%low visibility 2
177.87.210.0/23 No ROA Nonecovered by 177.87.208.0/22 3 0%low visibility 2
177.87.212.0/23 No ROA Nonecovered by 177.87.212.0/22 3 0%low visibility 2
177.87.214.0/23 No ROA Nonecovered by 177.87.212.0/22 3 0%low visibility 2
170.78.156.0/24 No ROA Other IRR onlyRADB 669 99% 66
177.87.208.0/21 No ROA Other IRR onlyRADB 669 99% 66
170.78.156.0/22 No ROA Other IRR onlyRADB 668 99% 66
2804:7a4::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS52860'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 22 are in fix.csv.

  • ROA: none10
  • Route object: none6
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none170.78.156.0/23No ROA covers it. Add a ROA for AS52860, maxLength 23.5 of 673
Route object: none170.78.156.0/23No route object for it. A route object for 170.78.156.0/22 with origin AS52860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52860 in the RIR database for the space.5 of 673
ROA: none170.78.158.0/23No ROA covers it. Add a ROA for AS52860, maxLength 23.5 of 673
Route object: none170.78.158.0/23No route object for it. A route object for 170.78.156.0/22 with origin AS52860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52860 in the RIR database for the space.5 of 673
ROA: none177.87.208.0/23No ROA covers it. Add a ROA for AS52860, maxLength 23.3 of 673
Route object: none177.87.208.0/23No route object for it. A route object for 177.87.208.0/22 with origin AS52860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52860 in the RIR database for the space.3 of 673
ROA: none177.87.210.0/23No ROA covers it. Add a ROA for AS52860, maxLength 23.3 of 673
Route object: none177.87.210.0/23No route object for it. A route object for 177.87.208.0/22 with origin AS52860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52860 in the RIR database for the space.3 of 673
ROA: none177.87.212.0/23No ROA covers it. Add a ROA for AS52860, maxLength 23.3 of 673
Route object: none177.87.212.0/23No route object for it. A route object for 177.87.212.0/22 with origin AS52860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52860 in the RIR database for the space.3 of 673
ROA: none177.87.214.0/23No ROA covers it. Add a ROA for AS52860, maxLength 23.3 of 673
Route object: none177.87.214.0/23No route object for it. A route object for 177.87.212.0/22 with origin AS52860 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52860 in the RIR database for the space.3 of 673
ROA: none170.78.156.0/24No ROA covers it. Add a ROA for AS52860, maxLength 24.669 of 673
Route object: RIR170.78.156.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none177.87.208.0/21No ROA covers it. Add a ROA for AS52860, maxLength 21.669 of 673
Route object: RIR177.87.208.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none170.78.156.0/22No ROA covers it. Add a ROA for AS52860, maxLength 22.668 of 673
Route object: RIR170.78.156.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:7a4::/32No ROA covers it. Add a ROA for AS52860, maxLength 32.634 of 636
Route object: RIR2804:7a4::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

177.87.208.0/22RADBNo ROA
177.87.212.0/22RADBNo 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.