Network · data from 2026-11-12
AS61449 Research SRL
Registry name: AS61449 - RESEARCH SRL, AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61449, 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.
| 2803:580:800::/39 | Valid | Nonecovered by 2803:580::/32 | 5 1%low visibility |
| 138.186.160.0/23 | Valid | Nonecovered by 138.186.160.0/22 | 4 1%low visibility |
| 138.186.160.0/24 | Valid | Nonecovered by 138.186.160.0/22 | 4 1%low visibility |
| 138.186.161.0/24 | Valid | Nonecovered by 138.186.160.0/22 | 4 1%low visibility |
| 138.186.162.0/23 | Valid | Nonecovered by 138.186.160.0/22 | 4 1%low visibility |
| 138.186.162.0/24 | Valid | Nonecovered by 138.186.160.0/22 | 4 1%low visibility |
| 138.186.163.0/24 | Valid | Nonecovered by 138.186.160.0/22 | 4 1%low visibility |
| 201.139.80.0/23 | Valid | Nonecovered by 201.139.80.0/22 | 4 1%low visibility |
| 201.139.80.0/24 | Valid | Nonecovered by 201.139.80.0/22 | 4 1%low visibility |
| 201.139.81.0/24 | Valid | Nonecovered by 201.139.80.0/22 | 4 1%low visibility |
| 201.139.82.0/23 | Valid | Nonecovered by 201.139.80.0/22 | 4 1%low visibility |
| 201.139.82.0/24 | Valid | Nonecovered by 201.139.80.0/22 | 4 1%low visibility |
| 201.139.83.0/24 | Valid | Nonecovered by 201.139.80.0/22 | 4 1%low visibility |
| 138.186.160.0/22 | Valid | RIR databaseLACNIC, RADB | 667 99% |
| 201.139.80.0/22 | Valid | RIR databaseLACNIC, RADB | 667 99% |
| 2803:580::/32 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS61449: AS61449:AS-RES. 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 (AS61449 isn't in the set, or no route object for AS61449 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 | AS61449 in it | Not covered |
|---|---|---|---|---|---|
| AS61449:AS-RES | LACNIC | 8 | 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 13 are in fix.csv.
- Route object: none13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:580:800::/39 | No route object for it. A route object for 2803:580::/32 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 138.186.160.0/23 | No route object for it. A route object for 138.186.160.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 138.186.160.0/24 | No route object for it. A route object for 138.186.160.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 138.186.161.0/24 | No route object for it. A route object for 138.186.160.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 138.186.162.0/23 | No route object for it. A route object for 138.186.160.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 138.186.162.0/24 | No route object for it. A route object for 138.186.160.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 138.186.163.0/24 | No route object for it. A route object for 138.186.160.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 201.139.80.0/23 | No route object for it. A route object for 201.139.80.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 201.139.80.0/24 | No route object for it. A route object for 201.139.80.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 201.139.81.0/24 | No route object for it. A route object for 201.139.80.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 201.139.82.0/23 | No route object for it. A route object for 201.139.80.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 201.139.82.0/24 | No route object for it. A route object for 201.139.80.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
| Route object: none | 201.139.83.0/24 | No route object for it. A route object for 201.139.80.0/22 with origin AS61449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61449 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS61449 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.