Home Prefix Lookup2a02:2698:9800::/38

2a02:2698:9800::/38 - MOSCOW JSC "ER Telecom Holding" (AS31363)

IPv6RIPEassignedAS31363MOSCOW-AS JSC "ER-Telecom Holding" RPKI Valid

CIDR

2a02:2698:9800::/38

IP Version

IPv6

Addresses

1237.9Y

Mask

/38

Country

🇷🇺 Russia

City

Moscow

RIR

RIPE

Status

assigned

Allocated

Announced BGP Routes

1 of 1 route

RPKI:

IRR:

Swipe sideways to see all columns →

Prefix	Origin AS	RPKI	IRR	Last Seen
2a02:2698:9800::/38	AS31363 MOSCOW-AS JSC "ER-Telecom Holding"	Valid	RIPE	2026-10-11

More-Specific Announcements

4 more-specific announcements

Prefix	Origin AS	RPKI	IRR	Last Seen
2a02:2698:982a::/48	AS31363 MOSCOW-AS JSC "ER-Telecom Holding"	Valid	-	2026-10-11
2a02:2698:982b::/48	AS31363 MOSCOW-AS JSC "ER-Telecom Holding"	Valid	-	2026-10-11
2a02:2698:982c::/48	AS31363 MOSCOW-AS JSC "ER-Telecom Holding"	Valid	-	2026-10-11
2a02:2698:982d::/48	AS31363 MOSCOW-AS JSC "ER-Telecom Holding"	Valid	-	2026-10-11

RPKI ROAs

Prefix	Origin	Max Length	Trust Anchor
2a02:2698:9800::/38	AS31363	/48	ripe

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS31363	RIPE	RAID-MNT	2020-07-21

Origin ASN

AS31363

MOSCOW-AS JSC "ER-Telecom Holding"

Related Prefixes

More prefixes of AS31363

All prefixes of AS31363 →

Geolocation

Country🇷🇺RussiaRU

RegionMoscow

CityMoscow

Coordinates55.7558, 37.6173 ↗

Abuse Contact

Learn more

RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
RPKI validatorCheck ROA coverage for any prefix or ASN
What is BGP?How prefixes are announced and routed
More-specific prefixesGlossary: covering and more-specific routes
IPv4 transfer marketTransfers published by all five RIRs

API

Open

GEThttps://api.ipctl.io/v1/prefix/2a02:2698:9800::/38

Returns prefix allocation, BGP routes, and more-specific subnets.

curl -s "https://api.ipctl.io/v1/prefix/2a02:2698:9800::/38" | jq

External Links

RIPEstat