Routing security
AS219074 FENECON-ASN Fenecon GmbH
Unclassified RIPE Enterprise
Announcements
What this network originates
Every prefix observed with AS219074 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 185.145.190.0/24 | RPKI valid | IRR | 57 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS219074 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 185.145.190.0/24 | /24 | RIPENCC |
| 2a0b:e880::/32 | /32 | 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 |
|---|---|---|---|
| AS24940 | Hetzner Online GmbH | 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 AS219074 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 |
|---|---|---|---|---|---|
| 2a0b:e880::/32 | RIPE | — | FENECON-MNT | 2026-08-04 | Not announced |
| 185.145.190.0/24 | RIPE | — | FENECON-MNT | 2026-08-20 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS219074 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS219074:AS-FENECON | PeeringDB | Declared by the operator as its own set |
AS219074:AS-FENECON | RIPE | Lists AS219074 as a direct member |
RPKI from rpki-client, validated 2026-11-02 13:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-02. Cross-check on bgp.he.net.