Routing security
AS218591 BYTEHOST Aaron Janssen
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS218591 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a09:3f00:1010::/48 | RPKI valid | IRR | 36 |
| 94.249.201.0/24 | RPKI valid | IRR | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS218591 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 94.249.201.0/24 | /24 | RIPENCC |
| 2a09:3f00:1010::/48 | /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 |
|---|---|---|---|
| AS214915 | Jan Smyrek | 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 AS218591 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 |
|---|---|---|---|---|---|
| 94.249.201.0/24 | RIPE | — | GHOSTNET-MNT | 2026-09-30 | Announced |
| 2a09:3f00:1010::/48 | RIPE | — | BYTEHOST-MNT | 2026-09-28 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS218591 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-HURRICANEV6 | RADB | Lists AS218591 as a direct member |
AS214915:AS-PAWHOST | RIPE | Lists AS218591 as a direct member |
RPKI from rpki-client, validated 2026-11-01 13:04 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-01. Cross-check on bgp.he.net.