Network · data from 2026-11-12
AS395743 STATIC1 - Static 1 LLC
Registry name: STATIC1 - Static 1 LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS395743, 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.
| 38.107.186.0/24 | No ROA | None | 671 100% |
| 38.76.2.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 207.34.41.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 207.34.45.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 209.104.208.0/24 | Valid | Nonecovered by 209.104.208.0/22 | 673 100% |
| 209.104.209.0/24 | Valid | Other origin onlycovered by 209.104.208.0/22 | 673 100% |
| 209.104.210.0/24 | Valid | Other origin onlycovered by 209.104.208.0/22 | 673 100% |
| 209.104.211.0/24 | Valid | Nonecovered by 209.104.208.0/22 | 673 100% |
| 185.29.231.0/24 | Valid | None | 10 1%low visibility |
| 207.34.44.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS395743 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 21 are in fix.csv.
- ROA: none4
- Route object: none6
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.107.186.0/24 | No ROA covers it. Add a ROA for AS395743, maxLength 24. |
| Route object: none | 38.107.186.0/24 | No route object for it. Add a route object with origin AS395743 in the RIR database for the space. |
| ROA: none | 38.76.2.0/24 | No ROA covers it. Add a ROA for AS395743, maxLength 24. |
| Route object: RIR | 38.76.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.34.41.0/24 | No ROA covers it. Add a ROA for AS395743, maxLength 24. |
| Route object: RIR | 207.34.41.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.34.45.0/24 | No ROA covers it. Add a ROA for AS395743, maxLength 24. |
| Route object: RIR | 207.34.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 209.104.208.0/24 | No route object for it. A route object for 209.104.208.0/22 with origin AS395743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395743 in the RIR database for the space. |
| Route object: none | 209.104.209.0/24 | Route objects for it name AS399589. A route object for 209.104.208.0/22 with origin AS395743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395743 in the RIR database for the space. |
| Route object: none | 209.104.210.0/24 | Route objects for it name AS399589. A route object for 209.104.208.0/22 with origin AS395743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395743 in the RIR database for the space. |
| Route object: none | 209.104.211.0/24 | No route object for it. A route object for 209.104.208.0/22 with origin AS395743 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395743 in the RIR database for the space. |
| Route object: none | 185.29.231.0/24 | No route object for it. Add a route object with origin AS395743 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS395743 whose prefix no peer sees AS395743 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 207.34.36.0/24 | RADB | No ROA |
| 207.34.37.0/24 | RADB | No ROA |
| 207.34.43.0/24 | RADB | No ROA |
| 208.95.84.0/22 | RADB | No ROA |
| 208.95.84.0/24 | ARIN | Valid |
| 208.95.85.0/24 | ARIN | Valid |
| 208.95.86.0/24 | ARIN | Valid |
| 209.104.208.0/22 | ARIN, 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.