Network · data from 2026-11-12
AS265234 N-MULTIMIDIA TELECOMUNICACOES
Registry name: AS265234 - N-MULTIMIDIA TELECOMUNICACOES LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265234, 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:2cac:1030::/48 | Valid | Nonecovered by 2804:2cac::/35 | 634 100% |
| 2804:2cac:bc00::/40 | Valid | Nonecovered by 2804:2cac:a000::/35 | 634 100% |
| 45.172.68.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.0.96.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:2cac:1111::/48 | Valid | Other IRR onlyTC | 634 100% |
| 2804:2cac:dddd::/48 | Valid | Other IRR onlyTC | 634 100% |
| 2804:2cac::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 168.0.96.0/23 | Valid | Other IRR onlyTC | 198 29% |
| 168.0.96.0/24 | Valid | Other IRR onlyTC | 198 29% |
| 168.0.97.0/24 | Valid | Other IRR onlyTC | 198 29% |
| 168.0.98.0/23 | Valid | Other IRR onlyTC | 198 29% |
| 168.0.98.0/24 | Valid | Other IRR onlyTC | 198 29% |
| 45.172.68.0/23 | Valid | Other IRR onlyTC | 197 29% |
| 45.172.68.0/24 | Valid | Other IRR onlyTC | 197 29% |
| 45.172.69.0/24 | Valid | Other IRR onlyTC | 197 29% |
| 45.172.70.0/23 | Valid | Other IRR onlyTC | 197 29% |
| 45.172.70.0/24 | Valid | Other IRR onlyTC | 197 29% |
| 45.172.71.0/24 | Valid | Other IRR onlyTC | 197 29% |
| 168.0.99.0/24 | Valid | Other IRR onlyTC | 197 29% |
AS-SET
PeeringDB's irr_as_set for AS265234: AS-NMULTIMIDIA. 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 (AS265234 isn't in the set, or no route object for AS265234 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 | AS265234 in it | Not covered |
|---|---|---|---|---|---|
| AS-NMULTIMIDIA | TC | 2 | 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 36 are in fix.csv.
- Route object: none2
- Route object: RIR17
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:2cac:1030::/48 | No route object for it. A route object for 2804:2cac::/35 with origin AS265234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265234 in the RIR database for the space. |
| Route object: none | 2804:2cac:bc00::/40 | No route object for it. A route object for 2804:2cac:a000::/35 with origin AS265234 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265234 in the RIR database for the space. |
| Route object: RIR | 45.172.68.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.96.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2cac:1111::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2cac:dddd::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2cac::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.96.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.96.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.97.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.98.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.98.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.68.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.68.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.69.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.70.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.70.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.71.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.99.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265234 whose prefix no peer sees AS265234 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:2cac::/33 | TC | Valid |
| 2804:2cac::/34 | TC | Valid |
| 2804:2cac::/35 | TC | Valid |
| 2804:2cac:2000::/35 | TC | Valid |
| 2804:2cac:4000::/34 | TC | Valid |
| 2804:2cac:4000::/35 | TC | Valid |
| 2804:2cac:6000::/35 | TC | Valid |
| 2804:2cac:8000::/33 | TC | Valid |
| 2804:2cac:8000::/34 | TC | Valid |
| 2804:2cac:8000::/35 | TC | Valid |
| 2804:2cac:a000::/35 | TC | Valid |
| 2804:2cac:bbbb::/48 | TC | Valid |
| 2804:2cac:c000::/34 | TC | Valid |
| 2804:2cac:c000::/35 | TC | Valid |
| 2804:2cac:cccc::/48 | TC | Valid |
| 2804:2cac:e000::/35 | TC | Valid |
| 2804:2cac:eeee::/48 | 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.