SUBNET.IM

240a:eff3::/32

BHARAT PUBLIC DNS (1.10.10.10)AS148000

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

18%

11 of 62 vantage points

RPKI

Invalid

Registry

APNICIN

Allocated 19th October 2021

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: 1 observed path to 240a:eff3::/32, fanning out from AS148000 toward the vantage points that see it. Each path is written out in full beneath the graph.AS148000BHARAT PUBLIC DNS…OriginAS45117Ishan Netsol Pvt …AS9498Bharti Airtel Ltd.AS132337Axclusive
  1. Singapore148000451179498132337This 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.

Route visibility

18%

Seen by 11 of 62 full-feed vantage points

Seen by few vantage points

Observed at 4 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
19th October 2021
Allocation block
240a:e000::/20
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 240a:eff3::/32
ROA prefixAuthorised originMax length
240a:eff0::/30AS148001/32
240a:eff0::/28AS148001/30
240a:e800::/21AS38620/22
240a:e000::/20AS148000/20

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 240a:eff3::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.240a:e000::/20AS148000240a:eff3::/32AS148000This prefix240a:eff2::/32AS148000

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 240a:eff3::/32
PrefixAddressesOriginVisibility
240a:e000::/2017.6T × /64AS148000BHARAT PUBLIC DNS (1.10.10.10)62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 240a:eff3::/32
PrefixAddressesOriginVisibility
240a:eff2::/324.3B × /64AS148000BHARAT PUBLIC DNS (1.10.10.10)62/62

History

  1. AS14800012th 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.

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