bgpreport

Network · data from 2026-11-12

AS26610 Universidad Tecnica Federico Santa Maria

Registry name: AS26610 - Universidad Tecnica Federico Santa Maria, CL · PeeringDB

19IPv4 routes 10.5% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
18No 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 AS26610, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26610, 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.
2800:270::/32 No ROA None 633 100% 67
204.87.169.0/24 No ROA Other IRR onlyNTTCOM 669 99% 67
200.1.16.0/24 No ROA Other IRR onlyNTTCOM 667 99% 67
200.1.17.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.18.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.19.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.20.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.21.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.22.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.25.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.29.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.30.0/24 No ROA Other IRR onlyNTTCOM, RADB 667 99% 67
200.1.23.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.1.24.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.1.26.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.1.27.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.1.28.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
200.1.31.0/24 No ROA Other IRR onlyNTTCOM, RADB 666 99% 67
146.83.92.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
146.83.90.0/24 Valid RIR databaseLACNIC, NTTCOM, RADB 670 100% 68
2001:1310:3121::/48 Valid RIR databaseLACNIC, RADB 17 3%low visibility 18

AS-SET

PeeringDB's irr_as_set for AS26610: AS26610:AS-USM. 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 (AS26610 isn't in the set, or no route object for AS26610 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 objectsAS26610 in itNot covered
AS26610:AS-USM LACNIC 1121 Yes 1

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

  • ROA: none18
  • Route object: none1
  • Route object: RIR17
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2800:270::/32No ROA covers it. Add a ROA for AS26610, maxLength 32.633 of 636
Route object: none2800:270::/32No route object for it. Add a route object with origin AS26610 in the RIR database for the space.633 of 636
ROA: none204.87.169.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.669 of 673
Route object: RIR204.87.169.0/24Route object only in NTTCOM. Add it in the RIR database for the space.669 of 673
ROA: none200.1.16.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.16.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
ROA: none200.1.17.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.17.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.18.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.18.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.19.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.19.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.20.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.20.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.21.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.21.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.22.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.22.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.25.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.25.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.29.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.29.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.30.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.667 of 673
Route object: RIR200.1.30.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.1.23.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.666 of 673
Route object: RIR200.1.23.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.1.24.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.666 of 673
Route object: RIR200.1.24.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.1.26.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.666 of 673
Route object: RIR200.1.26.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.1.27.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.666 of 673
Route object: RIR200.1.27.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.1.28.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.666 of 673
Route object: RIR200.1.28.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673
ROA: none200.1.31.0/24No ROA covers it. Add a ROA for AS26610, maxLength 24.666 of 673
Route object: RIR200.1.31.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

200.1.16.0/20NTTCOM, RADBNo ROA

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.