Network · data from 2026-11-12
AS393513 Synaptics Incorporated
Registry name: AS-SYNAPT - Synaptics Incorporated, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393513, 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.
| 192.147.44.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 199.33.119.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 61.14.164.0/24 | Valid | None | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS393513: AS393513. 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 (AS393513 isn't in the set, or no route object for AS393513 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 | AS393513 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS393513 | A single AS number, not a set: AS393513 (this network), 4 route objects. | |||||
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.
- ROA: none2
- Route object: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.147.44.0/24 | No ROA covers it. Add a ROA for AS393513, maxLength 24. |
| Route object: RIR | 192.147.44.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 199.33.119.0/24 | No ROA covers it. Add a ROA for AS393513, maxLength 24. |
| Route object: RIR | 199.33.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 61.14.164.0/24 | No route object for it. Add a route object with origin AS393513 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393513 whose prefix no peer sees AS393513 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 205.175.208.0/24 | ARIN | No ROA |
| 2620:113:e000::/44 | ARIN | 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.