bgpreport

Network · data from 2026-11-12

AS262253 ECONOCABLE MEDIA S.A.C.

Registry name: AS262253 - ECONOCABLE MEDIA SAC, PE · PeeringDB

38IPv4 routes 92.1% RPKI valid · 92.1% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS262253, seen from no peer

Announced routes

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

209.45.51.0/24 No ROA Other origin only 672 100% 67
209.45.95.0/24 No ROA Other origin only 672 100% 67
200.1.182.0/24 No ROA Other origin only 670 100% 67
2803:5940::/32 No ROA None 636 100% 67
167.250.204.0/24 Valid RIR databaseLACNIC 673 100% 67
167.250.205.0/24 Valid RIR databaseLACNIC 673 100% 67
167.250.206.0/24 Valid RIR databaseLACNIC 673 100% 67
167.250.207.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.227.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.245.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.246.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.247.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.248.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.249.0/24 Valid RIR databaseLACNIC 673 100% 67
181.224.225.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.226.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.228.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.229.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.231.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.235.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.236.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.237.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.238.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.239.0/24 Valid RIR databaseALTDB, LACNIC 672 100% 67
181.224.240.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.241.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.242.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.243.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.244.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.250.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.251.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.252.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.253.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.254.0/24 Valid RIR databaseLACNIC 672 100% 67
181.224.255.0/24 Valid RIR databaseLACNIC 672 100% 67
167.250.204.0/22 Valid RIR databaseLACNIC 671 100% 67
181.224.224.0/19 Valid RIR databaseLACNIC 671 100% 67
181.224.232.0/24 Valid RIR databaseLACNIC 671 100% 67
200.11.63.0/24 Valid RIR databaseLACNIC 671 100% 67
2803:2500::/32 Valid RIR databaseLACNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS262253: AS262253. 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 (AS262253 isn't in the set, or no route object for AS262253 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 objectsAS262253 in itNot covered
AS262253 A single AS number, not a set: AS262253 (this network), 49 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 21 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none209.45.51.0/24No ROA covers it. Add a ROA for AS262253, maxLength 24.672 of 673
Route object: none209.45.51.0/24Route objects for it name AS3132. Add a route object with origin AS262253 in the RIR database for the space.672 of 673
ROA: none209.45.95.0/24No ROA covers it. Add a ROA for AS262253, maxLength 24.672 of 673
Route object: none209.45.95.0/24Route objects for it name AS3132. Add a route object with origin AS262253 in the RIR database for the space.672 of 673
ROA: none200.1.182.0/24No ROA covers it. Add a ROA for AS262253, maxLength 24.670 of 673
Route object: none200.1.182.0/24Route objects for it name AS3132. Add a route object with origin AS262253 in the RIR database for the space.670 of 673
ROA: none2803:5940::/32No ROA covers it. Add a ROA for AS262253, maxLength 32.636 of 636
Route object: none2803:5940::/32No route object for it. Add a route object with origin AS262253 in the RIR database for the space.636 of 636

Route objects not announced

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

38.43.128.0/19ARINValid
38.187.0.0/19ARINValid
164.163.184.0/23LACNICValid
170.246.56.0/22LACNICValid
200.1.177.0/24RADBNo ROA
200.1.179.0/24RADBNo ROA
209.45.56.0/24RADBNo ROA
209.45.57.0/24RADBNo ROA
209.45.58.0/24RADBNo ROA
209.45.94.0/24RADBNo ROA
209.45.102.0/24RADBNo ROA
209.45.103.0/24RADBNo ROA
209.61.64.0/18ARINValid

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.