asn.dev

Routing security

AS210656 YACLOUDBMS

Unclassified RIPE

RPKI valid 100% 9 of 9 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 13 authorising this AS

Announcements

What this network originates

9 observed

Every prefix observed with AS210656 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
89.223.6.0/23RPKI validIRR54
89.223.20.0/24RPKI validIRR54
92.255.16.0/24RPKI validIRR54
92.255.58.0/23RPKI validIRR54
94.126.204.0/22RPKI validIRR54
94.139.248.0/22RPKI validIRR54
185.184.128.0/22RPKI validIRR54
185.216.194.0/23RPKI validIRR54
201.50.118.0/24RPKI validIRR54

RPKI · ROAs

Route origin authorisations

13 ROAs

Signed statements by address holders that AS210656 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
46.243.218.0/23/32RIPENCC
89.223.6.0/23/32RIPENCC
89.223.20.0/24/32RIPENCC
92.255.16.0/24/32RIPENCC
92.255.58.0/23/32RIPENCC
94.126.204.0/22/32RIPENCC
94.139.248.0/22/32RIPENCC
185.184.128.0/22/32RIPENCC
185.216.194.0/23/32RIPENCC
186.246.15.0/24/24RIPENCC
201.50.118.0/24/24RIPENCC
2a0d:d6c2::/48/48RIPENCC
2a0d:d6c7:3::/48/48RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

13 objects · 4 not announced

Route objects naming AS210656 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.

PrefixSourceDescriptionMaintainerChangedRouting
46.243.218.0/23RIPE—MNT-RU-YANDEXCLOUD-12026-10-22Not announced
186.246.15.0/24RIPE—TIMEWEB-MNT2026-05-06Not announced
2a0d:d6c2::/48RIPE—MNT-RU-YANDEXCLOUD-12024-05-24Not announced
2a0d:d6c7:3::/48RIPE—MNT-RU-YANDEXCLOUD-12024-03-28Not announced
89.223.6.0/23RIPE—MNT-RU-YANDEXCLOUD-12026-07-20Announced
89.223.20.0/24RIPE—MNT-RU-YANDEXCLOUD-12024-01-11Announced
92.255.16.0/24RIPE—MNT-RU-YANDEXCLOUD-12026-06-03Announced
92.255.58.0/23RIPE—MNT-RU-YANDEXCLOUD-12026-01-19Announced
94.126.204.0/22RIPE—MNT-RU-YANDEXCLOUD-12024-09-13Announced
94.139.248.0/22RIPE—MNT-RU-YANDEXCLOUD-12024-09-13Announced
185.184.128.0/22RIPE—MNT-RU-YANDEXCLOUD-12026-03-18Announced
185.216.194.0/23RIPE—MNT-RU-YANDEXCLOUD-12026-05-08Announced
201.50.118.0/24RIPE—IP-RIPE2026-07-01Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS210656 directly show who expects to carry it.

AS-setWhereRelationship
AS-RETN-ACTUAL-V4RIPELists AS210656 as a direct member
AS-TRANSROUTE-SPECRIPELists AS210656 as a direct member
AS-YACLOUDRIPELists AS210656 as a direct member
AS210656:AS-YACLOUDBMSRIPELists AS210656 as a direct member
AS41194:AS-RASCOMRIPELists AS210656 as a direct member

RPKI from rpki-client, validated 2026-10-30 12:03 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-30. Cross-check on bgp.he.net.