subnet.im

217.76.72.0/24

Mobile Telecom-Service LLPAS29555

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCKZ

Allocated 7th October 2003

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 217.76.72.0/24 as seen from London, UK, read outward from the origin: AS29555 → AS48503 → AS35168 → AS20485 → AS8529. Each hop is listed with its network name beneath the graph.AS29555Mobile Telecom-Se…OriginAS48503Mobile Telecom-Se…AS35168TNS-Plus LLPAS20485TransTeleCom JSCAS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS29555Mobile Telecom-Service LLPKZOrigin
    Peer of AS29555seen on 10,934 paths from 142 vantage points
  2. 2AS48503Mobile Telecom-Service LLPKZ
    Peer of AS48503seen on 15,843 paths from 142 vantage points
  3. 3AS35168TNS-Plus LLPKZ
    Peer of AS35168seen on 28,319 paths from 142 vantage points
  4. 4AS20485TransTeleCom JSCRU
    Peer of AS20485seen on 3,896 paths from 2 vantage points
  5. 5AS8529Zain 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. Amsterdam29555485033516820485213151This path
  2. London, UK295554850335168204858529Shown above
  3. Oregon, US295554850335168693920130This path
  4. Sao Paulo29555485033516832163356266213This path
  5. Singapore2955548503919812389174132337This 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
7th October 2003
Allocation block
217.76.64.0/20
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 217.76.72.0/24
ROA prefixAuthorised originMax length
217.76.72.0/24AS29555/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 217.76.72.0/24
PrefixAddressesOriginVisibility
217.76.73.0/24256AS29555Mobile Telecom-Service LLP80/80

History

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

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