SUBNET.IM

210.7.40.0/24

REANNZ CorporateAS38299

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICNZ

Allocated 16th May 2006

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: 5 observed paths to 210.7.40.0/24, fanning out from AS38299 toward the vantage points that see it. Each path is written out in full beneath the graph.AS38299REANNZ CorporateOriginAS38022REANNZ National R…AS137409GSL Networks Pty …AS8529Zain Omantel Inte…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS135069Feenix Communicat…AS174Cogent Communicat…AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK38299380221374098529This path
  2. Sao Paulo38299380223356266213This path
  3. Singapore38299380226939132337This path
  4. Oregon, US3829938022693920130This path
  5. Amsterdam382993802213506917434549213151This 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 80 of 80 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
APNIC — Asia-Pacific
Country
New Zealand
Allocated
16th May 2006
Allocation block
210.7.32.0/20
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 210.7.40.0/24
ROA prefixAuthorised originMax length
210.7.40.0/24AS38299/24
210.7.32.0/20AS38022/20

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 210.7.40.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.210.7.32.0/20AS38022210.7.40.0/24AS38299This prefix210.7.41.0/24AS38299

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 210.7.40.0/24
PrefixAddressesOriginVisibility
210.7.32.0/204.1kAS38022REANNZ National Research and Education Network79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 210.7.40.0/24
PrefixAddressesOriginVisibility
210.7.41.0/24256AS38299REANNZ Corporate79/80

History

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

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