subnet.im

141.11.228.0/24

HGC Global Communications LimitedAS9304

CODE ASSET LTDAS205489

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

6%

5 of 78 vantage points

RPKI

Invalid

Registry

RIPE NCCFR

Allocated 26th May 1992

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 2 observed paths to 141.11.228.0/24, fanning out from AS9304, AS205489 toward the vantage points that see it. Each path is written out in full beneath the graph.AS9304HGC Global Commun…OriginAS38623Metfone (Viettel …AS23673Cogetel Online, C…AS205489CODE ASSET LTDOriginAS215120Evolus IT Solutio…AS174Cogent Communicat…AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…
  1. Singapore93043862323673This path
  2. Oregon, US2054892151201746762168042013This 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

6%

Seen by 5 of 78 full-feed vantage points

Seen by few vantage points

Observed at 1 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.228.0/24
ROA prefixAuthorised originMax length
141.11.228.0/24AS212336/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.228.0/24
PrefixAddressesOriginVisibility
141.11.229.0/24256AS16509Amazon.com, Inc.78/78

History

  1. AS20548911th November 2026 — present
  2. AS930412th October 2026 — present
  3. AS2123367th November 2026 — 11th November 2026
  4. AS2054894th November 2026 — 7th November 2026
  5. AS3818622nd September 2026 — 12th October 2026
  6. AS930429th September 2026 — 29th September 2026
  7. 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.228.0/24 in the calculator/24 reference

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