subnet.im

141.11.238.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCFR

Allocated 26th May 1992

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 141.11.238.0/24 as seen from London, UK, read outward from the origin: AS402390 → AS137969 → AS9304 → AS6453 → AS8529. Each hop is listed with its network name beneath the graph.AS402390Wisewave Informat…OriginAS137969HONG KONG BRIDGE …AS9304HGC Global Commun…AS6453TATA Communicatio…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS402390seen on 992 paths from 76 vantage points
  2. Peer of AS137969seen on 2,473 paths from 75 vantage points
  3. Peer of AS9304seen on 42,912 paths from 136 vantage points
  4. Peer of AS6453seen on 76,461 paths from 2 vantage points

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. Amsterdam40239013796993048298This path
  2. Sao Paulo402390137969930435280This path
  3. London, UK402390137969930464538529Shown above
  4. Singapore4023901379699304463523673This path
  5. Oregon, US402390137969930474736461855142013This 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 76 of 76 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
France
Allocated
26th May 1992
Allocation block
141.11.0.0/16
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 141.11.238.0/24
ROA prefixAuthorised originMax length
141.11.238.0/24AS402390/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 141.11.238.0/24
PrefixAddressesOriginVisibility
141.11.239.0/24256AS210440AKAERE NETWORKS TECHNOLOGY LTD76/76

History

  1. AS40239015th October 2026 — present
  2. AS15133812th August 2026 — 6th October 2026
  3. AS20392312th August 2026 — 5th October 2026
  4. AS20998829th September 2026 — 29th September 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 141.11.238.0/24 in the calculator/24 reference

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