subnet.im

206.123.142.0/24

HDTIDC LIMITEDAS205960

Free Range Cloud Hosting Inc.AS53356

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

99%

75 of 76 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 9th March 2015

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 206.123.142.0/24 as seen from Singapore, read outward from the origin: AS205960 → AS138195 → AS138415 → AS17476 → AS23673. Each hop is listed with its network name beneath the graph.AS205960HDTIDC LIMITEDOriginAS138195MOACK.Co.LTDAS138415Yancy LimitedAS17476CloudRadium (HK) …AS23673Cogetel Online, C…

Seen from Singapore

  1. Peer of AS205960seen on 1,811 paths from 76 vantage points
  2. Peer of AS138195seen on 6,877 paths from 76 vantage points
  3. Peer of AS138415seen on 5,979 paths from 91 vantage points
  4. Adjacentseen on 797 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. Singapore2059601381951384151747623673Shown above
  2. London, UK2059601381951384151747664538529This path
  3. Sao Paulo20596013819513841517476645335280This path
  4. Amsterdam205960138195138415174766453250918298This path
  5. Oregon, US2059601381951384151747664531299855142013This 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

99%

Seen by 75 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
ARIN — North America
Country
United States
Allocated
9th March 2015
Allocation block
206.123.128.0/19
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 206.123.142.0/24
ROA prefixAuthorised originMax length
206.123.142.0/24AS205960/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 206.123.142.0/24
PrefixAddressesOriginVisibility
206.123.143.0/24256AS3223Voxility LLP76/76

History

  1. AS533563rd November 2026 — present
  2. AS20596015th October 2026 — present
  3. AS900912th August 2026 — 3rd November 2026
  4. AS5335622nd September 2026 — 12th October 2026
  5. AS40213312th 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 206.123.142.0/24 in the calculator/24 reference

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