bgpreport

Network · data from 2026-11-12

AS393994 BRRD-AS - Brantford Hydro

Registry name: BRRD-AS - Brantford Hydro, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393994, 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.201.56.0/23 Invalid: origin None 131 19% 51
2606:2580::/32 No ROA Other origin only 635 100% 69
192.189.204.0/24 No ROA Other IRR onlyRADB 671 100% 68
206.130.176.0/24 No ROA Other IRR onlyRADB 671 100% 68
66.207.112.0/24 Valid Nonecovered by 66.207.112.0/22 671 100% 68
66.207.113.0/24 Valid Nonecovered by 66.207.112.0/22 671 100% 68
66.207.114.0/24 Valid Nonecovered by 66.207.112.0/22 671 100% 68
66.207.116.0/24 Valid Nonecovered by 66.207.116.0/23 671 100% 68
66.207.112.0/22 Valid RIR databaseARIN, RADB 671 100% 68
66.207.116.0/23 Valid RIR databaseARIN, RADB 671 100% 68
216.185.74.0/23 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

AS393994 isn't in PeeringDB, where networks name their 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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none3
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: origin64.201.56.0/23ROAs covering it name AS812, not AS393994. If AS393994 should announce it, add a ROA for AS393994.131 of 673
Route object: none64.201.56.0/23No route object for it. Add a route object with origin AS393994 in the RIR database for the space.131 of 673
ROA: none2606:2580::/32No ROA covers it. Add a ROA for AS393994, maxLength 32.635 of 636
Route object: none2606:2580::/32Route objects for it name AS53486. Add a route object with origin AS393994 in the RIR database for the space.635 of 636
ROA: none192.189.204.0/24No ROA covers it. Add a ROA for AS393994, maxLength 24.671 of 673
Route object: RIR192.189.204.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none206.130.176.0/24No ROA covers it. Add a ROA for AS393994, maxLength 24.671 of 673
Route object: RIR206.130.176.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none66.207.112.0/24No route object for it. A route object for 66.207.112.0/22 with origin AS393994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393994 in the RIR database for the space.671 of 673
Route object: none66.207.113.0/24No route object for it. A route object for 66.207.112.0/22 with origin AS393994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393994 in the RIR database for the space.671 of 673
Route object: none66.207.114.0/24No route object for it. A route object for 66.207.112.0/22 with origin AS393994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393994 in the RIR database for the space.671 of 673
Route object: none66.207.116.0/24No route object for it. A route object for 66.207.116.0/23 with origin AS393994 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393994 in the RIR database for the space.671 of 673

Route objects not announced

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