Home ASN LookupAS35367

AS35367 bilesim BILESIM FINANSAL TEKNOLOJILER VE ODEME SISTEMLERI A.S.

🇹🇷

Org handle: ORG-BADK1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

4 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)2,304

Announced (BGP)1,280

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇹🇷 TR

RIR

RIPE NCC

Status

allocated

Allocated

2019-09-19

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
45.155.72.0/23	Valid	RIPE	-
45.155.74.0/24	Valid	RIPE	-
45.155.75.0/24	Valid	RIPE	-
176.236.247.0/24	Valid	RIPE	-

Allocated Prefixes

(RIR)6

Prefix	Country	RIR	Status
45.155.72.0/22	🇹🇷 TR	RIPENCC	allocated
45.155.72.0/23	🇹🇷 TR	RIPE	assigned
45.155.74.0/24	🇹🇷 TR	RIPE	assigned
45.155.75.0/24	🇹🇷 TR	RIPE	assigned
176.236.247.0/24	🇹🇷 TR	RIPE	assigned
2a0f:b900::/29	🇹🇷 TR	RIPENCC	allocated

All 4 announced prefixes of AS35367 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS9121TTNet Turk Telekomunikasyon Anonim Sirketi2
AS34984TELLCOM Superonline Iletisim Hizmetleri A.S2

Transfer History

Registry transfers of AS35367 between organisations.

AS35367M&A · 2017-12-07
Sony DADC Austria GmbH
RIPE NCC
→
Sony DADC Europe Limited
RIPE NCC

Date	Resource	From	To	Type
2017-12-07	AS35367	Sony DADC Austria GmbH RIPE NCC	Sony DADC Europe Limited RIPE NCC	M&A

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

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 AS35367 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

Open

GEThttps://api.ipctl.io/v1/asn/35367

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

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