Network · data from 2026-11-12
AS27781 SMITCOMS
Registry name: AS27781 - SMITCOMS N.V., SX · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27781, 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.
| 65.198.230.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 65.217.50.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 65.248.160.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 72.252.8.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 168.0.84.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 168.0.84.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 168.0.86.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 168.197.108.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 190.124.216.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 201.220.12.0/24 | Valid | Nonecovered by 201.220.0.0/20 | 672 100% |
| 201.220.13.0/24 | Valid | Nonecovered by 201.220.0.0/20 | 672 100% |
| 201.220.1.0/24 | Valid | Nonecovered by 201.220.0.0/20 | 671 100% |
| 201.220.8.0/24 | Valid | Nonecovered by 201.220.0.0/20 | 671 100% |
| 201.220.11.0/24 | Valid | Nonecovered by 201.220.0.0/20 | 671 100% |
| 201.220.0.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 201.220.9.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 131.161.84.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 131.161.85.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 131.161.86.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 131.161.87.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 201.220.0.0/20 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 131.161.84.0/23 | Valid | RIR databaseLACNIC, RADB | 668 99% |
| 2800:280::/32 | Valid | RIR databaseLACNIC, RADB | 636 100% |
| 2803:7380:8000::/34 | Valid | RIR databaseLACNIC | 636 100% |
| 2803:7380:c000::/34 | Valid | RIR databaseLACNIC | 636 100% |
AS-SET
AS27781'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 32 are in fix.csv.
- ROA: none9
- Route object: none5
- Route object: RIR11
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 65.198.230.0/24 | No ROA covers it. Add a ROA for AS27781, maxLength 24. |
| Route object: RIR | 65.198.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 65.217.50.0/24 | No ROA covers it. Add a ROA for AS27781, maxLength 24. |
| Route object: RIR | 65.217.50.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 65.248.160.0/24 | No ROA covers it. Add a ROA for AS27781, maxLength 24. |
| Route object: RIR | 65.248.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 72.252.8.0/21 | No ROA covers it. Add a ROA for AS27781, maxLength 21. |
| Route object: RIR | 72.252.8.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.0.84.0/22 | No ROA covers it. Add a ROA for AS27781, maxLength 22. |
| Route object: RIR | 168.0.84.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.0.84.0/23 | No ROA covers it. Add a ROA for AS27781, maxLength 23. |
| Route object: RIR | 168.0.84.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.0.86.0/23 | No ROA covers it. Add a ROA for AS27781, maxLength 23. |
| Route object: RIR | 168.0.86.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 168.197.108.0/22 | No ROA covers it. Add a ROA for AS27781, maxLength 22. |
| Route object: RIR | 168.197.108.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 190.124.216.0/22 | No ROA covers it. Add a ROA for AS27781, maxLength 22. |
| Route object: RIR | 190.124.216.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 201.220.12.0/24 | No route object for it. A route object for 201.220.0.0/20 with origin AS27781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27781 in the RIR database for the space. |
| Route object: none | 201.220.13.0/24 | No route object for it. A route object for 201.220.0.0/20 with origin AS27781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27781 in the RIR database for the space. |
| Route object: none | 201.220.1.0/24 | No route object for it. A route object for 201.220.0.0/20 with origin AS27781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27781 in the RIR database for the space. |
| Route object: none | 201.220.8.0/24 | No route object for it. A route object for 201.220.0.0/20 with origin AS27781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27781 in the RIR database for the space. |
| Route object: none | 201.220.11.0/24 | No route object for it. A route object for 201.220.0.0/20 with origin AS27781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27781 in the RIR database for the space. |
| Route object: RIR | 201.220.0.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.220.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS27781 whose prefix no peer sees AS27781 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.117.46.0/24 | RADB | No ROA |
| 72.252.8.0/24 | RADB | No ROA |
| 190.2.188.0/22 | RADB | No ROA |
| 200.0.23.0/24 | RADB | No ROA |
| 201.220.10.0/24 | RADB | Valid |
| 2803:18c0::/32 | RADB | No ROA |
| 2803:7380::/32 | LACNIC, RADB | 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.