subnet.im

91.235.140.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCGB

Allocated 13th February 2012

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 91.235.140.0/24 as seen from Singapore, read outward from the origin: AS44521 → AS32787 → AS132337. Each hop is listed with its network name beneath the graph.AS44521Jagex LimitedOriginAS32787Akamai (Prolexic)AS132337Axclusive

Seen from Singapore

  1. Peer of AS44521seen on 596 paths from 80 vantage points
  2. Peer of AS32787seen on 6,619 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. Amsterdam4452132787213151This path
  2. London, UK44521327878529This path
  3. Sao Paulo4452132787266213This path
  4. Singapore4452132787132337Shown above
  5. Oregon, US4452132787693920130This 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
United Kingdom
Allocated
13th February 2012
Allocation block
91.235.140.0/24
Status
assigned
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

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.235.140.0/24
PrefixAddressesOriginVisibility
91.235.141.0/24256AS16347ADISTA SAS80/80

History

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

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