Routing security
AS200949 EPPO
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS200949 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 185.46.239.0/24 | RPKI valid | IRR | 56 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS200949 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 185.46.239.0/24 | /25 | RIPENCC |
| 2a0a:6040:d800::/40 | /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.
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 AS200949 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 |
|---|---|---|---|---|---|
| 185.46.239.0/24 | RIPE | — | LIR-LU-EPPO1-1-MNT | 2026-03-04 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS200949 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLNET | APNIC | Lists AS200949 as a direct member |
AS-HURRICANE | RADB | Lists AS200949 as a direct member |
AS-PTLU | RIPE | Lists AS200949 as a direct member |
AS200949:AS-SET | RIPE | Lists AS200949 as a direct member |
AS212483:AS-CUSTOMERS | ALTDB | Lists AS200949 as a direct member |
AS6661:AS-NS | RIPE | Lists AS200949 as a direct member |
RPKI from rpki-client, validated 2026-10-16 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-16. Cross-check on bgp.he.net.