bgpreport

Network · data from 2026-11-12

AS18214 Telus International

Registry name: TELUS-INTERNATIONAL - TELUS INTERNATIONAL, PH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18214, 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.
203.153.12.0/23 No ROA Other IRR onlyRADB 671 100% 67
203.153.13.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
203.153.8.0/24 No ROA RIR databaseAPNIC, NTTCOM 670 100% 67
103.158.33.0/24 Valid RIR databaseAPNIC 673 100% 67
184.104.201.0/24 Valid RIR databaseARIN 673 100% 70
198.59.156.0/24 Valid RIR databaseARIN 673 100% 70
198.59.157.0/24 Valid RIR databaseARIN 673 100% 67
198.59.158.0/24 Valid RIR databaseARIN 673 100% 70
198.59.159.0/24 Valid RIR databaseARIN 673 100% 67
203.153.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
203.153.14.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69

AS-SET

AS18214's PeeringDB record names no AS-SET.

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

  • ROA: none3
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none203.153.12.0/23No ROA covers it. Add a ROA for AS18214, maxLength 23.671 of 673
Route object: RIR203.153.12.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.153.13.0/24No ROA covers it. Add a ROA for AS18214, maxLength 24.671 of 673
ROA: none203.153.8.0/24No ROA covers it. Add a ROA for AS18214, maxLength 24.670 of 673

Route objects not announced

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

64.14.194.0/24NTTCOM, RADBNo ROA
65.19.186.0/24ARINValid
80.95.17.0/24RIPEValid
80.95.18.0/24RIPEInvalid: origin
103.158.32.0/24APNICNo ROA
198.59.156.0/22ARINValid
203.153.8.0/21NTTCOM, RADBNo ROA
203.153.9.0/24APNIC, NTTCOMValid
203.153.11.0/24NTTCOMNo ROA
203.153.12.0/24APNIC, NTTCOMNo ROA
203.153.15.0/24NTTCOMNo ROA
208.181.136.0/24RADBValid
208.181.137.0/24RADBValid
209.29.241.0/24RADBValid

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.