subnet.im

153.56.205.0/24

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCKZ

Allocated 23rd September 1991

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 153.56.205.0/24 as seen from Amsterdam, read outward from the origin: AS58172 → AS39824 → AS41798 → AS60299 → AS12389 → AS6939 → AS8298. Each hop is listed with its network name beneath the graph.AS58172Freedom Telecom O…OriginAS39824JSC Alma Telecomm…AS41798JSC TranstelecomAS60299Mezhdugorodnyaya …AS12389PJSC RostelecomAS6939Hurricane Electri…AS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS58172seen on 3,795 paths from 138 vantage points
  2. Peer of AS39824seen on 6,143 paths from 139 vantage points
  3. Peer of AS41798seen on 13,266 paths from 138 vantage points
  4. Peer of AS60299seen on 15,126 paths from 136 vantage points
  5. Peer of AS12389seen on 413,266 paths from 105 vantage points
  6. Peer of AS6939seen on 130,728 paths from 2 vantage points
  7. 7AS8298IPng Networks GmbHCHVantage 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. London, UK58172398244179890028529This path
  2. Sao Paulo5817239824417989002645335280This path
  3. Oregon, US5817239824417989002855142013This path
  4. Amsterdam581723982441798602991238969398298Shown above

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

72%

Seen by 55 of 76 full-feed vantage points

Partially propagated

Observed at 4 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
Kazakhstan
Allocated
23rd September 1991
Allocation block
153.56.204.0/23
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 153.56.205.0/24
ROA prefixAuthorised originMax length
153.56.205.0/24AS58172/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 153.56.205.0/24
PrefixAddressesOriginVisibility
153.56.204.0/24256AS58172Freedom Telecom Operations LLP76/76

History

  1. AS5817210th November 2026 — present
  2. AS5817227th October 2026 — 3rd November 2026
  3. AS5817215th October 2026 — 19th 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 153.56.205.0/24 in the calculator/24 reference

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