Network · data from 2026-11-12
AS29584 AZEDUNET
Registry name: AZEDUNET-AS AZEDUNET LLC, AZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29584, 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.
| 2a00:8d40::/32 | No ROA | RIR databaseRIPE | 634 100% |
| 82.194.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.194.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.194.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.2.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.4.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.6.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.7.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.8.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.10.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.11.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.12.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.13.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.194.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS29584: AS29584. 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 (AS29584 isn't in the set, or no route object for AS29584 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 | AS29584 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS29584 | A single AS number, not a set: AS29584 (this network), 18 route objects. | |||||
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 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a00:8d40::/32 | No ROA covers it. Add a ROA for AS29584, maxLength 32. |
Route objects not announced
Route objects with origin AS29584 whose prefix no peer sees AS29584 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.194.0.0/21 | RIPE | No ROA |
| 82.194.4.0/24 | RIPE | Invalid: maxLength |
| 82.194.5.0/24 | RIPE | Invalid: maxLength |
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.