bgpreport

Network · data from 2026-11-12

AS21548 Aptum Fibre (Montreal)

Registry name: MTO - Beanfield Technologies Inc., CA · PeeringDB

9IPv4 routes 0.0% RPKI valid · 77.8% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
38Route objects not announced registered with origin AS21548, seen from no peer

Announced routes

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

64.18.68.0/24 No ROA Nonecovered by 64.18.64.0/19 673 100% 67
64.18.85.0/24 No ROA Nonecovered by 64.18.64.0/19 673 100% 67
2001:598:1300::/48 No ROA Nonecovered by 2001:598::/32 636 100% 67
67.22.224.0/20 No ROA Other IRR onlyALTDB, RADB 673 100% 67
204.9.80.0/22 No ROA Other IRR onlyALTDB, RADB 673 100% 67
209.47.172.0/24 No ROA Other IRR onlyALTDB, RADB 673 100% 67
2001:598::/32 No ROA Other IRR onlyALTDB 636 100% 67
64.18.64.0/19 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 67
64.254.224.0/19 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 67
66.11.32.0/20 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 67
206.55.80.0/20 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 67

AS-SET

AS21548'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 56 are in fix.csv.

  • ROA: none11
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced38
ChangePrefix or setDetailFull-table peers
ROA: none64.18.68.0/24No ROA covers it. Add a ROA for AS21548, maxLength 24.673 of 673
Route object: none64.18.68.0/24No route object for it. A route object for 64.18.64.0/19 with origin AS21548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21548 in the RIR database for the space.673 of 673
ROA: none64.18.85.0/24No ROA covers it. Add a ROA for AS21548, maxLength 24.673 of 673
Route object: none64.18.85.0/24No route object for it. A route object for 64.18.64.0/19 with origin AS21548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21548 in the RIR database for the space.673 of 673
ROA: none2001:598:1300::/48No ROA covers it. Add a ROA for AS21548, maxLength 48.636 of 636
Route object: none2001:598:1300::/48No route object for it. A route object for 2001:598::/32 with origin AS21548 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21548 in the RIR database for the space.636 of 636
ROA: none67.22.224.0/20No ROA covers it. Add a ROA for AS21548, maxLength 20.673 of 673
Route object: RIR67.22.224.0/20Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.9.80.0/22No ROA covers it. Add a ROA for AS21548, maxLength 22.673 of 673
Route object: RIR204.9.80.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.47.172.0/24No ROA covers it. Add a ROA for AS21548, maxLength 24.673 of 673
Route object: RIR209.47.172.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none2001:598::/32No ROA covers it. Add a ROA for AS21548, maxLength 32.636 of 636
Route object: RIR2001:598::/32Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
ROA: none64.18.64.0/19No ROA covers it. Add a ROA for AS21548, maxLength 19.673 of 673
ROA: none64.254.224.0/19No ROA covers it. Add a ROA for AS21548, maxLength 19.673 of 673
ROA: none66.11.32.0/20No ROA covers it. Add a ROA for AS21548, maxLength 20.673 of 673
ROA: none206.55.80.0/20No ROA covers it. Add a ROA for AS21548, maxLength 20.673 of 673

Route objects not announced

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

64.18.69.0/24ALTDBNo ROA
64.254.234.0/24ALTDBNo ROA
65.111.144.0/20ALTDBNo ROA
65.111.152.0/24RADBNo ROA
69.28.200.0/24ALTDBNo ROA
158.106.122.0/24ALTDBNo ROA
198.140.134.0/24ALTDB, RADBNo ROA
198.168.207.0/24ALTDB, RADBNo ROA
198.168.229.0/24ALTDBNo ROA
198.168.232.0/24ALTDBNo ROA
198.235.57.0/24ALTDB, RADBNo ROA
198.235.58.0/23ALTDBNo ROA
199.84.174.0/24ALTDBNo ROA
199.84.175.0/24ALTDBNo ROA
204.19.138.0/24ALTDBNo ROA
204.19.231.0/24ALTDB, RADBNo ROA
204.27.52.0/22ALTDBNo ROA
205.151.103.0/24ALTDBNo ROA
205.151.122.0/23ALTDBNo ROA
205.151.127.0/24ALTDBNo ROA
205.205.151.0/24ALTDBNo ROA
205.237.30.0/24ALTDBNo ROA
205.237.31.0/24ALTDBNo ROA
205.237.32.0/24ALTDBNo ROA
205.237.33.0/24ALTDBNo ROA
205.237.34.0/24ALTDB, RADBNo ROA
206.123.26.0/23ALTDBNo ROA
206.223.224.0/19ALTDBNo ROA
207.139.174.0/24ALTDBNo ROA
208.65.60.0/22ALTDBNo ROA
208.66.68.0/22ALTDBNo ROA
208.75.188.0/22ALTDBNo ROA
208.92.196.0/22ALTDBNo ROA
209.167.2.0/24ALTDBNo ROA
209.167.68.0/24ALTDBNo ROA
216.94.112.0/24ALTDBNo ROA
216.94.179.0/24ALTDBNo ROA
216.94.180.0/24ALTDBNo 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.