Network · data from 2026-11-12
AS399358 ANTHROPIC - Anthropic, PBC
Registry name: ANTHROPIC - Anthropic, PBC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399358, 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.
| 2607:6bc0:11::/48 | Valid | Nonecovered by 2607:6bc0::/32 | 604 95% |
| 160.79.104.0/23 | Valid | RIR databaseARIN | 673 100% |
| 2607:6bc0::/48 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS399358 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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2607:6bc0:11::/48 | No route object for it. A route object for 2607:6bc0::/32 with origin AS399358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399358 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399358 whose prefix no peer sees AS399358 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.46.212.0/24 | RADB | No ROA |
| 38.84.152.0/24 | RADB | No ROA |
| 160.79.104.0/24 | ARIN | Invalid: maxLength |
| 160.79.105.0/24 | ARIN | Invalid: maxLength |
| 209.249.57.0/24 | ARIN | Valid |
| 2607:6bc0::/32 | ARIN | 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.