bgpreport

Network · data from 2026-11-12

AS396472 Swift Internet

Registry name: SWIFTINTERNET - TELUS Communications Inc., CA · PeeringDB

6IPv4 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
7No 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 AS396472, seen from no peer

Announced routes

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

23.190.128.0/24 No ROA Other IRR onlyRADB 671 100% 68
104.193.104.0/24 No ROA Other IRR onlyRADB 671 100% 68
104.193.105.0/24 No ROA Other IRR onlyRADB 671 100% 68
104.193.106.0/24 No ROA Other IRR onlyRADB 671 100% 68
104.243.223.0/24 No ROA Other IRR onlyRADB 671 100% 68
192.81.55.0/24 No ROA Other IRR onlyRADB 671 100% 68
2604:4f40::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS396472: ARIN::AS396472:AS-ALL. 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 (AS396472 isn't in the set, or no route object for AS396472 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 objectsAS396472 in itNot covered
ARIN::AS396472:AS-ALL 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 15 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none23.190.128.0/24No ROA covers it. Add a ROA for AS396472, maxLength 24.671 of 673
Route object: RIR23.190.128.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.193.104.0/24No ROA covers it. Add a ROA for AS396472, maxLength 24.671 of 673
Route object: RIR104.193.104.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.193.105.0/24No ROA covers it. Add a ROA for AS396472, maxLength 24.671 of 673
Route object: RIR104.193.105.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.193.106.0/24No ROA covers it. Add a ROA for AS396472, maxLength 24.671 of 673
Route object: RIR104.193.106.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.243.223.0/24No ROA covers it. Add a ROA for AS396472, maxLength 24.671 of 673
Route object: RIR104.243.223.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.81.55.0/24No ROA covers it. Add a ROA for AS396472, maxLength 24.671 of 673
Route object: RIR192.81.55.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2604:4f40::/32No ROA covers it. Add a ROA for AS396472, maxLength 32.634 of 636
Route object: RIR2604:4f40::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
AS-SET: not foundARIN::AS396472:AS-ALLPeeringDB names ARIN::AS396472:AS-ALL; no IRR database read has it.

Route objects not announced

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