bgpreport

Network · data from 2026-11-12

AS214623 2644819 Ontario Inc

Registry name: ON2644819-NET 2644819 Ontario Inc, CA · PeeringDB

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

Announced routes

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

149.13.64.0/24 No ROA Other origin only 673 100% 67
154.3.47.0/24 No ROA None 673 100% 67
154.17.253.0/24 No ROA None 673 100% 67
205.237.92.0/24 Valid Nonecovered by 205.237.92.0/23 673 100% 67
205.237.94.0/24 Valid Nonecovered by 205.237.94.0/23 673 100% 67
108.165.21.0/24 Valid RIR databaseARIN, RADB 673 100% 67
110.172.149.0/24 Valid RIR databaseARIN 673 100% 67
185.218.23.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.222.106.0/24 Valid RIR databaseRIPE 673 100% 67
199.244.103.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS214623: RIPE::AS214623:AS-GLOBAL. 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 (AS214623 isn't in the set, or no route object for AS214623 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 objectsAS214623 in itNot covered
RIPE::AS214623:AS-GLOBAL RIPE 118 Yes 3

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

  • ROA: none3
  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none149.13.64.0/24No ROA covers it. Add a ROA for AS214623, maxLength 24.673 of 673
Route object: none149.13.64.0/24Route objects for it name AS17330. Add a route object with origin AS214623 in the RIR database for the space.673 of 673
ROA: none154.3.47.0/24No ROA covers it. Add a ROA for AS214623, maxLength 24.673 of 673
Route object: none154.3.47.0/24No route object for it. Add a route object with origin AS214623 in the RIR database for the space.673 of 673
ROA: none154.17.253.0/24No ROA covers it. Add a ROA for AS214623, maxLength 24.673 of 673
Route object: none154.17.253.0/24No route object for it. Add a route object with origin AS214623 in the RIR database for the space.673 of 673
Route object: none205.237.92.0/24No route object for it. A route object for 205.237.92.0/23 with origin AS214623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214623 in the RIR database for the space.673 of 673
Route object: none205.237.94.0/24No route object for it. A route object for 205.237.94.0/23 with origin AS214623 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214623 in the RIR database for the space.673 of 673

Route objects not announced

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

205.237.92.0/23RADB, RIPEValid
205.237.94.0/23RADB, RIPEValid
2a13:9500:6c::/48RIPEValid

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.