subnet.im

185.184.25.0/24

MUV Bilisim ve Telekomunikasyon Hizmetleri Ltd. Sti.AS209711

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCTR

Allocated 2nd January 2017

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: 1 observed path to 185.184.25.0/24, fanning out from AS209711 toward the vantage points that see it. Each path is written out in full beneath the graph.AS209711MUV Bilisim ve Te…OriginAS43260DGN TEKNOLOJI A.S.AS44901Belcloud LTDAS3257GTT Communication…AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Oregon, US209711432604490132576762168042013This 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.

Route visibility

1%

Seen by 1 of 76 full-feed vantage points

Seen by few vantage points

Observed at 1 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
2nd January 2017
Allocation block
185.184.24.0/22
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 185.184.25.0/24
ROA prefixAuthorised originMax length
185.184.25.0/24AS0/24

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.184.25.0/24
PrefixAddressesOriginVisibility
185.184.24.0/24256AS218964QUATTRO APPS LTD76/76

History

  1. AS20971129th October 2026 — present
  2. AS1997416th October 2026 — 29th October 2026
  3. AS20971112th August 2026 — 22nd October 2026
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.184.25.0/24 in the calculator/24 reference

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