subnet.im

185.85.205.0/24

AKA Bilisim Yazilim Arge Ins. Taah. San. Tic. A.S.AS201079

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCTR

Allocated 27th January 2015

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 185.85.205.0/24 as seen from Oregon, US, read outward from the origin: AS201079 → AS15830 → AS12735 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS201079AKA Bilisim Yazil…OriginAS15830Equinix, Inc.AS12735TurkNet Iletisim …AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. 1AS201079AKA Bilisim Yazilim Arge Ins. Taah. San. Tic. A.S.TROrigin
    Peer of AS201079seen on 612 paths from 80 vantage points
  2. 2AS15830Equinix, Inc.NL
    Peer of AS15830seen on 3,094 paths from 141 vantage points
  3. 3AS12735TurkNet Iletisim Hizmetleri A.S.TR
    Peer of AS12735seen on 5,518 paths from 29 vantage points
  4. 4AS6939Hurricane Electric LLCUS
    Peer of AS6939seen on 975,334 paths from 1 vantage point
  5. 5AS20130Depaul UniversityUSVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Amsterdam2010791583012735213151This path
  2. Singapore2010791583012735132337This path
  3. London, UK201079158301273554058529This path
  4. Oregon, US2010791583012735693920130Shown above
  5. Sao Paulo201079158301273590023356266213This 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

100%

Seen by 80 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
27th January 2015
Allocation block
185.85.204.0/22
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 185.85.205.0/24
ROA prefixAuthorised originMax length
185.85.205.0/24AS201079/24
185.85.204.0/22AS201079/22

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 185.85.205.0/24
PrefixAddressesOriginVisibility
185.85.204.0/24256AS201079AKA Bilisim Yazilim Arge Ins. Taah. San. Tic. A.S.80/80

History

  1. AS20107912th 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 185.85.205.0/24 in the calculator/24 reference

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