bgpreport

Network · data from 2026-11-12

AS267625 LD PRODUTOS DE INFORMATICA

Registry name: AS267625 - LD PRODUTOS DE INFORMATICA EIRELI - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267625, 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.71.239.0/24 Valid Nonecovered by 45.71.236.0/22 669 99% 67
45.71.237.0/24 Valid Nonecovered by 45.71.236.0/22 666 99% 67
45.71.238.0/24 Valid Nonecovered by 45.71.236.0/22 666 99% 67
45.71.236.0/24 Valid Nonecovered by 45.71.236.0/22 665 99% 67
2804:4454::/34 Valid Nonecovered by 2804:4454::/32 345 54% 64
2804:4454:4000::/34 Valid Nonecovered by 2804:4454::/32 345 54% 64
2804:4454:8000::/34 Valid Nonecovered by 2804:4454::/32 345 54% 64
2804:4454:c000::/34 Valid Nonecovered by 2804:4454::/32 345 54% 64
45.71.236.0/22 Valid Other IRR onlyRADB 667 99% 67
2804:4454::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS267625'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 10 are in fix.csv.

  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.71.239.0/24No route object for it. A route object for 45.71.236.0/22 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.669 of 673
Route object: none45.71.237.0/24No route object for it. A route object for 45.71.236.0/22 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.666 of 673
Route object: none45.71.238.0/24No route object for it. A route object for 45.71.236.0/22 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.666 of 673
Route object: none45.71.236.0/24No route object for it. A route object for 45.71.236.0/22 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.665 of 673
Route object: none2804:4454::/34No route object for it. A route object for 2804:4454::/32 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.345 of 636
Route object: none2804:4454:4000::/34No route object for it. A route object for 2804:4454::/32 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.345 of 636
Route object: none2804:4454:8000::/34No route object for it. A route object for 2804:4454::/32 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.345 of 636
Route object: none2804:4454:c000::/34No route object for it. A route object for 2804:4454::/32 with origin AS267625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267625 in the RIR database for the space.345 of 636
Route object: RIR45.71.236.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:4454::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS267625 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.