Network · data from 2026-11-12
AS212815 ★ Dyjix SAS
Registry name: AS-DYJIX Dyjix SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212815, 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.
| 195.177.94.252/32 | Invalid: origin | None | 3 0%low visibility |
| 45.154.96.107/32 | Invalid: maxLength | Nonecovered by 45.154.96.0/24 | 3 0%low visibility |
| 185.171.202.173/32 | Invalid: maxLength | Nonecovered by 185.171.202.0/24 | 1 0%low visibility |
| 89.33.194.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 91.209.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.171.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.13.119.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.154.96.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a10:4640::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a0f:6280:10a0::/45 | Valid | RIR databaseRIPE | 634 100% |
| 91.250.253.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS212815: AS-DYJIX. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS212815 isn't in the set, or no route object for AS212815 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS212815 in it | Not covered |
|---|---|---|---|---|---|
| AS-DYJIX | RIPElists itself further down1 member set in no database: AS-INFRASIO | 901 | 295 | Yes | 3 |
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 17 are in fix.csv.
- ROA: origin1
- ROA: maxLength2
- Route object: none3
- AS-SET: missing member1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 195.177.94.252/32 | ROAs covering it name AS62206, AS214961, not AS212815. If AS212815 should announce it, add a ROA for AS212815. |
| Route object: none | 195.177.94.252/32 | No route object for it. Add a route object with origin AS212815 in the RIR database for the space. |
| ROA: maxLength | 45.154.96.107/32 | ROA 45.154.96.0/24 AS212815 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 45.154.96.107/32. |
| Route object: none | 45.154.96.107/32 | No route object for it. A route object for 45.154.96.0/24 with origin AS212815 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS212815 in the RIR database for the space. |
| ROA: maxLength | 185.171.202.173/32 | ROA 185.171.202.0/24 AS212815 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.171.202.173/32. |
| Route object: none | 185.171.202.173/32 | No route object for it. A route object for 185.171.202.0/24 with origin AS212815 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS212815 in the RIR database for the space. |
| AS-SET: missing member | AS-DYJIX | AS-DYJIX (RIPE) lists AS-INFRASIO; no IRR database read has it. |
Route objects not announced
Route objects with origin AS212815 whose prefix no peer sees AS212815 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.152.70.0/24 | RIPE | Valid |
| 91.212.26.0/24 | RIPE | Valid |
| 163.5.143.0/24 | RADB, RIPE | Valid |
| 185.177.44.0/24 | RIPE | Valid |
| 194.124.66.0/24 | RIPE | Valid |
| 2a0a:2f80::/32 | RIPE | Valid |
| 2a0a:2f81::/32 | RIPE | Valid |
| 2a10:4640:ffff::/48 | RIPE | Invalid: maxLength |
| 2a10:4641::/32 | RIPE | No ROA |
| 2a10:4642::/32 | RIPE | 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.