SUBNET.IM

61.4.29.0/24

Towngas Telecommunications Fixed Network LimitedAS10132

At a glance

Addresses

256

/24 block

Visibility

24%

19 of 80 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 31st August 2000

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: 3 observed paths to 61.4.29.0/24, fanning out from AS10132 toward the vantage points that see it. Each path is written out in full beneath the graph.AS10132Towngas Telecommu…OriginAS10098Towngas Telecommu…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS58299Openfactory GmbH …AS41051Freetransit Proje…AS213151Christian Elsen
  1. Singapore1013210098132337This path
  2. Oregon, US1013210098693920130This path
  3. Amsterdam101321009869395829941051213151This 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

24%

Seen by 19 of 80 full-feed vantage points

Seen by few vantage points

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
APNIC — Asia-Pacific
Country
Hong Kong SAR China
Allocated
31st August 2000
Allocation block
61.4.0.0/18
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 61.4.29.0/24
ROA prefixAuthorised originMax length
61.4.29.0/24AS10132/24
61.4.0.0/18AS10132/18

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 61.4.29.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.61.4.0.0/18AS1013261.4.29.0/24AS10132This prefix61.4.28.0/24AS10132

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 61.4.29.0/24
PrefixAddressesOriginVisibility
61.4.0.0/1816.4kAS10132Towngas Telecommunications Fixed Network Limited80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 61.4.29.0/24
PrefixAddressesOriginVisibility
61.4.28.0/24256AS10132Towngas Telecommunications Fixed Network Limited19/80

History

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

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