Network · data from 2026-11-12
AS270052 STARTELECOM S.A.
Registry name: AS270052 - STARTELECOM S.A., PY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270052, 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.
| 154.51.4.0/24 | No ROA | Nonecovered by 154.51.4.0/23 | 17 3%low visibility |
| 154.51.5.0/24 | No ROA | Nonecovered by 154.51.4.0/23 | 17 3%low visibility |
| 154.51.6.0/24 | No ROA | Nonecovered by 154.51.6.0/23 | 17 3%low visibility |
| 154.51.7.0/24 | No ROA | Nonecovered by 154.51.6.0/23 | 17 3%low visibility |
| 154.51.4.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 154.51.4.0/23 | No ROA | Other IRR onlyALTDB | 672 100% |
| 154.51.6.0/23 | No ROA | Other IRR onlyALTDB | 672 100% |
| 37.230.56.0/23 | Valid | Other IRR onlyALTDB | 672 100% |
| 37.230.58.0/23 | Valid | Other IRR onlyALTDB | 672 100% |
| 37.230.56.0/24 | Valid | Other IRR onlyALTDB | 17 3%low visibility |
| 37.230.57.0/24 | Valid | Other IRR onlyALTDB | 17 3%low visibility |
| 37.230.56.0/22 | Valid | RIR databaseALTDB, RADB, RIPE | 672 100% |
| 138.59.224.0/22 | Valid | RIR databaseALTDB, LACNIC, RADB | 672 100% |
| 138.59.224.0/23 | Valid | RIR databaseALTDB, LACNIC, RADB | 671 100% |
| 138.59.226.0/23 | Valid | RIR databaseALTDB, LACNIC, RADB | 671 100% |
| 2803:ede0::/32 | Valid | RIR databaseALTDB, LACNIC, RADB | 634 100% |
| 138.59.224.0/24 | Valid | RIR databaseALTDB, LACNIC, RADB | 16 2%low visibility |
| 138.59.225.0/24 | Valid | RIR databaseALTDB, LACNIC, RADB | 16 2%low visibility |
| 138.59.226.0/24 | Valid | RIR databaseALTDB, LACNIC, RADB | 16 2%low visibility |
| 138.59.227.0/24 | Valid | RIR databaseALTDB, LACNIC, RADB | 16 2%low visibility |
| 2803:ede0::/33 | Valid | RIR databaseALTDB, LACNIC | 6 1%low visibility |
| 2803:ede0:8000::/33 | Valid | RIR databaseALTDB, LACNIC | 6 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS270052: AS-STARTPY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS270052 isn't in the set, or no route object for AS270052 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS270052 in it | Not covered |
|---|---|---|---|---|---|
| AS-STARTPY | ALTDB | 15 | 2 | Yes | 0 |
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: none7
- Route object: none4
- Route object: RIR7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.51.4.0/24 | No ROA covers it. Add a ROA for AS270052, maxLength 24. |
| Route object: none | 154.51.4.0/24 | No route object for it. A route object for 154.51.4.0/23 with origin AS270052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270052 in the RIR database for the space. |
| ROA: none | 154.51.5.0/24 | No ROA covers it. Add a ROA for AS270052, maxLength 24. |
| Route object: none | 154.51.5.0/24 | No route object for it. A route object for 154.51.4.0/23 with origin AS270052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270052 in the RIR database for the space. |
| ROA: none | 154.51.6.0/24 | No ROA covers it. Add a ROA for AS270052, maxLength 24. |
| Route object: none | 154.51.6.0/24 | No route object for it. A route object for 154.51.6.0/23 with origin AS270052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270052 in the RIR database for the space. |
| ROA: none | 154.51.7.0/24 | No ROA covers it. Add a ROA for AS270052, maxLength 24. |
| Route object: none | 154.51.7.0/24 | No route object for it. A route object for 154.51.6.0/23 with origin AS270052 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270052 in the RIR database for the space. |
| ROA: none | 154.51.4.0/22 | No ROA covers it. Add a ROA for AS270052, maxLength 22. |
| Route object: RIR | 154.51.4.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.51.4.0/23 | No ROA covers it. Add a ROA for AS270052, maxLength 23. |
| Route object: RIR | 154.51.4.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 154.51.6.0/23 | No ROA covers it. Add a ROA for AS270052, maxLength 23. |
| Route object: RIR | 154.51.6.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 37.230.56.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 37.230.58.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 37.230.56.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 37.230.57.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270052 whose prefix no peer sees AS270052 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.230.58.0/24 | ALTDB | Valid |
| 37.230.59.0/24 | ALTDB | 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.