Network · data from 2026-11-12
AS208914 T-DUDE Networks
Registry name: TDUDENET Tristan Gosselin-Hane, CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208914, 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.
| 2a0c:9a46:632::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a0c:9a46:633::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a0c:9a46:634::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a0c:9a46:635::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a0c:9a46:636::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a0c:9a46:637::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a10:4741:33::/48 | Valid | Other IRR onlyRADB | 633 100% |
| 2a10:4741:36::/48 | Valid | Other IRR onlyRADB | 633 100% |
| 2a10:4741:32::/48 | Valid | RIR databaseRADB, RIPE | 633 100% |
| 2a10:4741:34::/48 | Valid | RIR databaseRADB, RIPE | 633 100% |
| 2a10:4741:35::/48 | Valid | RIR databaseRADB, RIPE | 633 100% |
| 2a10:4741:37::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS208914: AS208914:AS-ALL. 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 (AS208914 isn't in the set, or no route object for AS208914 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 | AS208914 in it | Not covered |
|---|---|---|---|---|---|
| AS208914:AS-ALL | RIPE | 1 | 1 | Yes | 0 |
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 15 are in fix.csv.
- Route object: RIR8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2a0c:9a46:632::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0c:9a46:633::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0c:9a46:634::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0c:9a46:635::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0c:9a46:636::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0c:9a46:637::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a10:4741:33::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a10:4741:36::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208914 whose prefix no peer sees AS208914 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0c:9a46:600::/40 | RIPE | Valid |
| 2a10:4741:21::/48 | RIPE | Invalid: origin |
| 2a10:4741:30::/44 | RIPE | Invalid: origin |
| 2a10:4741:30::/48 | RIPE | Invalid: origin |
| 2a10:4741:31::/48 | RIPE | Invalid: origin |
| 2a10:4741:38::/48 | RIPE | Invalid: origin |
| 2a10:4741:39::/48 | RIPE | Invalid: origin |
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.