bgpreport

Network · data from 2026-11-12

AS270037 ComWiFi

Registry name: AS270037 - COMWIFI TELECOMUNICACIONES E.I.R.L, PE · PeeringDB

6IPv4 routes 100.0% RPKI valid · 16.7% with a route object
10IPv6 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
0Route objects not announced registered with origin AS270037, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270037, 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.

191.52.212.0/23 Valid Nonecovered by 191.52.212.0/22 672 100% 67
191.52.214.0/23 Valid Nonecovered by 191.52.212.0/22 672 100% 66
191.52.215.0/24 Valid Nonecovered by 191.52.212.0/22 672 100% 67
191.52.212.0/24 Valid Nonecovered by 191.52.212.0/22 671 100% 66
191.52.214.0/24 Valid Nonecovered by 191.52.212.0/22 671 100% 66
191.52.212.0/22 Valid RIR databaseLACNIC, RADB 672 100% 67
2803:15e0::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:100::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:200::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:300::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:400::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:500::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:600::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:700::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:800::/40 Valid RIR databaseLACNIC 636 100% 67
2803:15e0:900::/40 Valid RIR databaseLACNIC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS270037: AS270037. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS270037 isn't in the set, or no route object for AS270037 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS270037 in itNot covered
AS270037 A single AS number, not a set: AS270037 (this network), 11 route objects.

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

  • Route object: none5
ChangePrefix or setDetailFull-table peers
Route object: none191.52.212.0/23No route object for it. A route object for 191.52.212.0/22 with origin AS270037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270037 in the RIR database for the space.672 of 673
Route object: none191.52.214.0/23No route object for it. A route object for 191.52.212.0/22 with origin AS270037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270037 in the RIR database for the space.672 of 673
Route object: none191.52.215.0/24No route object for it. A route object for 191.52.212.0/22 with origin AS270037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270037 in the RIR database for the space.672 of 673
Route object: none191.52.212.0/24No route object for it. A route object for 191.52.212.0/22 with origin AS270037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270037 in the RIR database for the space.671 of 673
Route object: none191.52.214.0/24No route object for it. A route object for 191.52.212.0/22 with origin AS270037 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270037 in the RIR database for the space.671 of 673

Route objects not announced

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