bgpreport

Network · data from 2026-11-12

AS55053 2267921 ONTARIO

Registry name: RACK-AND-DATA - 2267921 ONTARIO LTD, CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55053, 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.
162.219.0.0/21 No ROA Other IRR onlyRADB 673 100% 67
66.159.108.0/22 No ROA Other IRR onlyRADB 671 100% 67
74.116.120.0/22 No ROA Other IRR onlyRADB 671 100% 67
199.127.108.0/24 No ROA Other IRR onlyRADB 671 100% 67
206.126.94.0/24 No ROA Other IRR onlyRADB 671 100% 67
130.12.176.0/22 No ROA Other IRR onlyRADB 667 99% 67
198.96.0.0/24 No ROA Other IRR onlyRADB 667 99% 67
208.92.49.0/24 No ROA Other IRR onlyRADB 667 99% 67
208.92.50.0/24 No ROA Other IRR onlyRADB 667 99% 67

AS-SET

AS55053'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 26 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none162.219.0.0/21No ROA covers it. Add a ROA for AS55053, maxLength 21.673 of 673
Route object: RIR162.219.0.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none66.159.108.0/22No ROA covers it. Add a ROA for AS55053, maxLength 22.671 of 673
Route object: RIR66.159.108.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none74.116.120.0/22No ROA covers it. Add a ROA for AS55053, maxLength 22.671 of 673
Route object: RIR74.116.120.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.127.108.0/24No ROA covers it. Add a ROA for AS55053, maxLength 24.671 of 673
Route object: RIR199.127.108.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none206.126.94.0/24No ROA covers it. Add a ROA for AS55053, maxLength 24.671 of 673
Route object: RIR206.126.94.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none130.12.176.0/22No ROA covers it. Add a ROA for AS55053, maxLength 22.667 of 673
Route object: RIR130.12.176.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none198.96.0.0/24No ROA covers it. Add a ROA for AS55053, maxLength 24.667 of 673
Route object: RIR198.96.0.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none208.92.49.0/24No ROA covers it. Add a ROA for AS55053, maxLength 24.667 of 673
Route object: RIR208.92.49.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none208.92.50.0/24No ROA covers it. Add a ROA for AS55053, maxLength 24.667 of 673
Route object: RIR208.92.50.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

64.137.128.0/17RADBNo ROA
104.167.122.0/24RADBNo ROA
130.12.110.0/24RADBNo ROA
168.235.157.0/24RADBNo ROA
168.235.158.0/23RADBNo ROA
170.39.48.0/24RADBNo ROA
198.52.161.0/24RADBNo ROA
2602:f816::/32RADBNo 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.