Routing security
AS207304 Y-KZ Y. Izdeu men Jarnama LLP
Unclassified APNIC
Announcements
What this network originates
Every prefix observed with AS207304 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a14:48c5::/48 | RPKI valid | IRR | 29 |
| 45.138.0.0/24 | RPKI valid | IRR | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS207304 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 5.45.213.0/24 | /24 | RIPENCC |
| 5.45.215.0/24 | /24 | RIPENCC |
| 45.138.0.0/24 | /24 | RIPENCC |
| 2a02:6b8:b::/48 | /48 | RIPENCC |
| 2a02:6b8:215::/48 | /48 | RIPENCC |
| 2a14:48c5::/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 |
|---|---|---|---|
| AS13238 | YANDEX LLC | Declared | Observed |
| AS41798 | JSC Transtelecom | Declared | not observed |
| AS208398 | Edge Technology Plus d.o.o. Beograd | 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 AS207304 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 |
|---|---|---|---|---|---|
| 5.45.215.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2026-02-05 | Not announced |
| 2a02:6b8:b::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-11 | Not announced |
| 2a02:6b8:215::/48 | RIPE | Yandex network | YANDEX-MNT | 2026-02-04 | Not announced |
| 45.138.0.0/24 | RIPE | — | LIR-AE-DIRECTCURSUS-1-MNT | 2025-07-11 | Announced |
| 2a14:48c5::/48 | RIPE | — | LIR-AE-DIRECTCURSUS-1-MNT | 2025-07-11 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS207304 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-4IXP | RIPE | Lists AS207304 as a direct member |
AS-4IXP-RS | RIPE | Lists AS207304 as a direct member |
AS-50710 | RIPE | Lists AS207304 as a direct member |
AS-NT | RIPE | Lists AS207304 as a direct member |
AS-ROZINT-DOWNSTREAM | ARIN | Lists AS207304 as a direct member |
AS-TRANSKZ | RIPE | Lists AS207304 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS207304 as a direct member |
AS-YANDEX | RIPE | Lists AS207304 as a direct member |
AS208398:AS-TELETECH | RIPE | Lists AS207304 as a direct member |
RPKI from rpki-client, validated 2026-11-15 12:58 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-15. Cross-check on bgp.he.net.