Routing security
AS41157 OXYMIUM
Hosting RIPE Content
Announcements
What this network originates
Every prefix observed with AS41157 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a0f:3400:500::/40 | RPKI valid | IRR | 34 |
| 81.201.178.0/24 | RPKI valid | IRR | 54 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS41157 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 81.201.178.0/24 | /24 | RIPENCC |
| 2a0f:3400:500::/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.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS47160 | MOJI SAS | Declared | not observed |
| AS62000 | SERVERD SAS | Declared | Observed |
| AS6939 | Hurricane Electric LLC | not declared | Observed |
| AS204092 | Association GRIFON | not declared | Observed |
| AS6696 | VERIXI SA | not 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 AS41157 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 |
|---|---|---|---|---|---|
| 2a02:2218::/29 | RIPE | Oxymium iPv6 PA Sup | MNT-OXYMIUM | 2019-11-28 | Not announced |
| 2a02:2218::/32 | RIPE | Oxymium iPv6 PA | MNT-OXYMIUM | 2010-08-06 | Not announced |
| 81.201.178.0/24 | RIPE | — | MNT-MOJI | 2026-09-25 | Announced |
| 2a0f:3400:500::/40 | RIPE | — | MNT-MOJI | 2026-09-23 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS41157 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS41157:AS-NINE-IX-EDGE-CACHE | PeeringDB | Declared by the operator as its own set |
AS-BLUENETECH-LILLIX-PEERS | RIPE | Lists AS41157 as a direct member |
AS-BLUENETECH-PEERS | RIPE | Lists AS41157 as a direct member |
AS-BLUENETECH-SFINX-PEERS | RIPE | Lists AS41157 as a direct member |
AS-FRANCEIX-PAR | RIPE | Lists AS41157 as a direct member |
AS-FRANCEIX-PAR-LIST | RIPE | Lists AS41157 as a direct member |
AS-NETRIX | RIPE | Lists AS41157 as a direct member |
AS-OXYMIUM | RIPE | Lists AS41157 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS41157 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS41157 as a direct member |
AS-SFINX-MEMBERS | RIPE | Lists AS41157 as a direct member |
AS-TELICITY-PEERING-FRANCE-IX | RIPE | Lists AS41157 as a direct member |
AS-TOPIX-RS | RIPE | Lists AS41157 as a direct member |
AS29169:AS-PEERS4 | RIPE | Lists AS41157 as a direct member |
AS29169:AS-PEERS6 | RIPE | Lists AS41157 as a direct member |
AS43100:AS-MEMBERS:AS-LYN-RS | RIPE | Lists AS41157 as a direct member |
AS47841:AS-OPEN-PEERING | RIPE | Lists AS41157 as a direct member |
AS51706:AS-MEMBERS | RIPE | Lists AS41157 as a direct member |
AS51706:AS-MEMBERS:AS-PAR-RS | RIPE | Lists AS41157 as a direct member |
AS62443:AS-MEMBERS | RIPE | Lists AS41157 as a direct member |
RPKI from rpki-client, validated 2026-10-27 12:06 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-27. Cross-check on bgp.he.net.