subnet.im

141.11.184.0/24

Belce TaylanAS219084

CODE ASSET LTDAS205489

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

29%

22 of 76 vantage points

RPKI

Invalid

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 Singapore.

OriginVantage point · Singapore
One AS path to 141.11.184.0/24 as seen from Singapore, read outward from the origin: AS219084 → AS208226 → AS212477 → AS2914 → AS23673. Each hop is listed with its network name beneath the graph.AS219084Belce TaylanOriginAS208226Ouiheberg SARLAS212477RoyaleHosting B.V.AS2914NTT America, Inc.AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS219084seen on 120 paths from 76 vantage points
  2. Peer of AS208226seen on 396 paths from 139 vantage points
  3. Peer of AS212477seen on 8,710 paths from 77 vantage points
  4. Peer of AS2914seen on 78,227 paths from 1 vantage 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. Singapore219084208226212477291423673Shown above
  2. Oregon, US205489566306762168042013This 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

29%

Seen by 22 of 76 full-feed vantage points

Seen by few vantage points

Observed at 2 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
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 141.11.184.0/24
ROA prefixAuthorised originMax length
141.11.184.0/24AS834/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.184.0/24
PrefixAddressesOriginVisibility
141.11.185.0/24256AS208226Ouiheberg SARL76/76

History

  1. AS2054899th November 2026 — present
  2. AS21908412th October 2026 — present
  3. AS40136222nd September 2026 — 6th October 2026
  4. AS20548912th August 2026 — 21st 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.184.0/24 in the calculator/24 reference

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