Network · data from 2026-11-12
AS269070 Hostzone Tecnologia LTDA
Registry name: AS269070 - Hostzone Tecnologia LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269070, 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.137.28.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 38.225.219.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 45.179.90.0/23 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.179.88.0/23 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 45.179.90.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 45.179.91.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 45.179.88.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 45.179.89.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 2804:5f00:10::/48 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:5f00:fc00::/40 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:5f00:fc01::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:5f00:fc02::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:5f00::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:5f00::/34 | Valid | Other IRR onlyTC | 633 100% |
| 2804:5f00:1::/48 | Valid | Other IRR onlyTC | 633 100% |
| 104.234.186.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 143.14.247.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 50.114.48.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 38.250.8.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 179.61.154.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS269070: TC::AS269070:AS-HOSTZONE. 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 (AS269070 isn't in the set, or no route object for AS269070 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 | AS269070 in it | Not covered |
|---|---|---|---|---|---|
| TC::AS269070:AS-HOSTZONE | TC | 7 | 2 | Yes | 1 |
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 25 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR14
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.137.28.0/24 | ROAs covering it name AS834, AS61317, not AS269070. If AS269070 should announce it, add a ROA for AS269070. |
| Route object: none | 45.137.28.0/24 | Route objects for it name AS834. Add a route object with origin AS269070 in the RIR database for the space. |
| ROA: none | 38.225.219.0/24 | No ROA covers it. Add a ROA for AS269070, maxLength 24. |
| Route object: RIR | 38.225.219.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.90.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.88.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.90.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.91.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.88.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.89.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00:10::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00:fc00::/40 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00:fc01::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00:fc02::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f00:1::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269070 whose prefix no peer sees AS269070 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.179.88.0/22 | RADB, TC | Valid |
| 130.185.238.0/24 | RADB, RIPE | Valid |
| 156.249.64.0/24 | AFRINIC, RADB | Valid |
| 156.249.65.0/24 | AFRINIC, RADB | Valid |
| 156.249.66.0/24 | AFRINIC, RADB | Valid |
| 156.249.67.0/24 | AFRINIC, RADB | Valid |
| 181.215.0.0/24 | RADB, RIPE | Valid |
| 181.215.48.0/24 | RADB, RIPE | 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.