Network · data from 2026-11-12
AS30006 TOP BUSINESS INC
Registry name: TOP-BUSINESS-INC - TOP BUSINESS INC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30006, 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.
| 2602:fb26:810::/48 | No ROA | Other origin only | 633 100% |
| 23.171.216.0/24 | Valid | RIR databaseARIN | 673 100% |
| 142.248.8.0/22 | Valid | RIR databaseARIN | 673 100% |
| 23.129.84.0/24 | Valid | RIR databaseARIN | 672 100% |
| 23.169.56.0/24 | Valid | RIR databaseARIN | 671 100% |
| 23.191.152.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS30006's PeeringDB record names no 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 7 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:fb26:810::/48 | No ROA covers it. Add a ROA for AS30006, maxLength 48. |
| Route object: none | 2602:fb26:810::/48 | Route objects for it name AS13898. Add a route object with origin AS30006 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30006 whose prefix no peer sees AS30006 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.169.57.0/24 | ARIN | Valid |
| 98.124.188.0/24 | ALTDB | No ROA |
| 2602:f7df::/40 | ARIN | Valid |
| 2602:f97c::/40 | ARIN | No ROA |
| 2602:f99a::/40 | ARIN | Valid |
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.