Network · data from 2026-11-12
AS33166 Broadridge Financial Solutions
Registry name: BFS-49-33166 - Broadridge Financial Solutions, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33166, 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.
| 167.212.40.0/21 | No ROA | Other origin only | 673 100% |
| 167.212.40.0/24 | No ROA | Other origin only | 673 100% |
| 167.212.47.0/24 | No ROA | Other origin only | 673 100% |
| 167.212.128.0/24 | No ROA | Other origin only | 673 100% |
| 167.212.0.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS33166: RADB::AS-BROADRIDGE. 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 (AS33166 isn't in the set, or no route object for AS33166 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 | AS33166 in it | Not covered | |
|---|---|---|---|---|---|---|
| RADB::AS-BROADRIDGE | In no IRR database read today. | |||||
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 16 are in fix.csv.
- ROA: none5
- Route object: none4
- Route object: RIR1
- AS-SET: not found1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.212.40.0/21 | No ROA covers it. Add a ROA for AS33166, maxLength 21. |
| Route object: none | 167.212.40.0/21 | Route objects for it name AS198949. Add a route object with origin AS33166 in the RIR database for the space. |
| ROA: none | 167.212.40.0/24 | No ROA covers it. Add a ROA for AS33166, maxLength 24. |
| Route object: none | 167.212.40.0/24 | Route objects for it name AS198949. Add a route object with origin AS33166 in the RIR database for the space. |
| ROA: none | 167.212.47.0/24 | No ROA covers it. Add a ROA for AS33166, maxLength 24. |
| Route object: none | 167.212.47.0/24 | Route objects for it name AS198949. Add a route object with origin AS33166 in the RIR database for the space. |
| ROA: none | 167.212.128.0/24 | No ROA covers it. Add a ROA for AS33166, maxLength 24. |
| Route object: none | 167.212.128.0/24 | Route objects for it name AS198949. Add a route object with origin AS33166 in the RIR database for the space. |
| ROA: none | 167.212.0.0/20 | No ROA covers it. Add a ROA for AS33166, maxLength 20. |
| Route object: RIR | 167.212.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | RADB::AS-BROADRIDGE | PeeringDB names RADB::AS-BROADRIDGE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS33166 whose prefix no peer sees AS33166 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.149.53.0/24 | RADB | No ROA |
| 63.119.254.0/24 | RADB | No ROA |
| 64.74.60.0/24 | RADB | No ROA |
| 64.74.69.0/24 | RADB | No ROA |
| 64.95.22.0/24 | RADB | No ROA |
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.