Routing security
AS42403
Unclassified RIPE Route Server
Announcements
What this network originates
Every prefix observed with AS42403 as its origin, checked against RPKI and the IRR. Problems sort first.
No announcements from this network were observed in the routing snapshot.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS42403 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 195.209.16.0/24 | /24 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS42403 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 |
|---|---|---|---|---|---|
| 195.209.16.0/24 | RIPE | MSK-IX Novosibirsk | AS3316-MNT | 2015-08-20 | Not announced |
| 2001:6d0:ffb8::/48 | RIPE | — | RUIX-MNT | 2019-12-25 | Not announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS42403 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-NSKROUTESERVER | PeeringDB | Declared by the operator as its own set |
AS-CONNECTA | RIPE | Lists AS42403 as a direct member |
AS-RELARN | RIPE | Lists AS42403 as a direct member |
AS25091:AS-ROUTESERVERS | RIPE | Lists AS42403 as a direct member |
RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.