Network · data from 2026-11-12
AS40793 LINKEDIN - LinkedIn Corporation
Registry name: LINKEDIN - LinkedIn Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40793, 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.
| 108.174.5.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 108.174.6.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 108.174.7.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 2620:109:c003::/48 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS40793 isn't in PeeringDB, where networks name their AS-SET.
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 5 are in fix.csv.
- Route object: RIR4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 108.174.5.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 108.174.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 108.174.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2620:109:c003::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40793 whose prefix no peer sees AS40793 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 144.2.19.0/24 | 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.