bgpreport

Network · data from 2026-11-12

AS264609 TECOMUNICA NICARAGUA

Registry name: AS264609 - TECOMUNICA NICARAGUA, NI · PeeringDB

8IPv4 routes 100.0% RPKI valid · 25.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.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 AS264609, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264609, 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.
143.202.252.0/24 Valid Nonecovered by 143.202.252.0/22 672 100% 67
143.202.254.0/24 Valid Nonecovered by 143.202.252.0/22 672 100% 67
143.202.255.0/24 Valid Nonecovered by 143.202.252.0/22 672 100% 67
181.193.150.0/24 Valid Nonecovered by 181.193.150.0/23 672 100% 68
181.193.151.0/24 Valid Nonecovered by 181.193.150.0/23 672 100% 68
143.202.253.0/24 Valid Nonecovered by 143.202.252.0/22 665 99% 68
143.202.252.0/22 Valid RIR databaseLACNIC, RADB 672 100% 68
181.193.150.0/23 Valid RIR databaseLACNIC 671 100% 68
2803:9140::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

AS264609'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 6 are in fix.csv.

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none143.202.252.0/24No route object for it. A route object for 143.202.252.0/22 with origin AS264609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264609 in the RIR database for the space.672 of 673
Route object: none143.202.254.0/24No route object for it. A route object for 143.202.252.0/22 with origin AS264609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264609 in the RIR database for the space.672 of 673
Route object: none143.202.255.0/24No route object for it. A route object for 143.202.252.0/22 with origin AS264609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264609 in the RIR database for the space.672 of 673
Route object: none181.193.150.0/24No route object for it. A route object for 181.193.150.0/23 with origin AS264609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264609 in the RIR database for the space.672 of 673
Route object: none181.193.151.0/24No route object for it. A route object for 181.193.150.0/23 with origin AS264609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264609 in the RIR database for the space.672 of 673
Route object: none143.202.253.0/24No route object for it. A route object for 143.202.252.0/22 with origin AS264609 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264609 in the RIR database for the space.665 of 673

Route objects not announced

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