Network · data from 2026-11-12
AS266771 Makronet Consulting Tecnologia E Informatica Limitada
Registry name: AS266771 - MAKRONET CONSULTING TECNOLOGIA E INFORMATICA LIMITADA, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266771, 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:cf20::/32 | No ROA | Other IRR onlyRADB | 636 100% |
| 160.19.202.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 45.166.74.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.166.75.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 160.19.203.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.232.176.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.232.177.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.232.178.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.232.179.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 45.166.73.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 190.93.229.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 190.93.230.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 190.93.231.0/24 | Valid | RIR databaseLACNIC, RADB | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS266771: AS266771:AS-FICOM. 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 (AS266771 isn't in the set, or no route object for AS266771 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 | AS266771 in it | Not covered |
|---|---|---|---|---|---|
| AS266771:AS-FICOM | RADB | 15 | 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 15 are in fix.csv.
- ROA: none1
- Route object: RIR5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2803:cf20::/32 | No ROA covers it. Add a ROA for AS266771, maxLength 32. |
| Route object: RIR | 2803:cf20::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.19.202.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.166.74.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.166.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.19.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266771 whose prefix no peer sees AS266771 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.250.112.0/23 | RADB | No ROA |
| 38.250.112.0/24 | RADB | No ROA |
| 38.250.113.0/24 | RADB | No ROA |
| 45.162.135.0/24 | LACNIC | Valid |
| 45.166.74.0/23 | LACNIC | Valid |
| 45.232.176.0/22 | LACNIC, RADB | Valid |
| 160.19.202.0/23 | LACNIC, RADB | Valid |
| 190.93.228.0/24 | LACNIC, RADB | Valid |
| 2803:7d50::/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.