Network · data from 2026-11-12
AS33346 MONSTERBROADBAND - Point Broadband Fiber Holding, LLC
Registry name: MONSTERBROADBAND - Point Broadband Fiber Holding, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33346, 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.
| 67.32.34.0/24 | Invalid: origin | None | 2 0%low visibility |
| 192.169.72.0/21 | No ROA | Other origin only | 671 100% |
| 162.252.64.0/22 | No ROA | Other origin only | 670 100% |
| 2602:ff88::/36 | No ROA | Other origin only | 634 100% |
| 163.123.164.0/22 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 192.209.17.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 66.180.44.0/23 | Valid | RIR databaseARIN | 670 100% |
| 67.210.252.0/24 | Valid | RIR databaseARIN | 670 100% |
| 162.254.211.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 66.212.51.0/24 | Valid | RIR databaseARIN, NTTCOM | 669 99% |
AS-SET
AS33346 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 24 are in fix.csv.
- ROA: origin1
- ROA: none5
- Route object: none4
- Route object: RIR2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 67.32.34.0/24 | ROAs covering it name AS6389, not AS33346. If AS33346 should announce it, add a ROA for AS33346. |
| Route object: none | 67.32.34.0/24 | No route object for it. Add a route object with origin AS33346 in the RIR database for the space. |
| ROA: none | 192.169.72.0/21 | No ROA covers it. Add a ROA for AS33346, maxLength 21. |
| Route object: none | 192.169.72.0/21 | Route objects for it name AS7029, AS7819, AS30676. Add a route object with origin AS33346 in the RIR database for the space. |
| ROA: none | 162.252.64.0/22 | No ROA covers it. Add a ROA for AS33346, maxLength 22. |
| Route object: none | 162.252.64.0/22 | Route objects for it name AS7819. Add a route object with origin AS33346 in the RIR database for the space. |
| ROA: none | 2602:ff88::/36 | No ROA covers it. Add a ROA for AS33346, maxLength 36. |
| Route object: none | 2602:ff88::/36 | Route objects for it name AS7819. Add a route object with origin AS33346 in the RIR database for the space. |
| ROA: none | 163.123.164.0/22 | No ROA covers it. Add a ROA for AS33346, maxLength 22. |
| Route object: RIR | 163.123.164.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 192.209.17.0/24 | No ROA covers it. Add a ROA for AS33346, maxLength 24. |
| Route object: RIR | 192.209.17.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS33346 whose prefix no peer sees AS33346 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.252.65.0/24 | RADB | No ROA |
| 162.252.66.0/23 | RADB | No ROA |
| 163.123.164.0/23 | NTTCOM | No ROA |
| 163.123.164.0/24 | NTTCOM | No ROA |
| 163.123.165.0/24 | NTTCOM, RADB | No ROA |
| 163.123.166.0/23 | NTTCOM | No ROA |
| 163.123.166.0/24 | NTTCOM | No ROA |
| 163.123.167.0/24 | NTTCOM | No ROA |
| 192.169.73.0/24 | RADB | No ROA |
| 192.169.74.0/24 | RADB | No ROA |
| 192.169.76.0/24 | RADB | No ROA |
| 192.169.78.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.