Network · data from 2026-11-12
AS263528 VIACOM NEXT GENERATION COMUNICACAO LTDA
Registry name: AS263528 - VIACOM NEXT GENERATION COMUNICACAO LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263528, 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.
| 170.254.4.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.254.5.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.254.6.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 191.253.64.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 191.253.66.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:1350::/32 | Valid | Other IRR onlyTC | 633 100% |
| 170.254.4.0/22 | Valid | Other IRR onlyRADB, TC | 2 0%low visibility |
| 191.253.64.0/22 | Valid | Other IRR onlyTC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS263528: AS263528:AS-LIG16. 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 (AS263528 isn't in the set, or no route object for AS263528 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 | AS263528 in it | Not covered |
|---|---|---|---|---|---|
| AS263528:AS-LIG16 | 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 17 are in fix.csv.
- Route object: RIR8
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 170.254.4.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.5.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.6.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.253.64.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.253.66.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1350::/32 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.4.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.253.64.0/22 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263528 whose prefix no peer sees AS263528 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.254.4.0/24 | TC | Valid |
| 170.254.6.0/24 | RADB, TC | Valid |
| 170.254.7.0/24 | TC | Valid |
| 191.253.64.0/24 | TC | Valid |
| 191.253.65.0/24 | RADB, TC | Valid |
| 191.253.66.0/24 | RADB, TC | Valid |
| 191.253.67.0/24 | TC | Valid |
| 2804:1350::/33 | RADB | Valid |
| 2804:1350:8000::/33 | RADB | 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.