Network · data from 2026-11-12
AS274146 Berisys
Registry name: AS274146 - BERISYS SOLUTIONS S.R.L., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274146, 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.
| 45.160.156.0/23 | Valid | Nonecovered by 45.160.156.0/22 | 673 100% |
| 45.160.156.0/24 | Valid | Nonecovered by 45.160.156.0/22 | 673 100% |
| 45.160.157.0/24 | Valid | Nonecovered by 45.160.156.0/22 | 673 100% |
| 45.160.158.0/23 | Valid | Nonecovered by 45.160.156.0/22 | 673 100% |
| 45.160.158.0/24 | Valid | Nonecovered by 45.160.156.0/22 | 673 100% |
| 45.160.159.0/24 | Valid | Nonecovered by 45.160.156.0/22 | 673 100% |
| 45.160.156.0/22 | Valid | RIR databaseALTDB, LACNIC | 673 100% |
| 2803:89d0::/32 | Valid | RIR databaseLACNIC | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS274146: LACNIC::AS274146:AS-BERISYS. 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 (AS274146 isn't in the set, or no route object for AS274146 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 | AS274146 in it | Not covered |
|---|---|---|---|---|---|
| LACNIC::AS274146:AS-BERISYS | LACNIC | 1 | 1 | 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 6 are in fix.csv.
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.160.156.0/23 | No route object for it. A route object for 45.160.156.0/22 with origin AS274146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274146 in the RIR database for the space. |
| Route object: none | 45.160.156.0/24 | No route object for it. A route object for 45.160.156.0/22 with origin AS274146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274146 in the RIR database for the space. |
| Route object: none | 45.160.157.0/24 | No route object for it. A route object for 45.160.156.0/22 with origin AS274146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274146 in the RIR database for the space. |
| Route object: none | 45.160.158.0/23 | No route object for it. A route object for 45.160.156.0/22 with origin AS274146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274146 in the RIR database for the space. |
| Route object: none | 45.160.158.0/24 | No route object for it. A route object for 45.160.156.0/22 with origin AS274146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274146 in the RIR database for the space. |
| Route object: none | 45.160.159.0/24 | No route object for it. A route object for 45.160.156.0/22 with origin AS274146 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274146 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS274146 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.