bgpreport

Network · data from 2026-11-12

AS273244 EXPERTOS EN TECNOLOGIA Y TELECOMUNICACIONES S.A.S

Registry name: AS273244 - EXPERTOS EN TECNOLOGIA Y TELECOMUNICACIONES S.A.S, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273244, 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.
38.191.166.0/23 Valid RIR databaseARIN 673 100% 67
38.226.1.0/24 Valid RIR databaseARIN, RADB 672 100% 67
179.63.188.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
179.63.190.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
179.63.191.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
38.19.46.0/23 Valid RIR databaseARIN 671 100% 66
38.225.40.0/24 Valid RIR databaseARIN 671 100% 67
38.224.24.0/24 Valid RIR databaseARIN, RADB 670 100% 66
2803:6150::/32 Valid RIR databaseLACNIC 635 100% 68
2803:ae90::/32 Valid RIR databaseLACNIC 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS273244: AS-XPERT-TIC. 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 (AS273244 isn't in the set, or no route object for AS273244 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 objectsAS273244 in itNot covered
AS-XPERT-TIC In no IRR database read today.

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

  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: not foundAS-XPERT-TICPeeringDB names AS-XPERT-TIC; no IRR database read has it.

Route objects not announced

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

38.236.180.0/24ARINValid
161.22.32.0/24LACNICValid

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.