subnet.im

91.228.39.0/24

KazNIC OrganizationAS60708

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCKZ

Allocated 24th May 2011

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 91.228.39.0/24 as seen from London, UK, read outward from the origin: AS60708 → AS9198 → AS31133 → AS8529. Each hop is listed with its network name beneath the graph.AS60708KazNIC Organizati…OriginAS9198JSC KazakhtelecomAS31133MegaFon PJSCAS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS60708KazNIC OrganizationKZOrigin
    Peer of AS60708seen on 80 paths from 80 vantage points
  2. 2AS9198JSC KazakhtelecomKZ
    Peer of AS9198seen on 42,999 paths from 82 vantage points
  3. 3AS31133MegaFon PJSCRU
    Peer of AS31133seen on 1,916 paths from 1 vantage point
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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, UK607089198311338529Shown above
  2. Amsterdam607089198437276939213151This path
  3. Sao Paulo60708919832163356266213This path
  4. Singapore607089198123894766132337This path
  5. Oregon, US60708919843727693920130This 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
Kazakhstan
Allocated
24th May 2011
Allocation block
91.228.39.0/24
Status
assigned
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 91.228.39.0/24
ROA prefixAuthorised originMax length
91.228.39.0/24AS60708/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 91.228.39.0/24
PrefixAddressesOriginVisibility
91.228.38.0/24256AS48452Telco power Ltd80/80

History

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

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