bgpreport

Network · data from 2026-11-12

AS265168 AS265168 - M. S. Ferreira Alves

Registry name: AS265168 - M. S. Ferreira Alves, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265168, 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:2bac:2::/48 No ROA Nonecovered by 2804:2bac::/32 635 100% 67
2804:2bac:7::/48 No ROA Nonecovered by 2804:2bac::/32 635 100% 67
2804:2bac:800::/40 No ROA Nonecovered by 2804:2bac::/32 635 100% 67
167.249.76.0/22 No ROA Other IRR onlyRADB, TC 670 100% 66
2804:2bac::/32 No ROA Other IRR onlyRADB, TC 635 100% 70

AS-SET

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

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2804:2bac:2::/48No ROA covers it. Add a ROA for AS265168, maxLength 48.635 of 636
Route object: none2804:2bac:2::/48No route object for it. A route object for 2804:2bac::/32 with origin AS265168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265168 in the RIR database for the space.635 of 636
ROA: none2804:2bac:7::/48No ROA covers it. Add a ROA for AS265168, maxLength 48.635 of 636
Route object: none2804:2bac:7::/48No route object for it. A route object for 2804:2bac::/32 with origin AS265168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265168 in the RIR database for the space.635 of 636
ROA: none2804:2bac:800::/40No ROA covers it. Add a ROA for AS265168, maxLength 40.635 of 636
Route object: none2804:2bac:800::/40No route object for it. A route object for 2804:2bac::/32 with origin AS265168 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265168 in the RIR database for the space.635 of 636
ROA: none167.249.76.0/22No ROA covers it. Add a ROA for AS265168, maxLength 22.670 of 673
Route object: RIR167.249.76.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:2bac::/32No ROA covers it. Add a ROA for AS265168, maxLength 32.635 of 636
Route object: RIR2804:2bac::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

167.249.76.0/24RADBNo ROA
167.249.77.0/24RADBNo ROA
167.249.78.0/24RADBNo ROA
167.249.79.0/24RADBNo ROA
2804:3780::/32RADBNo 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.