Network · data from 2026-11-12
AS271779 FULLNET SOLUTIONS
Registry name: AS271779 - FULLNET SOLUTIONS S.A.S., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271779, 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.
| 206.1.68.0/22 | Valid | Nonecovered by 206.1.64.0/20 | 669 99% |
| 206.1.72.0/24 | Valid | Nonecovered by 206.1.64.0/20 | 669 99% |
| 206.1.73.0/24 | Valid | Nonecovered by 206.1.64.0/20 | 669 99% |
| 206.1.74.0/24 | Valid | Nonecovered by 206.1.64.0/20 | 669 99% |
| 206.1.76.0/22 | Valid | Nonecovered by 206.1.64.0/20 | 669 99% |
| 200.106.184.0/24 | Valid | Nonecovered by 200.106.184.0/22 | 668 99% |
| 200.106.185.0/24 | Valid | Nonecovered by 200.106.184.0/22 | 668 99% |
| 200.106.186.0/24 | Valid | Nonecovered by 200.106.184.0/22 | 668 99% |
| 200.106.187.0/24 | Valid | Nonecovered by 200.106.184.0/22 | 668 99% |
| 206.1.72.0/22 | Valid | Nonecovered by 206.1.64.0/20 | 2 0%low visibility |
| 200.106.184.0/22 | Valid | RIR databaseLACNIC | 668 99% |
| 206.1.64.0/20 | Valid | RIR databaseARIN, RADB | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS271779: AS271779:AS-271779. 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 (AS271779 isn't in the set, or no route object for AS271779 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 | AS271779 in it | Not covered |
|---|---|---|---|---|---|
| AS271779:AS-271779 | LACNIC | 2 | 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 11 are in fix.csv.
- Route object: none10
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 206.1.68.0/22 | No route object for it. A route object for 206.1.64.0/20 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 206.1.72.0/24 | No route object for it. A route object for 206.1.64.0/20 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 206.1.73.0/24 | No route object for it. A route object for 206.1.64.0/20 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 206.1.74.0/24 | No route object for it. A route object for 206.1.64.0/20 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 206.1.76.0/22 | No route object for it. A route object for 206.1.64.0/20 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 200.106.184.0/24 | No route object for it. A route object for 200.106.184.0/22 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 200.106.185.0/24 | No route object for it. A route object for 200.106.184.0/22 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 200.106.186.0/24 | No route object for it. A route object for 200.106.184.0/22 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 200.106.187.0/24 | No route object for it. A route object for 200.106.184.0/22 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
| Route object: none | 206.1.72.0/22 | No route object for it. A route object for 206.1.64.0/20 with origin AS271779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271779 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271779 whose prefix no peer sees AS271779 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2803:6fe0::/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.