Network · data from 2026-11-12
AS269757 CYBERIA INTERNET
Registry name: AS269757 - URCHIPIA FERNANDO DIEGO(CYBERIA INTERNET), AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269757, 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.182.186.0/24 | Valid | Nonecovered by 45.182.186.0/23 | 670 100% |
| 45.182.187.0/24 | Valid | Nonecovered by 45.182.186.0/23 | 670 100% |
| 45.182.186.0/23 | Valid | RIR databaseLACNIC | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS269757: AS269757:AS-AS269757. 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 (AS269757 isn't in the set, or no route object for AS269757 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 | AS269757 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS269757:AS-AS269757 | In no IRR database read today. | |||||
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 5 are in fix.csv.
- Route object: none2
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.182.186.0/24 | No route object for it. A route object for 45.182.186.0/23 with origin AS269757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269757 in the RIR database for the space. |
| Route object: none | 45.182.187.0/24 | No route object for it. A route object for 45.182.186.0/23 with origin AS269757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269757 in the RIR database for the space. |
| AS-SET: not found | AS269757:AS-AS269757 | PeeringDB names AS269757:AS-AS269757; no IRR database read has it. |
Route objects not announced
Route objects with origin AS269757 whose prefix no peer sees AS269757 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.182.143.0/24 | LACNIC | Valid |
| 2803:4560::/32 | LACNIC | 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.