Home Prefix Lookup2a02:bf0:3000::/36

2a02:bf0:3000::/36 - MTSBY Mobile TeleSystems JLLC (AS25106)

IPv6RIPEassignedAS25106MTSBY-AS Mobile TeleSystems JLLC RPKI Valid

CIDR

2a02:bf0:3000::/36

IP Version

IPv6

Addresses

4951.7Y

Mask

/36

Country

🇧🇾 Belarus

City

Minsk

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:bf0:3000::/36	AS25106 MTSBY-AS Mobile TeleSystems JLLC	Valid	RIPE	2026-10-11

Related Announcements

1 less-specific, 3 more-specific announcements

Prefix	Origin AS	RPKI	IRR	Last Seen
2a02:bf0::/32	AS25106 MTSBY-AS Mobile TeleSystems JLLC	Valid	-	2026-10-11
2a02:bf0:3200::/44	AS25106 MTSBY-AS Mobile TeleSystems JLLC	Valid	-	2026-10-11
2a02:bf0:3220::/44	AS25106 MTSBY-AS Mobile TeleSystems JLLC	Valid	-	2026-10-11
2a02:bf0:3230::/44	AS25106 MTSBY-AS Mobile TeleSystems JLLC	Valid	-	2026-10-11

RPKI ROAs

Prefix	Origin	Max Length	Trust Anchor
2a02:bf0:3000::/36	AS25106	/44	ripe
2a02:bf0::/32	AS25106	/32	ripe

IRR Route Objects

Origin	Registry	Maintainer	Modified
AS25106	RIPE	MTSBY-MNT	2015-01-13

Origin ASN

AS25106

MTSBY-AS Mobile TeleSystems JLLC

Related Prefixes

Covering prefix

2a02:bf0::/32AS25106

More prefixes of AS25106

All prefixes of AS25106 →

Geolocation

Country🇧🇾BelarusBY

RegionMinsk City

CityMinsk

Coordinates53.9006, 27.5590 ↗

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:bf0:3000::/36

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

curl -s "https://api.ipctl.io/v1/prefix/2a02:bf0:3000::/36" | jq

External Links

RIPEstat