Routing security
AS39728 LUGANET
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS39728 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 45.152.24.0/22 | RPKI valid | IRR | 52 |
| 91.217.4.0/23 | RPKI valid | IRR | 57 |
| 91.217.5.0/24 | RPKI valid | IRR | 52 |
| 176.113.224.0/19 | RPKI valid | IRR | 57 |
| 176.113.224.0/24 | RPKI valid | IRR | 52 |
| 176.113.225.0/24 | RPKI valid | IRR | 52 |
| 176.113.241.0/24 | RPKI valid | IRR | 52 |
| 176.113.255.0/24 | RPKI valid | IRR | 52 |
| 178.214.160.0/19 | RPKI valid | IRR | 57 |
| 178.214.161.0/24 | RPKI valid | IRR | 52 |
| 178.214.183.0/24 | RPKI valid | IRR | 52 |
| 178.216.232.0/21 | RPKI valid | IRR | 57 |
| 185.149.196.0/22 | RPKI valid | IRR | 52 |
| 185.178.245.0/24 | RPKI valid | IRR | 52 |
| 194.31.152.0/22 | RPKI valid | IRR | 57 |
| 194.31.155.0/24 | RPKI valid | IRR | 52 |
| 195.8.56.0/24 | RPKI valid | IRR | 57 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS39728 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 45.152.24.0/22 | /22 | RIPENCC |
| 45.152.27.0/24 | /24 | RIPENCC |
| 91.217.4.0/23 | /24 | RIPENCC |
| 176.113.224.0/19 | /24 | RIPENCC |
| 178.214.160.0/19 | /24 | RIPENCC |
| 178.216.232.0/21 | /21 | RIPENCC |
| 185.149.196.0/22 | /22 | RIPENCC |
| 185.178.245.0/24 | /24 | RIPENCC |
| 185.178.246.0/24 | /24 | RIPENCC |
| 194.31.152.0/22 | /24 | RIPENCC |
| 195.8.56.0/23 | /24 | RIPENCC |
| 2a07:6900::/48 | /48 | RIPENCC |
| 2a07:6900:1::/48 | /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 |
|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Declared | Observed |
| AS12389 | PJSC Rostelecom | Declared | not observed |
| AS31500 | Global Network Management Inc | Declared | Observed |
| AS41039 | Timer, LLC | Declared | not observed |
| AS50509 | Transroute Telecom LTD | Declared | Observed |
| AS198310 | OOO Molniya | Declared | Observed |
| AS201706 | SERVICEPIPE LLC | Declared | Observed |
| AS24482 | SG.GS | not declared | Observed |
| AS37721 | Virtual Technologies & Solutions | not declared | Observed |
| AS49673 | Truenetwork LLC | not declared | Observed |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | 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 AS39728 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 |
|---|---|---|---|---|---|
| 91.217.4.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Not announced |
| 176.113.245.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Not announced |
| 176.113.246.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-03-04 | Not announced |
| 176.113.247.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Not announced |
| 185.178.246.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2024-03-11 | Not announced |
| 195.8.57.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Not announced |
| 2a07:6900::/48 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Not announced |
| 45.152.24.0/22 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-04-16 | Announced |
| 91.217.4.0/23 | RIPE | — | ARTA-MNT | 2023-06-21 | Announced |
| 91.217.5.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 176.113.224.0/19 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 176.113.224.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-03-18 | Announced |
| 176.113.225.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 176.113.241.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 176.113.255.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-03-25 | Announced |
| 178.214.160.0/19 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Announced |
| 178.214.161.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 178.214.183.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 178.216.232.0/21 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Announced |
| 185.149.196.0/22 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Announced |
| 185.178.245.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 194.31.152.0/22 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Announced |
| 194.31.155.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2026-02-25 | Announced |
| 195.8.56.0/24 | RIPE | — | MNT-RU-LIKHNO-1 | 2025-12-16 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS39728 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-BLOCK-SET | RIPE | Lists AS39728 as a direct member |
AS-BLOCKED-RU | RIPE | Lists AS39728 as a direct member |
AS-HURRICANE | RADB | Lists AS39728 as a direct member |
AS-IRIS-GTS | RIPE | Lists AS39728 as a direct member |
AS-LTC | RIPE | Lists AS39728 as a direct member |
AS-LUGANET | RIPE | Lists AS39728 as a direct member |
AS-PROMTELECOM | RIPE | Lists AS39728 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS39728 as a direct member |
AS-SERVICEPIPE | RIPE | Lists AS39728 as a direct member |
AS-SET-TELE-MATIKA | RIPE | Lists AS39728 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS39728 as a direct member |
AS-UAIS | RIPE | Lists AS39728 as a direct member |
AS198310:AS-MOLNIYA | RIPE | Lists AS39728 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS39728 as a direct member |
RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.