AS35703 NO-TV2-AS TV 2 AS

🇳🇴

Org handle: ORG-TA151-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

3 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)3.9×10²⁸

Announced (BGP)3.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2005-10-07

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
77.75.208.0/21	Valid	RIPE	2026-10-11
193.160.156.0/23	Valid	RIPE	2026-10-11
193.227.204.0/23	Valid	RIPE	2026-10-11
2a00:e48::/33	Valid	RIPE	2026-10-11

(RIR)4

Prefix	Country	RIR	Status
77.75.208.0/21	🇳🇴 NO	RIPENCC	allocated
193.160.156.0/23	🇳🇴 NO	RIPENCC	assigned
193.227.204.0/23	🇳🇴 NO	RIPENCC	assigned
2a00:e48::/33	🇳🇴 NO	RIPE	assigned

(seen in AS paths)

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

ASPA

No ASPA

Abuse Contact

+31205354444

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 AS35703 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/35703" | jq