Network · data from 2026-11-12
AS24589 Telenet SIA
Registry name: TELENETSIA-AS Telenet SIA, LV · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24589, 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.90.245.115/32 | Invalid: maxLength | Nonecovered by 91.90.224.0/19 | 2 0%low visibility |
| 109.197.210.19/32 | Invalid: maxLength | Nonecovered by 109.197.208.0/21 | 2 0%low visibility |
| 31.42.80.0/20 | No ROA | None | 2 0%low visibility |
| 31.42.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 83.243.88.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 84.38.136.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 87.99.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 87.99.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.99.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.99.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.99.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.99.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 88.135.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 88.135.144.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 88.135.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.233.214.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 109.197.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.229.192.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 109.229.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 171.25.218.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.103.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.106.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 176.106.100.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.106.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 176.106.176.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.47.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.220.198.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.0.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.111.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.238.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.238.216.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 194.9.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.110.64.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 213.110.76.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.110.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.255.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a01:8ca0::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS24589: AS-TELENET-LATVIA. 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 (AS24589 isn't in the set, or no route object for AS24589 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 | AS24589 in it | Not covered |
|---|---|---|---|---|---|
| AS-TELENET-LATVIA | RIPE | 29 | 4 | Yes | 3 |
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 21 are in fix.csv.
- ROA: maxLength2
- ROA: none1
- Route object: none3
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 91.90.245.115/32 | ROA 91.90.224.0/19 AS24589 has maxLength 29; the route is a /32. Raise the maxLength, or add a ROA for 91.90.245.115/32. |
| Route object: none | 91.90.245.115/32 | No route object for it. A route object for 91.90.224.0/19 with origin AS24589 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24589 in the RIR database for the space. |
| ROA: maxLength | 109.197.210.19/32 | ROA 109.197.208.0/21 AS24589 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 109.197.210.19/32. |
| Route object: none | 109.197.210.19/32 | No route object for it. A route object for 109.197.208.0/21 with origin AS24589 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24589 in the RIR database for the space. |
| ROA: none | 31.42.80.0/20 | No ROA covers it. Add a ROA for AS24589, maxLength 20. |
| Route object: none | 31.42.80.0/20 | No route object for it. Add a route object with origin AS24589 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24589 whose prefix no peer sees AS24589 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 88.135.128.0/19 | RIPE | No ROA |
| 91.90.225.0/24 | RIPE | Valid |
| 91.90.231.0/24 | RIPE | Valid |
| 91.90.237.0/25 | RIPE | Valid |
| 91.90.238.0/24 | RIPE | Valid |
| 91.199.86.0/24 | RIPE | Invalid: origin |
| 109.197.208.0/24 | RIPE | Valid |
| 176.103.176.0/20 | RIPE | No ROA |
| 176.103.184.0/24 | RIPE | Valid |
| 176.103.192.0/21 | RIPE | Invalid: origin |
| 185.47.8.0/22 | RIPE | No ROA |
| 185.47.10.0/24 | RIPE | Valid |
| 193.238.212.128/25 | RIPE | Valid |
| 2a01:8ca0::/56 | RIPE | Invalid: maxLength |
| 2a01:8ca0:f00f::/48 | RIPE | Invalid: maxLength |
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.