Network · data from 2026-11-12
AS26523 Province of New Brunswick PNB
Registry name: PNB-TRANSIT - Province of New Brunswick, CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26523, 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.
| 216.66.0.96/27 | Invalid: origin | None | 19 3%low visibility |
| 38.64.244.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2001:470:5f5::/48 | Valid | Nonecovered by 2001:470:5f4::/47 | 633 100% |
| 162.252.132.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 162.252.132.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 162.252.134.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 162.252.135.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 2604:2f80::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 2620:0:f0::/48 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS26523: AS26523:AS-ALL. 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 (AS26523 isn't in the set, or no route object for AS26523 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.
| Name | Database | ASNs | Sets | AS26523 in it | Not covered |
|---|---|---|---|---|---|
| AS26523:AS-ALL | RADB | 4 | 2 | Yes | 1 |
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: none1
- Route object: none2
- Route object: RIR7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 216.66.0.96/27 | ROAs covering it name AS6939, not AS26523. If AS26523 should announce it, add a ROA for AS26523. |
| Route object: none | 216.66.0.96/27 | No route object for it. Add a route object with origin AS26523 in the RIR database for the space. |
| ROA: none | 38.64.244.0/24 | No ROA covers it. Add a ROA for AS26523, maxLength 24. |
| Route object: RIR | 38.64.244.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2001:470:5f5::/48 | No route object for it. A route object for 2001:470:5f4::/47 with origin AS26523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26523 in the RIR database for the space. |
| Route object: RIR | 162.252.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.252.132.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.252.134.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.252.135.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2604:2f80::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2620:0:f0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26523 whose prefix no peer sees AS26523 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:5f4::/47 | ARIN | Valid |
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.