Network · data from 2026-11-12
AS271516 Unafiber
Registry name: AS271516 - UNAFIBER TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271516, 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.
| 2804:7cc0::/34 | Valid | Nonecovered by 2804:7cc0::/32 | 631 99% |
| 2804:7cc0:2001::/48 | Valid | Nonecovered by 2804:7cc0::/32 | 631 99% |
| 2804:7cc0:2100::/40 | Valid | Nonecovered by 2804:7cc0::/32 | 631 99% |
| 2804:7cc0:c000::/34 | Valid | Nonecovered by 2804:7cc0::/32 | 631 99% |
| 181.232.176.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 181.232.176.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 181.232.176.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 181.232.177.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 181.232.178.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 181.232.179.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.42.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.44.0/22 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.44.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.44.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.45.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.46.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.46.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.47.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 191.242.43.0/24 | Valid | Other IRR onlyTC | 3 0%low visibility |
| 181.232.178.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS271516: AS271516:AS-UNAFIBER. 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 (AS271516 isn't in the set, or no route object for AS271516 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 | AS271516 in it | Not covered |
|---|---|---|---|---|---|
| AS271516:AS-UNAFIBER | TC | 1 | 3 | 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 22 are in fix.csv.
- Route object: none4
- Route object: RIR16
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:7cc0::/34 | No route object for it. A route object for 2804:7cc0::/32 with origin AS271516 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271516 in the RIR database for the space. |
| Route object: none | 2804:7cc0:2001::/48 | No route object for it. A route object for 2804:7cc0::/32 with origin AS271516 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271516 in the RIR database for the space. |
| Route object: none | 2804:7cc0:2100::/40 | No route object for it. A route object for 2804:7cc0::/32 with origin AS271516 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271516 in the RIR database for the space. |
| Route object: none | 2804:7cc0:c000::/34 | No route object for it. A route object for 2804:7cc0::/32 with origin AS271516 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271516 in the RIR database for the space. |
| Route object: RIR | 181.232.176.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.176.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.176.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.177.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.178.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.179.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.42.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.44.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.44.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.44.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.45.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.46.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.46.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.47.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.242.43.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 181.232.178.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271516 whose prefix no peer sees AS271516 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 191.242.42.0/24 | TC | Valid |
| 2804:7cc0::/32 | RADB, TC | 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.