bgpreport

Network · data from 2026-11-12

AS17120 New Brunswick Education Network

Registry name: NBDOE-ORG - New Brunswick Department of Education and Early Childhood Development, CA · PeeringDB

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

Announced routes

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

204.81.0.0/16 Valid Other IRR onlyCANARIE, RADB 670 100% 68
204.82.0.0/16 Valid Other IRR onlyCANARIE, RADB 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS17120: RADB::AS26523:AS-CUSTOMERS. 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 (AS17120 isn't in the set, or no route object for AS17120 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 objectsAS17120 in itNot covered
RADB::AS26523:AS-CUSTOMERS RADB 3122 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 15 are in fix.csv.

  • Route object: RIR2
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: RIR204.81.0.0/16Route object only in CANARIE, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.82.0.0/16Route object only in CANARIE, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

204.81.0.0/18RADBValid
204.81.0.0/22CANARIEInvalid: maxLength
204.81.4.0/22CANARIEInvalid: maxLength
204.81.8.0/21CANARIEInvalid: maxLength
204.81.16.0/20CANARIEInvalid: maxLength
204.81.32.0/19CANARIEInvalid: maxLength
204.81.64.0/18CANARIE, RADBValid
204.81.128.0/18CANARIE, RADBValid
204.81.192.0/18CANARIE, RADBValid
204.82.0.0/18CANARIE, RADBValid
204.82.64.0/18CANARIE, RADBValid
204.82.128.0/18CANARIE, RADBValid
204.82.192.0/18CANARIE, RADBValid

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.