Routing security
AS47160 MOJI
Residential RIPE
Announcements
What this network originates
Every prefix observed with AS47160 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 195.190.1.0/24 | No ROA | IRR | 53 |
| 2a0f:3400::/40 | RPKI valid | IRR | 32 |
| 2a0f:3400:200::/40 | RPKI valid | IRR | 32 |
| 2a06:c480::/29 | RPKI valid | IRR | 32 |
| 2a06:c480::/32 | RPKI valid | IRR | 32 |
| 2a06:c481::/32 | RPKI valid | IRR | 32 |
| 2a06:c484::/30 | RPKI valid | IRR | 32 |
| 31.14.68.0/22 | RPKI valid | IRR | 53 |
| 45.112.120.0/24 | RPKI valid | IRR | 52 |
| 45.112.122.0/24 | RPKI valid | IRR | 53 |
| 45.147.208.0/22 | RPKI valid | IRR | 53 |
| 81.201.176.0/22 | RPKI valid | IRR | 53 |
| 87.236.35.0/24 | RPKI valid | IRR | 53 |
| 176.124.40.0/22 | RPKI valid | IRR | 53 |
| 185.126.228.0/22 | RPKI valid | IRR | 52 |
| 185.126.229.0/24 | RPKI valid | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS47160 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 31.14.68.0/22 | /24 | RIPENCC |
| 45.112.120.0/23 | /24 | RIPENCC |
| 45.112.122.0/24 | /24 | RIPENCC |
| 45.147.208.0/22 | /24 | RIPENCC |
| 81.201.176.0/22 | /22 | RIPENCC |
| 81.201.180.0/24 | /24 | RIPENCC |
| 87.236.35.0/24 | /24 | RIPENCC |
| 176.124.40.0/22 | /24 | RIPENCC |
| 185.126.228.0/22 | /24 | RIPENCC |
| 2a06:c480::/29 | /48 | RIPENCC |
| 2a0f:3400::/29 | /48 | RIPENCC |
| 2a0f:3400::/40 | /40 | RIPENCC |
| 2a0f:3400:200::/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 |
|---|---|---|---|
| AS174 | Cogent Communications, LLC | Declared | not observed |
| AS3257 | GTT Communications Inc. | Declared | not observed |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Declared | not observed |
| AS6461 | Zayo Bandwidth | Declared | not observed |
| AS9002 | RETN Limited | Declared | not observed |
| AS62000 | SERVERD SAS | 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 AS47160 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 |
|---|---|---|---|---|---|
| 81.201.180.0/22 | RIPE | — | OXY-MNT | 2026-07-02 | Not announced |
| 159.100.42.0/24 | RIPE | — | INTERPC-MNT | 2026-01-21 | Not announced |
| 159.100.43.0/24 | RIPE | — | INTERPC-MNT | 2026-01-21 | Not announced |
| 159.100.44.0/24 | RIPE | — | INTERPC-MNT | 2026-01-21 | Not announced |
| 185.126.228.0/24 | RIPE | MOJI FTTO Enterprise - Paris | MNT-MOJI | 2025-11-23 | Not announced |
| 185.126.230.0/24 | RIPE | — | MNT-MOJI | 2025-11-24 | Not announced |
| 185.126.231.0/24 | RIPE | — | MNT-MOJI | 2025-11-24 | Not announced |
| 2a0f:3400::/29 | RIPE | MOJI FTTO Enterprise | MNT-MOJI | 2024-10-11 | Not announced |
| 31.14.68.0/22 | RIPE | MOJI FTTO Enterprise - Paris | MNT-MOJI | 2024-10-11 | Announced |
| 45.112.120.0/24 | RIPE | MOJI FTTO Enterprise - Lyon | MNT-FR-MOJISERVICES-1 | 2024-10-11 | Announced |
| 45.112.122.0/24 | RIPE | MOJI FTTO Enterprise - Paris | MNT-FR-MOJISERVICES-1 | 2024-10-11 | Announced |
| 45.147.208.0/22 | RIPE | MOJI FTTO Enterprise - Paris | MNT-FR-MOJISERVICES-1 | 2024-10-11 | Announced |
| 81.201.176.0/22 | RIPE | — | MNT-MOJI | 2026-08-13 | Announced |
| 87.236.35.0/24 | RIPE | — | MNT-MOJI | 2023-11-07 | Announced |
| 176.124.40.0/22 | RIPE | — | MNT-FR-MOJISERVICES-1 | 2023-10-30 | Announced |
| 185.126.228.0/22 | RIPE | MOJI FTTO Enterprise - Paris | MNT-FR-MOJISERVICES-1 | 2024-10-11 | Announced |
| 185.126.229.0/24 | RIPE | — | MNT-MOJI | 2025-11-24 | Announced |
| 195.190.1.0/24 | RIPE | IHS GLOBAL SP. Z O.O. | NETIA-MNT | 2012-11-22 | Announced |
| 2a06:c480::/29 | RIPE | — | MNT-MOJI | 2023-11-07 | Announced |
| 2a06:c480::/32 | RIPE | — | MNT-MOJI | 2024-10-30 | Announced |
| 2a06:c481::/32 | RIPE | — | MNT-MOJI | 2024-10-30 | Announced |
| 2a06:c484::/30 | RIPE | — | MNT-MOJI | 2024-10-30 | Announced |
| 2a0f:3400::/40 | RIPE | — | MNT-MOJI | 2024-10-30 | Announced |
| 2a0f:3400:200::/40 | RIPE | — | MNT-MOJI | 2025-02-14 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS47160 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-RETN-ACTUAL-V4 | RIPE | Lists AS47160 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS47160 as a direct member |
AS12897:AS-AMSIX-RS-PEERS | RIPE | Lists AS47160 as a direct member |
AS47160:AS-MOJI | RIPE | Lists AS47160 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.