Network · data from 2026-11-12
AS208822 EITECH Eitech AB
Registry name: EITECH Eitech AB, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208822, 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.
| 194.68.172.128/26 | Invalid: maxLength | Nonecovered by 194.68.172.0/24 | 1 0%low visibility |
| 194.68.172.192/26 | Invalid: maxLength | Nonecovered by 194.68.172.0/24 | 1 0%low visibility |
| 194.68.172.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS208822 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.
- ROA: maxLength2
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 194.68.172.128/26 | ROA 194.68.172.0/24 AS208822 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 194.68.172.128/26. |
| Route object: none | 194.68.172.128/26 | No route object for it. A route object for 194.68.172.0/24 with origin AS208822 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208822 in the RIR database for the space. |
| ROA: maxLength | 194.68.172.192/26 | ROA 194.68.172.0/24 AS208822 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 194.68.172.192/26. |
| Route object: none | 194.68.172.192/26 | No route object for it. A route object for 194.68.172.0/24 with origin AS208822 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS208822 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208822 whose prefix no peer sees AS208822 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.103.196.0/24 | RIPE | 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.