bgpreport

Network · data from 2026-11-12

AS266894 LOJASYSTEM

Registry name: AS266894 - LOJASYSTEM C.A., EC · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS266894, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266894, 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.32.0/24 Valid Other IRR onlyRADB 667 99% 67
45.161.33.0/24 Valid Other IRR onlyRADB 667 99% 67
45.161.34.0/24 Valid Other IRR onlyRADB 665 99% 67
45.161.35.0/24 Valid Other IRR onlyRADB 664 99% 67
2803:56a0::/32 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:56a0:100::/40 Valid RIR databaseLACNIC 635 100% 67
2803:56a0:500::/40 Valid RIR databaseLACNIC 635 100% 67
2803:56a0:600::/40 Valid RIR databaseLACNIC 635 100% 67
2803:56a0:b00::/40 Valid RIR databaseLACNIC 633 100% 67

AS-SET

AS266894'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 17 are in fix.csv.

  • Route object: RIR4
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: RIR45.161.32.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.161.33.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.161.34.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR45.161.35.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673

Route objects not announced

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

45.161.32.0/22LACNIC, RADBValid
2803:56a0::/40LACNICValid
2803:56a0:200::/40LACNICValid
2803:56a0:300::/40LACNICValid
2803:56a0:400::/40LACNICValid
2803:56a0:700::/40LACNICValid
2803:56a0:800::/40LACNICValid
2803:56a0:900::/40LACNICValid
2803:56a0:a00::/40LACNICValid
2803:56a0:c00::/40LACNICValid
2803:56a0:2000::/40LACNICValid
2803:56a0:2100::/40LACNICValid
2803:56a0:2200::/40LACNICValid

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.