Network · data from 2026-11-12
AS26943 YOUR-ORG-INC-EURO - YOUR.ORG, INC.
Registry name: YOUR-ORG-INC-EURO - YOUR.ORG, INC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26943, 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.
| 2001:4978:f::/48 | No ROA | Nonecovered by 2001:4978::/44 | 635 100% |
| 23.129.152.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 199.165.179.0/24 | No ROA | Other IRR onlyNTTCOM | 669 99% |
| 2606:96c0::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS26943 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 23 are in fix.csv.
- ROA: none4
- Route object: none1
- Route object: RIR3
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:4978:f::/48 | No ROA covers it. Add a ROA for AS26943, maxLength 48. |
| Route object: none | 2001:4978:f::/48 | No route object for it. A route object for 2001:4978::/44 with origin AS26943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26943 in the RIR database for the space. |
| ROA: none | 23.129.152.0/24 | No ROA covers it. Add a ROA for AS26943, maxLength 24. |
| Route object: RIR | 23.129.152.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.165.179.0/24 | No ROA covers it. Add a ROA for AS26943, maxLength 24. |
| Route object: RIR | 199.165.179.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 2606:96c0::/32 | No ROA covers it. Add a ROA for AS26943, maxLength 32. |
| Route object: RIR | 2606:96c0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26943 whose prefix no peer sees AS26943 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.202.112.0/23 | RADB | No ROA |
| 66.17.132.0/24 | NTTCOM | No ROA |
| 69.31.98.0/23 | NTTCOM, RADB | No ROA |
| 204.9.48.0/21 | ARIN, NTTCOM, RADB | No ROA |
| 204.9.48.0/24 | ARIN | No ROA |
| 204.9.49.0/24 | ARIN | No ROA |
| 204.9.50.0/23 | ARIN | No ROA |
| 204.9.51.0/24 | RADB | No ROA |
| 204.9.52.0/23 | ARIN | No ROA |
| 204.9.54.0/23 | ARIN, NTTCOM | No ROA |
| 216.14.96.0/20 | ARIN | No ROA |
| 2001:4978::/32 | ALTDB | No ROA |
| 2001:4978::/44 | RADB | No ROA |
| 2001:4978:4000::/44 | ALTDB | No ROA |
| 2002::/16 | ALTDB | 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.