Network · data from 2026-11-12

AS47952 ICTBULUT ICT BULUT BILISIM A.S.

Registry name: ICTBULUT ICT BULUT BILISIM A.S., TR · not in PeeringDB

60IPv4 routes 100.0% RPKI valid · 98.3% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

6Route objects not announced registered with origin AS47952, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47952, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


81.200.140.0/24	Valid	None	672 100%	66
81.200.143.0/24	Valid	RIR databaseRIPE	673 100%	68
91.194.52.0/24	Valid	RIR databaseRIPE	673 100%	67
153.56.138.0/24	Valid	RIR databaseRIPE	673 100%	67
185.201.212.0/24	Valid	RIR databaseRIPE	673 100%	67
185.201.213.0/24	Valid	RIR databaseRIPE	673 100%	67
185.201.214.0/24	Valid	RIR databaseRIPE	673 100%	67
185.201.215.0/24	Valid	RIR databaseRIPE	673 100%	67
193.35.207.0/24	Valid	RIR databaseRIPE	673 100%	67
194.56.184.0/24	Valid	RIR databaseRIPE	673 100%	67
194.56.186.0/24	Valid	RIR databaseRIPE	673 100%	67
194.56.187.0/24	Valid	RIR databaseRIPE	673 100%	67
212.103.39.0/24	Valid	RIR databaseRIPE	673 100%	66
45.139.220.0/24	Valid	RIR databaseRIPE	672 100%	66
45.139.223.0/24	Valid	RIR databaseRIPE	672 100%	66
91.194.54.0/24	Valid	RIR databaseRIPE	672 100%	66
92.112.93.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
185.82.222.0/24	Valid	RIR databaseRIPE	672 100%	67
185.126.178.0/24	Valid	RIR databaseRIPE	672 100%	67
193.35.204.0/24	Valid	RIR databaseRIPE	672 100%	67
193.35.205.0/24	Valid	RIR databaseRIPE	672 100%	67
193.35.206.0/24	Valid	RIR databaseRIPE	672 100%	67
193.138.172.0/24	Valid	RIR databaseRIPE	672 100%	67
193.138.173.0/24	Valid	RIR databaseRIPE	672 100%	67
193.138.175.0/24	Valid	RIR databaseRIPE	672 100%	67
212.103.36.0/24	Valid	RIR databaseRIPE	672 100%	67
212.103.37.0/24	Valid	RIR databaseRIPE	672 100%	67
212.103.38.0/24	Valid	RIR databaseRIPE	672 100%	67
45.130.13.0/24	Valid	RIR databaseRIPE	671 100%	67
45.130.14.0/24	Valid	RIR databaseRIPE	671 100%	67
45.130.15.0/24	Valid	RIR databaseRIPE	671 100%	67
45.136.106.0/24	Valid	RIR databaseRIPE	671 100%	67
45.145.22.0/24	Valid	RIR databaseRIPE	671 100%	67
45.145.23.0/24	Valid	RIR databaseRIPE	671 100%	66
81.90.177.0/24	Valid	RIR databaseRIPE	671 100%	67
81.90.179.0/24	Valid	RIR databaseRIPE	671 100%	67
81.200.141.0/24	Valid	RIR databaseRIPE	671 100%	67
81.200.142.0/24	Valid	RIR databaseRIPE	671 100%	67
91.106.216.0/24	Valid	RIR databaseRIPE	671 100%	67
91.106.217.0/24	Valid	RIR databaseRIPE	671 100%	67
91.106.218.0/24	Valid	RIR databaseRIPE	671 100%	67
91.106.219.0/24	Valid	RIR databaseRIPE	671 100%	67
153.56.251.0/24	Valid	RIR databaseRIPE	671 100%	67
185.82.220.0/24	Valid	RIR databaseRIPE	671 100%	67
185.82.221.0/24	Valid	RIR databaseRIPE	671 100%	67
185.82.223.0/24	Valid	RIR databaseRIPE	671 100%	67
185.126.177.0/24	Valid	RIR databaseRIPE	671 100%	67
185.185.235.0/24	Valid	RIR databaseRIPE	671 100%	67
193.138.174.0/24	Valid	RIR databaseRIPE	671 100%	67
194.56.185.0/24	Valid	RIR databaseRIPE	671 100%	67
194.127.116.0/24	Valid	RIR databaseRIPE	671 100%	67
194.127.117.0/24	Valid	RIR databaseRIPE	671 100%	67
194.127.118.0/24	Valid	RIR databaseRIPE	671 100%	67
45.139.221.0/24	Valid	RIR databaseRIPE	670 100%	67
45.145.21.0/24	Valid	RIR databaseRIPE	670 100%	67
81.90.176.0/24	Valid	RIR databaseRIPE	670 100%	67
81.90.178.0/24	Valid	RIR databaseRIPE	670 100%	67
153.56.139.0/24	Valid	RIR databaseRIPE	670 100%	67
185.126.179.0/24	Valid	RIR databaseRIPE	670 100%	67
2a0a:c4c0::/48	Valid	RIR databaseRIPE	635 100%	67
2a0a:c4c0:1::/48	Valid	RIR databaseRIPE	634 100%	67
91.198.64.0/24	Valid	RIR databaseRIPE	267 40%	52

AS-SET

AS47952 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 7 are in fix.csv.

Route object: none1
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: none	81.200.140.0/24	No route object for it. Add a route object with origin AS47952 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

81.200.140.0/24

No route object for it. Add a route object with origin AS47952 in the RIR database for the space.

672 of 673

Route objects not announced

Route objects with origin AS47952 whose prefix no peer sees AS47952 announce. Many are kept on purpose (backup routes, space announced only in some places).


194.127.119.0/24	RIPE	Valid
2a0a:c4c0::/64	RIPE	Invalid: maxLength
2a0a:c4c0:1::/64	RIPE	Invalid: maxLength
2a0a:c4c0:2::/48	RIPE	Valid
2a0a:c4c0:3::/48	RIPE	Valid
2a0a:c4c0:100::/48	RIPE	Valid

194.127.119.0/24

RIPE

Valid

2a0a:c4c0::/64

RIPE

Invalid: maxLength

2a0a:c4c0:1::/64

RIPE

Invalid: maxLength

2a0a:c4c0:2::/48

RIPE

Valid

2a0a:c4c0:3::/48

RIPE

Valid

2a0a:c4c0:100::/48

RIPE

Valid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.