Network · data from 2026-11-12
AS329479 Hollywood Connect
Registry name: HOLLYWOOD CONNECT (PTY) LTD - HOLLYWOOD CONNECT (PTY) LTD, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS329479, 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.
| 196.2.160.0/19 | Valid | RIR databaseAFRINIC | 672 100% |
| 196.2.160.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.161.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.162.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.163.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.164.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.165.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.166.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.167.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.168.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.169.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.170.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.171.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.172.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.173.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.174.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.175.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.176.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.177.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.178.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.179.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.180.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.181.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.182.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.183.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.184.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.185.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.186.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.187.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.188.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.189.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.190.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
| 196.2.191.0/24 | Valid | RIR databaseAFRINIC | 134 20% |
AS-SET
PeeringDB's irr_as_set for AS329479: AS-HOLLYWOOD-CONNECT. 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 (AS329479 isn't in the set, or no route object for AS329479 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 | AS329479 in it | Not covered |
|---|---|---|---|---|---|
| AS-HOLLYWOOD-CONNECT | AFRINIC | 1 | 1 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS329479 is announced.
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.