Routing security
AS39910 ASPERIQ
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS39910 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a10:7a40::/29 | RPKI valid | IRR | 1 |
| 2a10:7a40:a::/48 | RPKI valid | IRR | 1 |
| 2a10:7a40:b::/48 | RPKI valid | IRR | 31 |
| 80.244.9.0/24 | RPKI valid | IRR | 52 |
| 185.203.90.0/24 | RPKI valid | IRR | 1 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS39910 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 80.244.9.0/24 | /24 | RIPENCC |
| 185.203.90.0/24 | /24 | RIPENCC |
| 2a10:7a40::/29 | /48 | 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 |
|---|---|---|---|
| AS174 | Cogent Communications, LLC | Declared | not observed |
| AS58299 | Openfactory GmbH | Declared | Observed |
| AS39351 | 31173 Services AB | not 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 AS39910 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 |
|---|---|---|---|---|---|
| 2a10:7a40::/32 | RIPE | — | ASPERIQ-MNT | 2020-10-07 | Not announced |
| 2a10:7a40::/48 | RIPE | Asperiq6-Anycast | ASPERIQ-MNT | 2020-10-09 | Not announced |
| 2a10:7a40:1::/48 | RIPE | Asperiq6-Baar | ASPERIQ-MNT | 2022-11-23 | Not announced |
| 2a10:7a40:2::/48 | RIPE | Asperiq6-Lund | ASPERIQ-MNT | 2020-10-09 | Not announced |
| 80.244.9.0/24 | RIPE | — | ASPERIQ-MNT | 2024-11-14 | Announced |
| 185.203.90.0/24 | RIPE | — | ASPERIQ-MNT | 2020-10-07 | Announced |
| 2a10:7a40::/29 | RIPE | — | ASPERIQ-MNT | 2023-03-24 | Announced |
| 2a10:7a40:a::/48 | RIPE | Asperiq6-A | ASPERIQ-MNT | 2020-11-03 | Announced |
| 2a10:7a40:b::/48 | RIPE | Asperiq6-B Lund | ASPERIQ-MNT | 2022-11-22 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS39910 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-ASPERIQ | RIPE | Lists AS39910 as a direct member |
AS-BALKANIX | RIPE | Lists AS39910 as a direct member |
AS-ESAB | RIPE | Lists AS39910 as a direct member |
AS-HURRICANE | RADB | Lists AS39910 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS39910 as a direct member |
AS-NETIX | RIPE | Lists AS39910 as a direct member |
AS-NETIX-NET | RIPE | Lists AS39910 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS39910 as a direct member |
AS57463:AS-NETIX-NET | RIPE | Lists AS39910 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.