SUBNET.IM

85.9.128.0/24

Tacom LLCAS34557

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCTJ

Allocated 14th February 2005

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 85.9.128.0/24, fanning out from AS34557 toward the vantage points that see it. Each path is written out in full beneath the graph.AS34557Tacom LLCOriginAS208592LLC "NET SOLUTION…AS51346Opened Joint Stoc…AS29049Delta Telecom LtdAS8529Zain Omantel Inte…AS12389Rostelecom PJSCAS6939Hurricane Electri…AS213151Christian ElsenAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS4766Korea TelecomAS132337AxclusiveAS20130Depaul University
  1. London, UK3455720859251346290498529This path
  2. Amsterdam3455720859251346123896939213151This path
  3. Sao Paulo3455720859251346290493356266213This path
  4. Singapore3455720859251346123894766132337This path
  5. Oregon, US345572085925134612389693920130This 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
Tajikistan
Allocated
14th February 2005
Allocation block
85.9.128.0/18
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 85.9.128.0/24
ROA prefixAuthorised originMax length
85.9.128.0/24AS34557/24
85.9.128.0/18AS34557/18

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 85.9.128.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.85.9.128.0/18AS3455785.9.128.0/24AS34557This prefix85.9.129.0/24AS34557

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 85.9.128.0/24
PrefixAddressesOriginVisibility
85.9.128.0/1816.4kAS34557Tacom LLC80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 85.9.128.0/24
PrefixAddressesOriginVisibility
85.9.129.0/24256AS34557Tacom LLC80/80

History

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

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