Network · data from 2026-11-12
AS3918 SHELL-3918 - Shell Information Technology International B.V.
Registry name: SHELL-3918 - Shell Information Technology International B.V., EU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3918, 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.
| 144.199.196.0/24 | No ROA | Nonecovered by 144.199.196.0/22 | 671 100% |
| 144.199.196.0/22 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 161.126.110.0/24 | No ROA | RIR databaseAPNIC | 2 0%low visibility |
| 145.30.239.0/24 | Valid | None | 673 100% |
| 156.149.128.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 161.126.181.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 134.144.78.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 134.144.182.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 134.144.82.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 134.144.83.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 156.149.136.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 156.149.137.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 156.149.138.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 156.149.139.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 161.126.150.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 161.126.151.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 161.126.210.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 161.126.211.0/24 | Valid | RIR databaseAPNIC | 670 100% |
AS-SET
AS3918 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 20 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR1
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 144.199.196.0/24 | No ROA covers it. Add a ROA for AS3918, maxLength 24. |
| Route object: none | 144.199.196.0/24 | No route object for it. A route object for 144.199.196.0/22 with origin AS3918 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3918 in the RIR database for the space. |
| ROA: none | 144.199.196.0/22 | No ROA covers it. Add a ROA for AS3918, maxLength 22. |
| Route object: RIR | 144.199.196.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 161.126.110.0/24 | No ROA covers it. Add a ROA for AS3918, maxLength 24. |
| Route object: none | 145.30.239.0/24 | No route object for it. Add a route object with origin AS3918 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3918 whose prefix no peer sees AS3918 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 134.144.10.0/24 | APNIC, RADB | No ROA |
| 134.144.246.0/23 | RADB | No ROA |
| 134.144.250.0/23 | RADB | No ROA |
| 134.146.222.0/24 | RIPE | No ROA |
| 134.146.240.0/23 | RIPE | No ROA |
| 144.199.0.0/16 | RADB, RIPE-NONAUTH | No ROA |
| 144.199.193.0/24 | NTTCOM | No ROA |
| 144.199.194.0/24 | NTTCOM | No ROA |
| 145.30.227.0/24 | RADB, RIPE | Valid |
| 145.30.230.0/24 | RIPE | No ROA |
| 156.31.197.0/24 | NTTCOM, RADB | No ROA |
| 156.149.250.0/24 | RADB | No ROA |
| 161.126.156.0/24 | APNIC | No ROA |
| 161.126.186.0/24 | APNIC | 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.