bgpreport

Network · data from 2026-11-12

AS265044 valtenir bezerra costa network

Registry name: AS265044 - MY INTERNET, BR · PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
5IPv6 routes 0.0% RPKI valid · 20.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS265044, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265044, 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:31e8::/34 No ROA Nonecovered by 2804:31e8::/33 325 51% 64
2804:31e8:4000::/34 No ROA Nonecovered by 2804:31e8::/33 325 51% 64
2804:31e8:8000::/34 No ROA Nonecovered by 2804:31e8::/32 325 51% 64
2804:31e8:c000::/34 No ROA Nonecovered by 2804:31e8::/32 325 51% 64
170.150.244.0/22 No ROA Other IRR onlyRADB, TC 670 100% 67
170.150.246.0/23 No ROA Other IRR onlyRADB 669 99% 67
170.150.244.0/23 No ROA Other IRR onlyRADB 668 99% 67
2804:31e8::/32 No ROA Other IRR onlyRADB, TC 635 100% 69
170.150.245.0/24 No ROA Other IRR onlyRADB 121 18% 43
170.150.244.0/24 No ROA Other IRR onlyRADB 118 18% 42
170.150.246.0/24 No ROA Other IRR onlyRADB 118 18% 42
170.150.247.0/24 No ROA Other IRR onlyRADB 118 18% 42

AS-SET

AS265044'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 25 are in fix.csv.

  • ROA: none12
  • Route object: none4
  • Route object: RIR8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:31e8::/34No ROA covers it. Add a ROA for AS265044, maxLength 34.325 of 636
Route object: none2804:31e8::/34No route object for it. A route object for 2804:31e8::/33 with origin AS265044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265044 in the RIR database for the space.325 of 636
ROA: none2804:31e8:4000::/34No ROA covers it. Add a ROA for AS265044, maxLength 34.325 of 636
Route object: none2804:31e8:4000::/34No route object for it. A route object for 2804:31e8::/33 with origin AS265044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265044 in the RIR database for the space.325 of 636
ROA: none2804:31e8:8000::/34No ROA covers it. Add a ROA for AS265044, maxLength 34.325 of 636
Route object: none2804:31e8:8000::/34No route object for it. A route object for 2804:31e8::/32 with origin AS265044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265044 in the RIR database for the space.325 of 636
ROA: none2804:31e8:c000::/34No ROA covers it. Add a ROA for AS265044, maxLength 34.325 of 636
Route object: none2804:31e8:c000::/34No route object for it. A route object for 2804:31e8::/32 with origin AS265044 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265044 in the RIR database for the space.325 of 636
ROA: none170.150.244.0/22No ROA covers it. Add a ROA for AS265044, maxLength 22.670 of 673
Route object: RIR170.150.244.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none170.150.246.0/23No ROA covers it. Add a ROA for AS265044, maxLength 23.669 of 673
Route object: RIR170.150.246.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none170.150.244.0/23No ROA covers it. Add a ROA for AS265044, maxLength 23.668 of 673
Route object: RIR170.150.244.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:31e8::/32No ROA covers it. Add a ROA for AS265044, maxLength 32.635 of 636
Route object: RIR2804:31e8::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none170.150.245.0/24No ROA covers it. Add a ROA for AS265044, maxLength 24.121 of 673
Route object: RIR170.150.245.0/24Route object only in RADB. Add it in the RIR database for the space.121 of 673
ROA: none170.150.244.0/24No ROA covers it. Add a ROA for AS265044, maxLength 24.118 of 673
Route object: RIR170.150.244.0/24Route object only in RADB. Add it in the RIR database for the space.118 of 673
ROA: none170.150.246.0/24No ROA covers it. Add a ROA for AS265044, maxLength 24.118 of 673
Route object: RIR170.150.246.0/24Route object only in RADB. Add it in the RIR database for the space.118 of 673
ROA: none170.150.247.0/24No ROA covers it. Add a ROA for AS265044, maxLength 24.118 of 673
Route object: RIR170.150.247.0/24Route object only in RADB. Add it in the RIR database for the space.118 of 673

Route objects not announced

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

2804:31e8::/33RADBNo 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.