Network · data from 2026-11-12
AS47527 DLX-AS DLX A/S
Registry name: DLX-AS DLX A/S, DK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47527, 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.
| 46.30.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 62.69.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 79.174.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.223.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.230.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.23.176.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.31.76.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.126.152.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.208.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.226.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.226.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.116.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.121.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.247.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.182.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.142.140.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.95.208.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:1b18::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:1b19::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:1cf0::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:b920::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a0d:dc00::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS47527 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS47527 is announced.
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.