Network · data from 2026-11-12
AS44027 Spitamen Alexander Internet
Registry name: SPITAMEN_ALEXANDER_INTERNET-AS Spitamen Alexander Internet LLC., TJ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44027, 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.
| 91.231.252.0/23 | No ROA | Other origin onlycovered by 91.231.252.0/22 | 673 100% |
| 91.231.254.0/23 | No ROA | Other origin onlycovered by 91.231.252.0/22 | 673 100% |
| 91.200.216.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.218.168.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.231.252.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.235.36.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.113.128.0/20 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS44027'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 45 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: not announced36
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.231.252.0/23 | No ROA covers it. Add a ROA for AS44027, maxLength 23. |
| Route object: none | 91.231.252.0/23 | Route objects for it name AS28910. A route object for 91.231.252.0/22 with origin AS44027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44027 in the RIR database for the space. |
| ROA: none | 91.231.254.0/23 | No ROA covers it. Add a ROA for AS44027, maxLength 23. |
| Route object: none | 91.231.254.0/23 | Route objects for it name AS28910. A route object for 91.231.252.0/22 with origin AS44027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44027 in the RIR database for the space. |
| ROA: none | 91.200.216.0/22 | No ROA covers it. Add a ROA for AS44027, maxLength 22. |
| ROA: none | 91.218.168.0/22 | No ROA covers it. Add a ROA for AS44027, maxLength 22. |
| ROA: none | 91.231.252.0/22 | No ROA covers it. Add a ROA for AS44027, maxLength 22. |
| ROA: none | 91.235.36.0/22 | No ROA covers it. Add a ROA for AS44027, maxLength 22. |
| ROA: none | 176.113.128.0/20 | No ROA covers it. Add a ROA for AS44027, maxLength 20. |
Route objects not announced
Route objects with origin AS44027 whose prefix no peer sees AS44027 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.200.216.0/23 | RIPE | No ROA |
| 91.200.216.0/24 | RIPE | No ROA |
| 91.200.217.0/24 | RIPE | No ROA |
| 91.200.218.0/23 | RIPE | No ROA |
| 91.200.218.0/24 | RIPE | No ROA |
| 91.200.219.0/24 | RIPE | No ROA |
| 91.218.168.0/23 | RIPE | No ROA |
| 91.218.168.0/24 | RIPE | No ROA |
| 91.218.169.0/24 | RIPE | No ROA |
| 91.218.170.0/23 | RIPE | No ROA |
| 91.218.170.0/24 | RIPE | No ROA |
| 91.218.171.0/24 | RIPE | No ROA |
| 91.231.252.0/24 | RIPE | No ROA |
| 91.231.253.0/24 | RIPE | No ROA |
| 91.231.254.0/24 | RIPE | No ROA |
| 91.231.255.0/24 | RIPE | No ROA |
| 91.235.36.0/24 | RIPE | No ROA |
| 91.235.37.0/24 | RIPE | No ROA |
| 91.235.38.0/24 | RIPE | No ROA |
| 91.235.39.0/24 | RIPE | No ROA |
| 176.113.128.0/24 | RIPE | No ROA |
| 176.113.129.0/24 | RIPE | No ROA |
| 176.113.130.0/24 | RIPE | No ROA |
| 176.113.131.0/24 | RIPE | No ROA |
| 176.113.132.0/24 | RIPE | No ROA |
| 176.113.133.0/24 | RIPE | No ROA |
| 176.113.134.0/24 | RIPE | No ROA |
| 176.113.135.0/24 | RIPE | No ROA |
| 176.113.136.0/24 | RIPE | No ROA |
| 176.113.137.0/24 | RIPE | No ROA |
| 176.113.138.0/24 | RIPE | No ROA |
| 176.113.139.0/24 | RIPE | No ROA |
| 176.113.140.0/24 | RIPE | No ROA |
| 176.113.141.0/24 | RIPE | No ROA |
| 176.113.142.0/24 | RIPE | No ROA |
| 176.113.143.0/24 | RIPE | 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.