Network · data from 2026-11-12
AS263761 Broadcom Group
Registry name: AS263761 - Broadcom Group, S.A, GT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263761, 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.166.240.0/24 | Valid | Nonecovered by 45.166.240.0/22 | 673 100% |
| 45.166.241.0/24 | Valid | Nonecovered by 45.166.240.0/22 | 673 100% |
| 45.166.242.0/24 | Valid | Nonecovered by 45.166.240.0/22 | 673 100% |
| 45.166.243.0/24 | Valid | Nonecovered by 45.166.240.0/22 | 673 100% |
| 138.117.142.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 138.117.143.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 45.166.240.0/22 | Valid | RIR databaseLACNIC | 672 100% |
| 138.117.142.0/23 | Valid | RIR databaseLACNIC | 672 100% |
| 190.99.116.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.99.117.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.99.118.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.99.119.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 190.99.116.0/22 | Valid | RIR databaseLACNIC | 671 100% |
| 2803:5100::/32 | Valid | RIR databaseLACNIC | 605 95% |
AS-SET
PeeringDB's irr_as_set for AS263761: AS263761:AS-BROADCOM. 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 (AS263761 isn't in the set, or no route object for AS263761 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 | AS263761 in it | Not covered |
|---|---|---|---|---|---|
| AS263761:AS-BROADCOM | LACNIC | 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 7 are in fix.csv.
- Route object: none4
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.166.240.0/24 | No route object for it. A route object for 45.166.240.0/22 with origin AS263761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263761 in the RIR database for the space. |
| Route object: none | 45.166.241.0/24 | No route object for it. A route object for 45.166.240.0/22 with origin AS263761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263761 in the RIR database for the space. |
| Route object: none | 45.166.242.0/24 | No route object for it. A route object for 45.166.240.0/22 with origin AS263761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263761 in the RIR database for the space. |
| Route object: none | 45.166.243.0/24 | No route object for it. A route object for 45.166.240.0/22 with origin AS263761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263761 in the RIR database for the space. |
| Route object: RIR | 138.117.142.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.117.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263761 whose prefix no peer sees AS263761 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.117.140.0/23 | LACNIC | 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.