SUBNET.IM

95.1.128.0/17

Turk TelekomAS9121

At a glance

Addresses

32,768

/17 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCTR

Allocated 14th October 2008

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 95.1.128.0/17, fanning out from AS9121 toward the vantage points that see it. Each path is written out in full beneath the graph.AS9121Turk TelekomOriginAS8529Zain Omantel Inte…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS5511Orange S.A.AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK91218529This path
  2. Sao Paulo91213356266213This path
  3. Singapore91216939132337This path
  4. Oregon, US9121693920130This path
  5. Amsterdam91213356551134549213151This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

99%

Seen by 79 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
RIPE NCC — Europe, Middle East, Central Asia
Country
Türkiye
Allocated
14th October 2008
Allocation block
95.0.0.0/12
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 95.1.128.0/17
ROA prefixAuthorised originMax length
95.0.0.0/12AS47331/24
95.0.0.0/12AS9121/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 95.1.128.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.95.0.0.0/12AS912195.1.128.0/17AS9121This prefix95.1.0.0/17AS912195.1.128.0/20AS912195.1.160.0/20AS912195.1.144.0/21AS912195.1.176.0/21AS912195.1.152.0/22AS9121+14 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 95.1.128.0/17
PrefixAddressesOriginVisibility
95.0.0.0/121MAS9121Turk Telekom78/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 95.1.128.0/17
PrefixAddressesOriginVisibility
95.1.0.0/1732.8kAS9121Turk Telekom79/80

History

  1. AS912112th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 95.1.128.0/17 in the calculator/17 reference

Routing data derived from RouteViews MRT archives and public registry data.