bgpreport

Network · data from 2026-11-12

AS267258 AS267258 - J C DE ALMEIDA LIMA INFORMATICA - ME

Registry name: AS267258 - J C DE ALMEIDA LIMA INFORMATICA - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267258, 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.232.111.0/24 Valid Nonecovered by 45.232.108.0/22 670 100% 66
2804:4ab4:80::/44 Valid Nonecovered by 2804:4ab4::/32 632 99% 67
2804:4ab4::/33 Valid Nonecovered by 2804:4ab4::/32 348 55% 65
2804:4ab4:8000::/33 Valid Nonecovered by 2804:4ab4::/32 348 55% 65
45.232.110.0/23 Valid Nonecovered by 45.232.108.0/22 199 30% 56
45.232.108.0/23 Valid Nonecovered by 45.232.108.0/22 197 29% 56
45.232.108.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
2804:4ab4::/32 Valid Other IRR onlyRADB, TC 632 99% 67

AS-SET

AS267258 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 8 are in fix.csv.

  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.232.111.0/24No route object for it. A route object for 45.232.108.0/22 with origin AS267258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267258 in the RIR database for the space.670 of 673
Route object: none2804:4ab4:80::/44No route object for it. A route object for 2804:4ab4::/32 with origin AS267258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267258 in the RIR database for the space.632 of 636
Route object: none2804:4ab4::/33No route object for it. A route object for 2804:4ab4::/32 with origin AS267258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267258 in the RIR database for the space.348 of 636
Route object: none2804:4ab4:8000::/33No route object for it. A route object for 2804:4ab4::/32 with origin AS267258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267258 in the RIR database for the space.348 of 636
Route object: none45.232.110.0/23No route object for it. A route object for 45.232.108.0/22 with origin AS267258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267258 in the RIR database for the space.199 of 673
Route object: none45.232.108.0/23No route object for it. A route object for 45.232.108.0/22 with origin AS267258 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267258 in the RIR database for the space.197 of 673
Route object: RIR45.232.108.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4ab4::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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