Routing security
AS201376 Association AuvernIX
Unclassified RIPE Route Server
Announcements
What this network originates
Every prefix observed with AS201376 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 AS201376 may originate these prefixes, up to the maximum length shown.
No ROA names this AS as an authorised origin.
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 |
|---|---|---|---|
| AS0 | unnamed | Declared | not 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 AS201376 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.1.2.0/24 | RIPE | AuvernIX LAN Prefix IPv4 | AUVERNIX-MNT | 2020-08-11 | Not announced |
| 2001:7f8:81::/48 | RIPE | AuvernIX LAN Prefix IPv6 | AUVERNIX-MNT | 2020-08-11 | Not announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS201376 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS201376:AS-MEMBERS | PeeringDB | Declared by the operator as its own set |
RPKI from rpki-client, validated 2026-10-11 12:23 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-11. Cross-check on bgp.he.net.