Network · data from 2026-11-12

AS9000 ESER-ASN Eser Telekom Sanayi ve Ticaret A.S.

Registry name: ESER-ASN Eser Telekom Sanayi ve Ticaret A.S., TR · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

22Route objects not announced registered with origin AS9000, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9000, 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.


84.17.85.0/24	Valid	RIR databaseRIPE	672 100%	66
212.50.37.0/24	Valid	RIR databaseRIPE	672 100%	66
212.50.41.0/24	Valid	RIR databaseRIPE	672 100%	66
212.50.32.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.33.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.34.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.36.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.38.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.39.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.40.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.54.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.55.0/24	Valid	RIR databaseRIPE	671 100%	67
212.50.61.0/24	Valid	RIR databaseRIPE	671 100%	67

AS-SET

AS9000 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 22 are in fix.csv.

Route object: not announced22

Route objects not announced

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


212.50.32.0/19	RIPE	No ROA
212.50.35.0/24	RIPE	Invalid: origin
212.50.36.0/22	RIPE	No ROA
212.50.42.0/24	RIPE	Invalid: origin
212.50.43.0/24	RIPE	Invalid: origin
212.50.44.0/24	RIPE	Valid
212.50.45.0/24	RIPE	Invalid: origin
212.50.46.0/24	RIPE	Invalid: origin
212.50.47.0/24	RIPE	Invalid: origin
212.50.48.0/24	RIPE	Invalid: origin
212.50.49.0/24	RIPE	Invalid: origin
212.50.50.0/24	RIPE	Invalid: origin
212.50.51.0/24	RIPE	Invalid: origin
212.50.52.0/24	RIPE	Invalid: origin
212.50.53.0/24	RIPE	Invalid: origin
212.50.56.0/24	RIPE	Invalid: origin
212.50.57.0/24	RIPE	Invalid: origin
212.50.58.0/24	RIPE	Invalid: origin
212.50.59.0/24	RIPE	Invalid: origin
212.50.60.0/24	RIPE	Invalid: origin
212.50.62.0/24	RIPE	Invalid: origin
212.50.63.0/24	RIPE	Invalid: origin

212.50.32.0/19

RIPE

No ROA

212.50.35.0/24

RIPE

Invalid: origin

212.50.36.0/22

RIPE

No ROA

212.50.42.0/24

RIPE

Invalid: origin

212.50.43.0/24

RIPE

Invalid: origin

212.50.44.0/24

RIPE

Valid

212.50.45.0/24

RIPE

Invalid: origin

212.50.46.0/24

RIPE

Invalid: origin

212.50.47.0/24

RIPE

Invalid: origin

212.50.48.0/24

RIPE

Invalid: origin

212.50.49.0/24

RIPE

Invalid: origin

212.50.50.0/24

RIPE

Invalid: origin

212.50.51.0/24

RIPE

Invalid: origin

212.50.52.0/24

RIPE

Invalid: origin

212.50.53.0/24

RIPE

Invalid: origin

212.50.56.0/24

RIPE

Invalid: origin

212.50.57.0/24

RIPE

Invalid: origin

212.50.58.0/24

RIPE

Invalid: origin

212.50.59.0/24

RIPE

Invalid: origin

212.50.60.0/24

RIPE

Invalid: origin

212.50.62.0/24

RIPE

Invalid: origin

212.50.63.0/24

RIPE

Invalid: origin

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.