bgpreport

Network · data from 2026-11-12

AS40788 Start.ca

Registry name: MULTIB-40788 - Start Communications, CA · PeeringDB

32IPv4 routes 96.9% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS40788, seen from no peer

Announced routes

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

192.68.188.0/24 No ROA RIR databaseARIN 671 100% 67
23.92.128.0/20 Valid RIR databaseARIN 673 100% 67
24.50.160.0/19 Valid RIR databaseARIN 673 100% 67
24.53.96.0/19 Valid RIR databaseARIN 673 100% 67
24.53.240.0/20 Valid RIR databaseARIN 673 100% 67
24.54.64.0/19 Valid RIR databaseARIN 673 100% 67
24.140.240.0/20 Valid RIR databaseARIN 673 100% 67
24.143.128.0/19 Valid RIR databaseARIN 673 100% 67
24.156.176.0/20 Valid RIR databaseARIN 673 100% 67
45.3.0.0/19 Valid RIR databaseARIN 673 100% 67
45.40.64.0/20 Valid RIR databaseARIN 673 100% 67
45.74.96.0/19 Valid RIR databaseARIN 673 100% 67
64.140.112.0/20 Valid RIR databaseARIN 673 100% 67
96.46.192.0/20 Valid RIR databaseARIN 673 100% 67
104.193.56.0/21 Valid RIR databaseARIN 673 100% 67
104.193.64.0/21 Valid RIR databaseARIN 673 100% 67
104.243.80.0/20 Valid RIR databaseARIN 673 100% 67
142.90.0.0/18 Valid RIR databaseARIN 673 100% 67
162.247.224.0/21 Valid RIR databaseARIN 673 100% 67
172.87.80.0/20 Valid RIR databaseARIN 673 100% 67
173.247.128.0/19 Valid RIR databaseARIN 673 100% 67
184.171.208.0/20 Valid RIR databaseARIN 673 100% 67
198.2.64.0/18 Valid RIR databaseARIN 673 100% 67
216.212.192.0/19 Valid RIR databaseARIN 673 100% 67
23.182.0.0/24 Valid RIR databaseARIN 671 100% 67
104.153.24.0/22 Valid RIR databaseARIN 671 100% 67
162.250.196.0/22 Valid RIR databaseARIN 671 100% 67
162.255.112.0/22 Valid RIR databaseARIN 671 100% 67
192.64.8.0/22 Valid RIR databaseARIN 671 100% 67
96.47.176.0/20 Valid RIR databaseARIN 670 100% 67
108.168.0.0/17 Valid RIR databaseARIN 670 100% 67
108.170.128.0/18 Valid RIR databaseARIN 670 100% 67
2600:1600::/24 Valid RIR databaseARIN 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS40788: AS-START-CA. 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 (AS40788 isn't in the set, or no route object for AS40788 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 objectsAS40788 in itNot covered
AS-START-CA ARIN 51194 Yes 0

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

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none192.68.188.0/24No ROA covers it. Add a ROA for AS40788, maxLength 24.671 of 673

Route objects not announced

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