bgpreport

Network · data from 2026-11-12

AS14602 Teliax, Inc

Registry name: TELIAX - Teliax, Inc., US · PeeringDB

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

Announced routes

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

8.3.252.0/24 No ROA Other IRR onlyRADB 671 100% 67
8.14.120.0/24 No ROA Other IRR onlyRADB 671 100% 67
8.17.37.0/24 No ROA Other IRR onlyRADB 671 100% 67
8.20.212.0/24 No ROA Other IRR onlyRADB 671 100% 67
8.22.84.0/22 No ROA Other IRR onlyRADB 671 100% 67
8.28.85.0/24 No ROA Other IRR onlyRADB 671 100% 67
63.211.239.0/24 No ROA Other IRR onlyRADB 671 100% 67
2604:bb80::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS14602: RADB::AS-TELIAX. 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 (AS14602 isn't in the set, or no route object for AS14602 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 objectsAS14602 in itNot covered
RADB::AS-TELIAX RADBlists itself further down 2210 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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none8.3.252.0/24No ROA covers it. Add a ROA for AS14602, maxLength 24.671 of 673
Route object: RIR8.3.252.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none8.14.120.0/24No ROA covers it. Add a ROA for AS14602, maxLength 24.671 of 673
Route object: RIR8.14.120.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none8.17.37.0/24No ROA covers it. Add a ROA for AS14602, maxLength 24.671 of 673
Route object: RIR8.17.37.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none8.20.212.0/24No ROA covers it. Add a ROA for AS14602, maxLength 24.671 of 673
Route object: RIR8.20.212.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none8.22.84.0/22No ROA covers it. Add a ROA for AS14602, maxLength 22.671 of 673
Route object: RIR8.22.84.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none8.28.85.0/24No ROA covers it. Add a ROA for AS14602, maxLength 24.671 of 673
Route object: RIR8.28.85.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none63.211.239.0/24No ROA covers it. Add a ROA for AS14602, maxLength 24.671 of 673
Route object: RIR63.211.239.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2604:bb80::/32No ROA covers it. Add a ROA for AS14602, maxLength 32.636 of 636
Route object: RIR2604:bb80::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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