SUBNET.IM

164.100.0.0/17

National Informatics CentreAS4758

At a glance

Addresses

32,768

/17 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICIN

Allocated 4th February 1993

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 164.100.0.0/17, fanning out from AS4758 toward the vantage points that see it. Each path is written out in full beneath the graph.AS4758National Informat…OriginAS9885NKN INTERNET GATE…AS4755TATA Communicatio…AS6453TATA Communicatio…AS8529Zain Omantel Inte…AS55836Reliance Jio Info…AS64049Reliance Jio Info…AS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian ElsenAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. London, UK47589885475564538529This path
  2. Singapore475898855583664049132337This path
  3. Amsterdam47589885558366404934549213151This path
  4. Sao Paulo4758988555836640493356266213This path
  5. Oregon, US4758988547556453693920130This 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
India
Allocated
4th February 1993
Allocation block
164.100.0.0/16
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 164.100.0.0/17
ROA prefixAuthorised originMax length
164.100.0.0/17AS4758/17
164.100.0.0/16AS4758/16

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 164.100.0.0/17: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.164.100.0.0/16AS4758164.100.0.0/17AS4758This prefix164.100.128.0/17AS4758164.100.0.0/19AS4758164.100.32.0/19AS4758164.100.64.0/19AS4758164.100.96.0/19AS4758164.100.0.0/20AS4758+19 more

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 164.100.0.0/17
PrefixAddressesOriginVisibility
164.100.0.0/1665.5kAS4758National Informatics Centre80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 164.100.0.0/17
PrefixAddressesOriginVisibility
164.100.128.0/1732.8kAS4758National Informatics Centre80/80

History

  1. AS475812th 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 164.100.0.0/17 in the calculator/17 reference

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