Network · data from 2026-11-12
AS265947 INTERADIONET SERVICOS DE REDES E INTERNET LTDA
Registry name: AS265947 - INTERADIONET SERVICOS DE REDES E INTERNET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265947, 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.
| 164.163.76.0/23 | Valid | Other IRR onlyALTDB, RADB | 672 100% |
| 164.163.79.0/24 | Valid | Other IRR onlyALTDB, RADB | 672 100% |
| 164.163.76.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB, TC | 671 100% |
| 164.163.76.0/24 | Valid | Other IRR onlyALTDB, RADB | 671 100% |
| 164.163.78.0/23 | Valid | Other IRR onlyALTDB, RADB | 670 100% |
| 2804:4040::/32 | Valid | Other IRR onlyALTDB, NTTCOM, RADB, TC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS265947: AS-265947. 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 (AS265947 isn't in the set, or no route object for AS265947 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 | AS265947 in it | Not covered |
|---|---|---|---|---|---|
| AS-265947 | ALTDB | 1 | 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 14 are in fix.csv.
- Route object: RIR6
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 164.163.76.0/23 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.79.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.76.0/22 | Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.76.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.78.0/23 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4040::/32 | Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265947 whose prefix no peer sees AS265947 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 164.163.77.0/24 | ALTDB, RADB | Valid |
| 164.163.78.0/24 | ALTDB, RADB | Valid |
| 2804:4040::/33 | ALTDB | Valid |
| 2804:4040::/34 | ALTDB | Valid |
| 2804:4040:4000::/34 | ALTDB | Valid |
| 2804:4040:8000::/33 | ALTDB | Valid |
| 2804:4040:8000::/34 | ALTDB | Valid |
| 2804:4040:c000::/34 | ALTDB | 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.