23IPv4 routes
95.7% RPKI valid · 13.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
20 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS52322, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS52322, 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.
| 38.51.26.0/24 | No ROA | Other IRR onlyALTDB | 670 100% |
| 191.97.32.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.33.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.34.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.35.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.36.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.37.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.38.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.39.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.40.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.41.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.42.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.43.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.44.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 191.97.45.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 673 100% |
| 190.14.156.0/24 | Valid | Nonecovered by 190.14.156.0/22 | 672 100% |
| 190.14.157.0/24 | Valid | Nonecovered by 190.14.156.0/22 | 672 100% |
| 190.14.158.0/24 | Valid | Nonecovered by 190.14.156.0/22 | 672 100% |
| 190.14.159.0/24 | Valid | Nonecovered by 190.14.156.0/22 | 672 100% |
| 191.97.47.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 5 1%low visibility |
| 191.97.46.0/24 | Valid | Nonecovered by 191.97.32.0/20 | 4 1%low visibility |
| 191.97.32.0/20 | Valid | RIR databaseLACNIC | 673 100% |
| 190.14.156.0/22 | Valid | RIR databaseLACNIC | 672 100% |
| 2803:f200::/32 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS52322: AS52322:AS-TELCOCOM. 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 (AS52322 isn't in the set, or no route object for AS52322 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 | AS52322 in it | Not covered |
|---|---|---|---|---|---|
| AS52322:AS-TELCOCOM | LACNIC | 7 | 1 | No | 24 |
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 23 are in fix.csv.
- ROA: none1
- Route object: none20
- Route object: RIR1
- AS-SET: own ASN1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.51.26.0/24 | No ROA covers it. Add a ROA for AS52322, maxLength 24. |
| Route object: RIR | 38.51.26.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 191.97.32.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.33.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.34.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.35.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.36.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.37.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.38.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.39.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.40.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.41.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.42.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.43.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.44.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.45.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 190.14.156.0/24 | No route object for it. A route object for 190.14.156.0/22 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 190.14.157.0/24 | No route object for it. A route object for 190.14.156.0/22 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 190.14.158.0/24 | No route object for it. A route object for 190.14.156.0/22 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 190.14.159.0/24 | No route object for it. A route object for 190.14.156.0/22 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.47.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| Route object: none | 191.97.46.0/24 | No route object for it. A route object for 191.97.32.0/20 with origin AS52322 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52322 in the RIR database for the space. |
| AS-SET: own ASN | AS52322:AS-TELCOCOM | AS52322 isn't in AS52322:AS-TELCOCOM (LACNIC) once expanded. Add AS52322 to it. |
Route objects not announced
Every route object with origin AS52322 is announced.
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.