Network · data from 2026-11-12
AS20194 BEARTECH - Bear Technologies Corporation
Registry name: BEARTECH - Bear Technologies Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20194, 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.11.40.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.41.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.42.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.43.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.44.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.45.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.46.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 204.11.47.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
AS-SET
AS20194 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 15 are in fix.csv.
- Route object: RIR8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 204.11.40.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.41.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.42.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.43.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.44.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.45.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.46.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.11.47.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20194 whose prefix no peer sees AS20194 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.112.191.0/24 | RADB | No ROA |
| 66.226.198.0/24 | RADB | No ROA |
| 67.122.164.0/24 | RADB | No ROA |
| 67.133.165.0/24 | RADB | No ROA |
| 67.218.220.0/23 | NTTCOM, RADB | No ROA |
| 204.11.40.0/21 | ARIN, RADB | No ROA |
| 208.243.49.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.