Network · data from 2026-11-12
AS269174 FIXANET TELECOM PROVEDOR DE INTERNET
Registry name: AS269174 - FIXANET TELECOM PROVEDOR DE INTERNET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269174, 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.180.104.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.180.104.0/23 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.180.106.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 45.180.106.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.180.104.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 45.180.105.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 45.180.107.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:608c::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS269174: AS269174:AS-ANNOUNCEMENTS. 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 (AS269174 isn't in the set, or no route object for AS269174 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 | AS269174 in it | Not covered |
|---|---|---|---|---|---|
| AS269174:AS-ANNOUNCEMENTS | TC | 1 | 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 9 are in fix.csv.
- Route object: RIR8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.180.104.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.180.104.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.180.106.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.180.106.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.180.104.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.180.105.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.180.107.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:608c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269174 whose prefix no peer sees AS269174 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:7374::/32 | RADB | No ROA |
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.