bgpreport

Network · data from 2026-11-12

AS265162 JOSE RENATO COSTA DOS SANTOS DE NOVA SOURE - ME

Registry name: AS265162 - JOSE RENATO COSTA DOS SANTOS DE NOVA SOURE - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265162, 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.
2804:4850:d8::/45 Invalid: origin None 21 3%low visibility 14
143.255.228.0/23 No ROA Other IRR onlyRADB, TC 671 100% 67
143.255.228.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
143.255.229.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
143.255.231.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
2804:2b98::/32 Valid Other IRR onlyRADB, TC 636 100% 69
2804:2b98:4000::/34 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS265162'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 15 are in fix.csv.

  • ROA: origin1
  • ROA: none3
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin2804:4850:d8::/45ROAs covering it name AS267113, not AS265162. If AS265162 should announce it, add a ROA for AS265162.21 of 636
Route object: none2804:4850:d8::/45No route object for it. Add a route object with origin AS265162 in the RIR database for the space.21 of 636
ROA: none143.255.228.0/23No ROA covers it. Add a ROA for AS265162, maxLength 23.671 of 673
Route object: RIR143.255.228.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none143.255.228.0/24No ROA covers it. Add a ROA for AS265162, maxLength 24.671 of 673
Route object: RIR143.255.228.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none143.255.229.0/24No ROA covers it. Add a ROA for AS265162, maxLength 24.671 of 673
Route object: RIR143.255.229.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR143.255.231.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2b98::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2b98:4000::/34Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

143.255.228.0/22RADB, TCNo ROA
143.255.230.0/23RADB, TCNo ROA
2804:2b98::/33TCValid
2804:2b98:8000::/33TCValid

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.