AS56814 T2TELECOM-AS M2 CONNECT LLC

🇷🇺

Org handle: ORG-TTL45-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

7total

5 IPv42 IPv6

IPv4 Addresses

Allocated (RIR)2,304

Announced (BGP)2,304

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)9.5×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2021-03-02

Announced Prefixes

(BGP)7

Prefix	RPKI	IRR	Last Seen
5.11.60.0/23	Valid	RIPE	2026-10-11
5.11.62.0/23	Valid	RIPE	2026-10-11
193.163.3.0/24	Valid	RIPE	2026-10-11
193.243.172.0/23	Valid	RIPE	2026-10-11
194.110.52.0/23	Valid	RIPE	2026-10-11
2a09:6880::/29	Valid	RIPE	2026-10-11
2a09:6880::/30	Valid	RIPE	2026-10-11

(RIR)6

Prefix	Country	RIR	Status
5.11.60.0/23	🇷🇺 RU	RIPE	assigned
5.11.62.0/23	🇷🇺 RU	RIPE	assigned
193.163.3.0/24	🇷🇺 RU	RIPENCC	allocated
193.243.172.0/23	🇷🇺 RU	RIPENCC	allocated
194.110.52.0/23	🇷🇺 RU	RIPENCC	allocated
2a09:6880::/29	🇷🇺 RU	RIPENCC	allocated

(seen in AS paths)

Networks AS56814 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

Abuse Contact

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS56814 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/56814" | jq