bgpreport

Network · data from 2026-11-12

AS263102 R A DIAS SANTOS PROVEDOR DE INTERNET

Registry name: AS263102 - R A DIAS SANTOS PROVEDOR DE INTERNET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263102, 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:5558:2a00::/40 No ROA Nonecovered by 2804:5558::/32 636 100% 67
2804:5558:2b00::/40 No ROA Nonecovered by 2804:5558::/32 636 100% 67
45.165.236.0/22 No ROA Other IRR onlyRADB 671 100% 67
45.165.237.0/24 No ROA Other IRR onlyRADB 664 99% 67
45.165.238.0/24 No ROA Other IRR onlyRADB 664 99% 67
45.165.239.0/24 No ROA Other IRR onlyRADB 664 99% 67
45.165.236.0/24 No ROA Other IRR onlyRADB 663 99% 67
2804:5558::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS263102'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 16 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none2804:5558:2a00::/40No ROA covers it. Add a ROA for AS263102, maxLength 40.636 of 636
Route object: none2804:5558:2a00::/40No route object for it. A route object for 2804:5558::/32 with origin AS263102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263102 in the RIR database for the space.636 of 636
ROA: none2804:5558:2b00::/40No ROA covers it. Add a ROA for AS263102, maxLength 40.636 of 636
Route object: none2804:5558:2b00::/40No route object for it. A route object for 2804:5558::/32 with origin AS263102 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263102 in the RIR database for the space.636 of 636
ROA: none45.165.236.0/22No ROA covers it. Add a ROA for AS263102, maxLength 22.671 of 673
Route object: RIR45.165.236.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.165.237.0/24No ROA covers it. Add a ROA for AS263102, maxLength 24.664 of 673
Route object: RIR45.165.237.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none45.165.238.0/24No ROA covers it. Add a ROA for AS263102, maxLength 24.664 of 673
Route object: RIR45.165.238.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none45.165.239.0/24No ROA covers it. Add a ROA for AS263102, maxLength 24.664 of 673
Route object: RIR45.165.239.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none45.165.236.0/24No ROA covers it. Add a ROA for AS263102, maxLength 24.663 of 673
Route object: RIR45.165.236.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none2804:5558::/32No ROA covers it. Add a ROA for AS263102, maxLength 32.636 of 636
Route object: RIR2804:5558::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS263102 is announced.

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.