Network · data from 2026-11-12
AS26769 BandCon
Registry name: NC-1197-26769 - NetO Corp, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26769, 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.183.242.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 193.31.60.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS26769: AS-BANDCON. 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 (AS26769 isn't in the set, or no route object for AS26769 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 | AS26769 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-BANDCON | In no IRR database read today. | |||||
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 11 are in fix.csv.
- ROA: origin2
- Route object: none2
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 216.183.242.0/24 | ROAs covering it name AS834, AS21769, not AS26769. If AS26769 should announce it, add a ROA for AS26769. |
| Route object: none | 216.183.242.0/24 | Route objects for it name AS834. Add a route object with origin AS26769 in the RIR database for the space. |
| ROA: origin | 193.31.60.0/24 | ROAs covering it name AS834, not AS26769. If AS26769 should announce it, add a ROA for AS26769. |
| Route object: none | 193.31.60.0/24 | Route objects for it name AS834. Add a route object with origin AS26769 in the RIR database for the space. |
| AS-SET: not found | AS-BANDCON | PeeringDB names AS-BANDCON; no IRR database read has it. |
Route objects not announced
Route objects with origin AS26769 whose prefix no peer sees AS26769 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.86.184.0/21 | ALTDB | No ROA |
| 38.86.184.0/22 | ALTDB | No ROA |
| 38.86.188.0/24 | ALTDB | No ROA |
| 38.93.140.0/22 | ALTDB | No ROA |
| 140.150.225.0/24 | RIPE | Invalid: origin |
| 209.101.136.0/24 | 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.