bgpreport

Network · data from 2026-11-12

AS262216 TELCONET S A

Registry name: AS262216 - TELCONET S A, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262216, 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.
2803:5a00:4000::/48 Invalid: maxLength Nonecovered by 2803:5a00::/32 8 1%low visibility 6
190.60.175.0/24 Valid Other IRR onlyRADB 671 100% 66
200.80.8.0/24 Valid Other IRR onlyRADB 671 100% 66
200.80.9.0/24 Valid Other IRR onlyRADB 671 100% 66
200.80.22.0/24 Valid Other IRR onlyRADB 671 100% 66
200.80.23.0/24 Valid Other IRR onlyRADB 671 100% 66
138.0.104.0/22 Valid RIR databaseLACNIC, RADB 672 100% 66
177.184.91.0/24 Valid RIR databaseLACNIC 672 100% 66
190.113.224.0/21 Valid RIR databaseLACNIC, RADB 671 100% 66
138.0.104.0/24 Valid RIR databaseLACNIC 668 99% 67
138.0.105.0/24 Valid RIR databaseLACNIC 668 99% 67
138.0.106.0/24 Valid RIR databaseLACNIC 668 99% 67
138.0.107.0/24 Valid RIR databaseLACNIC 668 99% 67
190.113.224.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.225.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.226.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.227.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.228.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.229.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.230.0/24 Valid RIR databaseLACNIC 667 99% 67
190.113.231.0/24 Valid RIR databaseLACNIC 667 99% 67
2803:5a00::/32 Valid RIR databaseLACNIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS262216: AS262216:AS-PEERS. 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 (AS262216 isn't in the set, or no route object for AS262216 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 objectsAS262216 in itNot covered
AS262216:AS-PEERS LACNIC 1122 Yes 0

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.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2803:5a00:4000::/48ROA 2803:5a00::/32 AS262216 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2803:5a00:4000::/48.8 of 636
Route object: none2803:5a00:4000::/48No route object for it. A route object for 2803:5a00::/32 with origin AS262216 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262216 in the RIR database for the space.8 of 636
Route object: RIR190.60.175.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.8.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.9.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.22.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.23.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

190.210.106.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.