Network · data from 2026-11-12
AS18842 VERTICAL-SCR - Business Information Group, Inc.
Registry name: VERTICAL-SCR - Business Information Group, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18842, 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.
| 63.121.77.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 65.211.100.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 208.251.220.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 208.251.221.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS18842 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 8 are in fix.csv.
- ROA: none4
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 63.121.77.0/24 | No ROA covers it. Add a ROA for AS18842, maxLength 24. |
| Route object: RIR | 63.121.77.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 65.211.100.0/24 | No ROA covers it. Add a ROA for AS18842, maxLength 24. |
| Route object: RIR | 65.211.100.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.251.220.0/24 | No ROA covers it. Add a ROA for AS18842, maxLength 24. |
| Route object: RIR | 208.251.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.251.221.0/24 | No ROA covers it. Add a ROA for AS18842, maxLength 24. |
| Route object: RIR | 208.251.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS18842 is announced.
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.