bgpreport

Network · data from 2026-11-12

AS265385 AS265385 - Interline Provedor

Registry name: AS265385 - Interline Provedor, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265385, 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:3344:8000::/35 No ROA Nonecovered by 2804:3344:8000::/34 635 100% 67
2804:3344:a000::/35 No ROA Nonecovered by 2804:3344:8000::/34 635 100% 67
170.254.248.0/24 No ROA Other IRR onlyRADB 669 99% 67
170.254.249.0/24 No ROA Other IRR onlyRADB 669 99% 67
170.254.250.0/24 No ROA Other IRR onlyRADB 669 99% 67
170.254.251.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:3344::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 69
2804:3344:8000::/33 No ROA Other IRR onlyRADB 635 100% 69
2804:3344:c000::/34 No ROA Other IRR onlyRADB 635 100% 69
2804:3344::/33 No ROA Other IRR onlyRADB 634 100% 69
2804:3344::/34 No ROA Other IRR onlyRADB 634 100% 69
2804:3344:4000::/34 No ROA Other IRR onlyRADB 634 100% 69
2804:3344:8000::/34 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS265385 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 29 are in fix.csv.

  • ROA: none13
  • Route object: none2
  • Route object: RIR11
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:3344:8000::/35No ROA covers it. Add a ROA for AS265385, maxLength 35.635 of 636
Route object: none2804:3344:8000::/35No route object for it. A route object for 2804:3344:8000::/34 with origin AS265385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265385 in the RIR database for the space.635 of 636
ROA: none2804:3344:a000::/35No ROA covers it. Add a ROA for AS265385, maxLength 35.635 of 636
Route object: none2804:3344:a000::/35No route object for it. A route object for 2804:3344:8000::/34 with origin AS265385 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265385 in the RIR database for the space.635 of 636
ROA: none170.254.248.0/24No ROA covers it. Add a ROA for AS265385, maxLength 24.669 of 673
Route object: RIR170.254.248.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none170.254.249.0/24No ROA covers it. Add a ROA for AS265385, maxLength 24.669 of 673
Route object: RIR170.254.249.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none170.254.250.0/24No ROA covers it. Add a ROA for AS265385, maxLength 24.669 of 673
Route object: RIR170.254.250.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none170.254.251.0/24No ROA covers it. Add a ROA for AS265385, maxLength 24.667 of 673
Route object: RIR170.254.251.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:3344::/32No ROA covers it. Add a ROA for AS265385, maxLength 32.635 of 636
Route object: RIR2804:3344::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:3344:8000::/33No ROA covers it. Add a ROA for AS265385, maxLength 33.635 of 636
Route object: RIR2804:3344:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:3344:c000::/34No ROA covers it. Add a ROA for AS265385, maxLength 34.635 of 636
Route object: RIR2804:3344:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:3344::/33No ROA covers it. Add a ROA for AS265385, maxLength 33.634 of 636
Route object: RIR2804:3344::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:3344::/34No ROA covers it. Add a ROA for AS265385, maxLength 34.634 of 636
Route object: RIR2804:3344::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:3344:4000::/34No ROA covers it. Add a ROA for AS265385, maxLength 34.634 of 636
Route object: RIR2804:3344:4000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2804:3344:8000::/34No ROA covers it. Add a ROA for AS265385, maxLength 34.634 of 636
Route object: RIR2804:3344:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

170.254.248.0/22ALTDB, RADBNo ROA
170.254.248.0/23RADBNo ROA
170.254.250.0/23RADBNo 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.