bgpreport

Network · data from 2026-11-12

AS267749 INVERSIONES TELCOTEL SAC

Registry name: AS267749 - INVERSIONES TELCOTEL SAC, PE · PeeringDB

11IPv4 routes 100.0% RPKI valid · 45.5% 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
2Route objects not announced registered with origin AS267749, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267749, 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.192.0/24 Valid Nonecovered by 45.232.192.0/22 669 99% 67
45.232.193.0/24 Valid Nonecovered by 45.232.192.0/22 669 99% 67
45.232.194.0/24 Valid Nonecovered by 45.232.192.0/22 669 99% 67
45.232.195.0/24 Valid Nonecovered by 45.232.192.0/22 669 99% 67
38.9.38.0/24 Valid Nonecovered by 38.9.38.0/23 668 99% 67
38.9.39.0/24 Valid Nonecovered by 38.9.38.0/23 668 99% 67
181.224.224.0/24 Valid RIR databaseLACNIC 670 100% 67
181.224.230.0/24 Valid RIR databaseLACNIC 669 99% 67
181.224.233.0/24 Valid RIR databaseLACNIC 669 99% 67
38.137.206.0/24 Valid RIR databaseARIN, RADB 668 99% 67
181.224.234.0/24 Valid RIR databaseLACNIC 668 99% 67
2803:6720::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

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

  • Route object: none6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none45.232.192.0/24No route object for it. A route object for 45.232.192.0/22 with origin AS267749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267749 in the RIR database for the space.669 of 673
Route object: none45.232.193.0/24No route object for it. A route object for 45.232.192.0/22 with origin AS267749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267749 in the RIR database for the space.669 of 673
Route object: none45.232.194.0/24No route object for it. A route object for 45.232.192.0/22 with origin AS267749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267749 in the RIR database for the space.669 of 673
Route object: none45.232.195.0/24No route object for it. A route object for 45.232.192.0/22 with origin AS267749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267749 in the RIR database for the space.669 of 673
Route object: none38.9.38.0/24No route object for it. A route object for 38.9.38.0/23 with origin AS267749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267749 in the RIR database for the space.668 of 673
Route object: none38.9.39.0/24No route object for it. A route object for 38.9.38.0/23 with origin AS267749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267749 in the RIR database for the space.668 of 673

Route objects not announced

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

38.9.38.0/23ARINValid
45.232.192.0/22LACNICValid

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.