bgpreport

Network · data from 2026-11-12

AS271813 AS271813 - COMUNICACIONES MIGTEL C.A.

Registry name: AS271813 - COMUNICACIONES MIGTEL C.A., VE · not in PeeringDB

8IPv4 routes 100.0% RPKI valid · 37.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 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS271813, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271813, 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.
190.123.66.0/24 Valid Nonecovered by 190.123.66.0/23 669 99% 67
190.123.67.0/24 Valid Nonecovered by 190.123.66.0/23 669 99% 67
38.52.169.0/24 Valid Nonecovered by 38.52.168.0/23 665 99% 67
38.246.177.0/24 Valid Nonecovered by 38.246.176.0/23 665 99% 67
38.52.168.0/24 Valid Nonecovered by 38.52.168.0/23 664 99% 67
38.52.168.0/23 Valid RIR databaseARIN 669 99% 67
38.246.176.0/23 Valid RIR databaseARIN 669 99% 67
190.123.66.0/23 Valid RIR databaseLACNIC, RADB 669 99% 67
2803:f010::/48 Valid RIR databaseLACNIC 635 100% 67

AS-SET

AS271813 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: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none190.123.66.0/24No route object for it. A route object for 190.123.66.0/23 with origin AS271813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271813 in the RIR database for the space.669 of 673
Route object: none190.123.67.0/24No route object for it. A route object for 190.123.66.0/23 with origin AS271813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271813 in the RIR database for the space.669 of 673
Route object: none38.52.169.0/24No route object for it. A route object for 38.52.168.0/23 with origin AS271813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271813 in the RIR database for the space.665 of 673
Route object: none38.246.177.0/24No route object for it. A route object for 38.246.176.0/23 with origin AS271813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271813 in the RIR database for the space.665 of 673
Route object: none38.52.168.0/24No route object for it. A route object for 38.52.168.0/23 with origin AS271813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271813 in the RIR database for the space.664 of 673

Route objects not announced

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

2803:f010::/32LACNICValid
2803:f010:1::/48LACNICValid
2803:f010:2::/48LACNICValid

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.