Network · data from 2026-11-12
AS133735 MCKINSEY-AS-SG - McKinsey & Company
Registry name: MCKINSEY-AS-SG - McKinsey & Company, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133735, 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.
| 156.107.108.0/24 | No ROA | Other origin only | 673 100% |
| 156.107.101.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS133735 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 12 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 156.107.108.0/24 | No ROA covers it. Add a ROA for AS133735, maxLength 24. |
| Route object: none | 156.107.108.0/24 | Route objects for it name AS133734. Add a route object with origin AS133735 in the RIR database for the space. |
| ROA: none | 156.107.101.0/24 | No ROA covers it. Add a ROA for AS133735, maxLength 24. |
| Route object: RIR | 156.107.101.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133735 whose prefix no peer sees AS133735 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.107.26.0/24 | RADB | No ROA |
| 156.107.27.0/24 | RADB | No ROA |
| 156.107.100.0/24 | RADB | No ROA |
| 156.107.136.0/24 | RADB | No ROA |
| 156.107.137.0/24 | RADB | No ROA |
| 156.107.138.0/24 | RADB | No ROA |
| 156.107.139.0/24 | RADB | No ROA |
| 2001:470:313::/48 | ARIN | Invalid: origin |
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.