bgpreport

Network · data from 2026-11-12

AS267408 ISP DE PERNAMBCO

Registry name: AS267408 - Provedor de Acesso a Internet de Pernambuco Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267408, 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.

45.234.9.0/24 No ROA Other origin onlycovered by 45.234.8.0/23 672 100% 66
45.234.11.0/24 No ROA Nonecovered by 45.234.10.0/23 669 99% 66
2804:4d08:c000::/34 No ROA Nonecovered by 2804:4d08::/32 635 100% 67
2804:4d08:4000::/34 No ROA Nonecovered by 2804:4d08::/32 634 100% 67
45.70.211.0/24 No ROA Other origin only 368 55% 60
45.234.8.0/24 Valid Nonecovered by 45.234.8.0/23 671 100% 66

AS-SET

AS267408'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: none5
  • Route object: none6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none45.234.9.0/24No ROA covers it. Add a ROA for AS267408, maxLength 24.672 of 673
Route object: none45.234.9.0/24Route objects for it name AS61568. A route object for 45.234.8.0/23 with origin AS267408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267408 in the RIR database for the space.672 of 673
ROA: none45.234.11.0/24No ROA covers it. Add a ROA for AS267408, maxLength 24.669 of 673
Route object: none45.234.11.0/24No route object for it. A route object for 45.234.10.0/23 with origin AS267408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267408 in the RIR database for the space.669 of 673
ROA: none2804:4d08:c000::/34No ROA covers it. Add a ROA for AS267408, maxLength 34.635 of 636
Route object: none2804:4d08:c000::/34No route object for it. A route object for 2804:4d08::/32 with origin AS267408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267408 in the RIR database for the space.635 of 636
ROA: none2804:4d08:4000::/34No ROA covers it. Add a ROA for AS267408, maxLength 34.634 of 636
Route object: none2804:4d08:4000::/34No route object for it. A route object for 2804:4d08::/32 with origin AS267408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267408 in the RIR database for the space.634 of 636
ROA: none45.70.211.0/24No ROA covers it. Add a ROA for AS267408, maxLength 24.368 of 673
Route object: none45.70.211.0/24Route objects for it name AS271618. Add a route object with origin AS267408 in the RIR database for the space.368 of 673
Route object: none45.234.8.0/24No route object for it. A route object for 45.234.8.0/23 with origin AS267408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267408 in the RIR database for the space.671 of 673

Route objects not announced

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

45.234.8.0/22NTTCOM, RADB, TCNo ROA
45.234.8.0/23RADBNo ROA
45.234.10.0/23RADBNo ROA
2804:3934::/32RADBNo ROA
2804:4d08::/32NTTCOM, RADB, TCNo 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.