Network · data from 2026-11-12
AS23077 SPICA - SPICA Industry LLC
Registry name: SPICA - SPICA Industry LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23077, 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.
| 155.103.196.0/23 | Valid | Nonecovered by 155.103.196.0/22 | 672 100% |
| 155.103.197.0/24 | Valid | Nonecovered by 155.103.196.0/22 | 672 100% |
| 155.103.198.0/23 | Valid | Nonecovered by 155.103.196.0/22 | 672 100% |
| 155.103.198.0/24 | Valid | Nonecovered by 155.103.196.0/22 | 672 100% |
| 155.103.199.0/24 | Valid | Nonecovered by 155.103.196.0/22 | 672 100% |
| 155.103.196.0/24 | Valid | Other origin onlycovered by 155.103.196.0/22 | 669 99% |
| 2602:f9aa:10::/44 | Valid | Nonecovered by 2602:f9aa::/40 | 634 100% |
| 155.103.196.0/22 | Valid | RIR databaseARIN | 670 100% |
| 2602:f9aa::/40 | Valid | RIR databaseARIN | 635 100% |
AS-SET
AS23077 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 41 are in fix.csv.
- Route object: none7
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 155.103.196.0/23 | No route object for it. A route object for 155.103.196.0/22 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
| Route object: none | 155.103.197.0/24 | No route object for it. A route object for 155.103.196.0/22 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
| Route object: none | 155.103.198.0/23 | No route object for it. A route object for 155.103.196.0/22 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
| Route object: none | 155.103.198.0/24 | No route object for it. A route object for 155.103.196.0/22 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
| Route object: none | 155.103.199.0/24 | No route object for it. A route object for 155.103.196.0/22 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
| Route object: none | 155.103.196.0/24 | Route objects for it name AS19205. A route object for 155.103.196.0/22 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
| Route object: none | 2602:f9aa:10::/44 | No route object for it. A route object for 2602:f9aa::/40 with origin AS23077 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23077 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23077 whose prefix no peer sees AS23077 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.170.24.0/24 | RADB | Valid |
| 2405:84c0:3000::/36 | APNIC | Valid |
| 2405:84c0:3000::/37 | APNIC | Valid |
| 2405:84c0:3000::/38 | APNIC | Valid |
| 2405:84c0:3000::/39 | APNIC | Valid |
| 2405:84c0:3000::/40 | APNIC | Valid |
| 2405:84c0:3100::/40 | APNIC | Valid |
| 2405:84c0:3200::/39 | APNIC | Valid |
| 2405:84c0:3200::/40 | APNIC | Valid |
| 2405:84c0:3300::/40 | APNIC | Valid |
| 2405:84c0:3400::/38 | APNIC | Valid |
| 2405:84c0:3400::/39 | APNIC | Valid |
| 2405:84c0:3400::/40 | APNIC | Valid |
| 2405:84c0:3500::/40 | APNIC | Valid |
| 2405:84c0:3600::/39 | APNIC | Valid |
| 2405:84c0:3600::/40 | APNIC | Valid |
| 2405:84c0:3700::/40 | APNIC | Valid |
| 2405:84c0:3800::/37 | APNIC | Valid |
| 2405:84c0:3800::/38 | APNIC | Valid |
| 2405:84c0:3800::/39 | APNIC | Valid |
| 2405:84c0:3800::/40 | APNIC | Valid |
| 2405:84c0:3900::/40 | APNIC | Valid |
| 2405:84c0:3a00::/39 | APNIC | Valid |
| 2405:84c0:3a00::/40 | APNIC | Valid |
| 2405:84c0:3b00::/40 | APNIC | Valid |
| 2405:84c0:3c00::/38 | APNIC | Valid |
| 2405:84c0:3c00::/39 | APNIC | Valid |
| 2405:84c0:3c00::/40 | APNIC | Valid |
| 2405:84c0:3d00::/40 | APNIC | Valid |
| 2405:84c0:3e00::/39 | APNIC | Valid |
| 2405:84c0:3e00::/40 | APNIC | Valid |
| 2405:84c0:3f00::/40 | APNIC | Valid |
| 2405:84c0:5e00::/40 | APNIC | Valid |
| 2a0a:6040:ad50::/44 | RIPE | Invalid: origin |
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.