Network · data from 2026-11-12
AS398999 Sucura Networks
Registry name: BOREAL-TELECOM - Sucura Networks Inc, CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398999, 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.
| 23.138.20.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 2602:fb41::/40 | Valid | Nonecovered by 2602:fb41::/36 | 3 0%low visibility |
| 2602:fb41:f00::/48 | Valid | Nonecovered by 2602:fb41::/36 | 3 0%low visibility |
| 23.132.148.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 172.98.29.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 142.248.29.0/24 | Valid | RIR databaseARIN | 672 100% |
| 142.248.30.0/24 | Valid | RIR databaseARIN | 672 100% |
| 2602:fb41::/36 | Valid | RIR databaseARIN, RADB | 635 100% |
| 142.248.28.0/22 | Valid | RIR databaseARIN, RADB | 2 0%low visibility |
| 142.248.31.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS398999: AS-BOREAL. 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 (AS398999 isn't in the set, or no route object for AS398999 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 | AS398999 in it | Not covered |
|---|---|---|---|---|---|
| AS-BOREAL | ARINlists itself further down7 member sets in no database: AS-6186, AS-FALIX, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL … | 888 | 100 | 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 13 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: RIR1
- AS-SET: missing member7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.138.20.0/24 | No ROA covers it. Add a ROA for AS398999, maxLength 24. |
| Route object: RIR | 23.138.20.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2602:fb41::/40 | No route object for it. A route object for 2602:fb41::/36 with origin AS398999 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398999 in the RIR database for the space. |
| Route object: none | 2602:fb41:f00::/48 | No route object for it. A route object for 2602:fb41::/36 with origin AS398999 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398999 in the RIR database for the space. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS-FALIX; no IRR database read has it. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS150249:AS-ATHARVA; no IRR database read has it. |
| AS-SET: missing member | AS-BOREAL | AS-BOREAL (ARIN) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS398999 whose prefix no peer sees AS398999 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 142.248.28.0/24 | ARIN | Valid |
| 2604:d60::/32 | RADB | No ROA |
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.