SUBNET.IM

66.110.0.0/17

TATA Communications (America) IncAS6453

At a glance

Addresses

32,768

/17 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

Unknown

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 66.110.0.0/17 as seen from Singapore, read outward from the origin: AS6453 → AS9002 → AS132337. Each hop is listed with its network name beneath the graph.AS6453TATA Communicatio…OriginAS9002RETN LimitedAS132337Axclusive

Seen from Singapore

  1. 1AS6453TATA Communications (America) IncUSOrigin
    Peer of AS6453seen on 241,792 paths from 25 vantage points
  2. 2AS9002RETN LimitedGB
    Peer of AS9002seen on 45,093 paths from 2 vantage points
  3. 3AS132337AxclusiveSGVantage 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. London, UK64538529This path
  2. Amsterdam645334549213151This path
  3. Sao Paulo64533356266213This path
  4. Singapore64539002132337Shown above
  5. Oregon, US6453693920130This 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 79 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
Unknown
Country
Unknown
Allocated
Unknown
Allocation block
Unknown
Status
Unknown
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 66.110.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.66.110.0.0/17AS6453This prefix66.110.0.0/18AS645366.110.96.0/19AS645366.110.64.0/20AS645366.110.112.0/20AS1125966.110.40.0/21AS6453+10 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

No less specific announcement covers this prefix.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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

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