Routing security
AS205669 RESEL Association ResEl
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS205669 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a00:5881:30c0::/44 | RPKI valid | IRR | 31 |
| 2a00:5881:3040::/44 | RPKI valid | IRR | 34 |
| 2a00:5881:3080::/44 | RPKI valid | IRR | 33 |
| 89.234.160.0/24 | RPKI valid | IRR | 54 |
| 89.234.161.0/24 | RPKI valid | IRR | 54 |
| 89.234.162.0/24 | RPKI valid | IRR | 54 |
| 89.234.163.0/24 | RPKI valid | IRR | 54 |
| 89.234.164.0/24 | RPKI valid | IRR | 54 |
| 89.234.165.0/24 | RPKI valid | IRR | 54 |
| 89.234.166.0/24 | RPKI valid | IRR | 54 |
| 89.234.167.0/24 | RPKI valid | IRR | 54 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS205669 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 89.234.160.0/21 | /24 | RIPENCC |
| 2a00:5881:3040::/44 | /44 | RIPENCC |
| 2a00:5881:3080::/44 | /44 | RIPENCC |
| 2a00:5881:30c0::/44 | /44 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS47160 | MOJI SAS | Declared | Observed |
| AS198507 | IELO-LIAZO SERVICES SAS | Declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS205669 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 89.234.160.0/21 | RIPE | Route for ResEl main IPv4 | OPDOP-MNT | 2024-04-12 | Not announced |
| 2a00:5881:3000::/40 | RIPE | Route for ResEl main IPv6 | RESEL-MNT | 2025-09-23 | Not announced |
| 2a06:e044:10::/48 | RIPE | Route to ResEl Rennes | QUANTIC-MNT | 2020-08-16 | Not announced |
| 2a06:e044:12::/48 | RIPE | Route to ResEl Brest | QUANTIC-MNT | 2020-08-16 | Not announced |
| 89.234.160.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.161.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.162.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.163.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.164.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.165.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.166.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 89.234.167.0/24 | RIPE | — | RESEL-MNT | 2024-04-12 | Announced |
| 2a00:5881:3040::/44 | RIPE | Route for ResEl Brest IPv6 | RESEL-MNT | 2025-09-23 | Announced |
| 2a00:5881:3080::/44 | RIPE | Route for ResEl Rennes IPv6 | RESEL-MNT | 2025-09-23 | Announced |
| 2a00:5881:30c0::/44 | RIPE | Route for ResEl Nantes IPv6 | RESEL-MNT | 2025-09-23 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS205669 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-HURRICANEV6 | RADB | Lists AS205669 as a direct member |
AS-RESEL | RIPE | Lists AS205669 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS205669 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS205669 as a direct member |
AS205669:AS-MEMBERS | RIPE | Lists AS205669 as a direct member |
RPKI from rpki-client, validated 2026-11-04 19:18 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-04. Cross-check on bgp.he.net.