bgpreport

Network · data from 2026-11-12

AS268463 AS268463 - LOG INFORMATICA LTDA

Registry name: AS268463 - LOG INFORMATICA LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268463, 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.161.96.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
45.161.96.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
45.161.98.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
2804:5194::/33 Valid Other IRR onlyRADB, TC 636 100% 67
2804:5194:8000::/33 Valid Other IRR onlyRADB, TC 636 100% 67
2804:5194::/32 Valid Other IRR onlyRADB, TC 635 100% 67
45.161.96.0/24 Valid Other IRR onlyRADB, TC 202 30% 54
45.161.98.0/24 Valid Other IRR onlyRADB, TC 202 30% 54
45.161.99.0/24 Valid Other IRR onlyRADB, TC 202 30% 54
45.161.97.0/24 Valid Other IRR onlyRADB, TC 201 30% 54
2804:5194::/34 Valid Other IRR onlyTC 26 4%low visibility 12
2804:5194:4000::/34 Valid Other IRR onlyTC 26 4%low visibility 12
2804:5194:8000::/34 Valid Other IRR onlyTC 26 4%low visibility 12
2804:5194:c000::/34 Valid Other IRR onlyTC 26 4%low visibility 12

AS-SET

AS268463 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 14 are in fix.csv.

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR45.161.96.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.161.96.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.161.98.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:5194::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:5194:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:5194::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.161.96.0/24Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
Route object: RIR45.161.98.0/24Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
Route object: RIR45.161.99.0/24Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
Route object: RIR45.161.97.0/24Route object only in RADB, TC. Add it in the RIR database for the space.201 of 673
Route object: RIR2804:5194::/34Route object only in TC. Add it in the RIR database for the space.26 of 636
Route object: RIR2804:5194:4000::/34Route object only in TC. Add it in the RIR database for the space.26 of 636
Route object: RIR2804:5194:8000::/34Route object only in TC. Add it in the RIR database for the space.26 of 636
Route object: RIR2804:5194:c000::/34Route object only in TC. Add it in the RIR database for the space.26 of 636

Route objects not announced

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